June 2, 2013 at 7:52 pm
Hi,
I am trying to connect to a named instance on another server myhost\myinstance, but get an 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: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=-1&LinkId=20476
If I use IP address and the port number, it all works fine. I can even connect using the hostname and the port number, but if I use the instance name, it does not work.
E.g.:
xxx.xxx.xxx.xxx,3000 -- works
myhost,3000 -- works
myhost\myinstance -- does not work
I can connect to myhost\myinstance from another server just fine.
The server which has problem is a clustered instance of SQL 2008 R2 SP2, the two other servers are SQL 2008 R2 SP1.
Any ideas?
Thanks.
June 2, 2013 at 10:54 pm
myhost\myinstance -- does not work
Are you referring to "myhost" as the SQL Cluster Virtual Name or the local active node?
Use the SQL cluster name instead of the node name or the Windows Cluster Name
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
This thing is addressing problems that dont exist. Its solution-ism at its worst. We are dumbing down machines that are inherently superior. - Gilfoyle
June 2, 2013 at 11:53 pm
It is SQL cluster name and I can connect to that instance from another server with no problems.
Let me try to explain it in a different way:
I can't connect from server A to server B using hostname\instance name
But it works when connecting from server C to server B.
So the problem is most likely on server A, not on the server I am trying to connect to.
June 3, 2013 at 12:30 am
please try with fully qualified host name.
June 3, 2013 at 12:39 am
are these two instances on the same domain?
June 3, 2013 at 12:52 am
They are on the same domain, but servers A and C are in a different subnet from server B.
June 3, 2013 at 1:38 am
cool, my advise, flush the DNS of Server A and B and use the fully qualified name.
June 4, 2013 at 1:27 am
It turned out that UDP port 1434 was blocked. Once unblocked, the problem was resolved.
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply