All the threads I have looked at document how to use localhost rather than the actual hostname.
SQL Server instance SQLP1 is running on CALSQL1. We can connect from another system using CALSQL1\SQLP1. Error message is at the end and is probably familiar to all.
We cannot connect when running SSMS on CALSQL1 to CALSQL1\SQLP1.
We can connect when running SSMS on CALSQL1 if we use localhost\SQLP1 or .\SQLP1
I suspect something is setup differently at the Windows O/S level on CALSQL1 than on our other servers.
We are using SQL Server 2008 R2 (10.50.1600) on Microsoft Windows [Version 6.1.7601]
Another instance running on a different node works as I would normally expect. I can run SSMS on CALSQL2 and connect to SQLP2 by entering CALSQL2\SQLP2 in the Server name field when connecting.
I am trying to understand why we cannot use the server name on the CALSQL1 server and what impacts this may have going forward.
Here's the error message.
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: TCP Provider, error: 0 - No connection could be made because the target machine actively refused it.) (Microsoft SQL Server, Error: 10061)