Newly installed named instance of SQL Server 2012 with Mixed Authentication on Windows Server 2008 R2 x64:
SQL2012 is the instance name and it is listening on port 1080.
I restarted the service after changing the port #.
SSMS2012 running on a desktop Windows 7 x64 machine discovers the new database server but cannot connect, either as Server6 or as Server6\SQL2012:
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 2)
Per this article http://msdn.microsoft.com/en-us/library/ms177440.aspx I checked the SQL Server Network Configuration. The TCP/IP protocol was enabled; however, in the IP2 section, the IP address is the server's address on our LAN but the TCP Port was blank and dynamic ports was 0. I deleted the 0 and changed the TCP Port to 1080, saved, and restarted the services; but then SSMS no longer even discovers the server! So that change made things worse.
What haven't I done correctly?