My SSMS is not connecting to one particular server say X
except X
it is connecting to all the other servers. Could not find the root cause for this problem does anyone have idea here?
Guy sitting next to me can connect to X
server. Only for me its not connecting.
Note: Before one hour I can connect to same X
server.
Details of my ssms client
Microsoft SQL Server 2012 – 11.0.5058.0 (X64) May 14 2014 18:34:29
Copyright (c) Microsoft Corporation Developer Edition (64-bit) on
Windows NT 6.2 (Build 9200: )
Error am getting
Any help is highly appreciated.
I went to the command prompt and typed ping X
. It's coming back with Request Timed Out 4 times. Server is not down; my neighbour can connect to same X
server which is not connecting to me.
Best Answer
Due to your comments on the main answer, I would write my suggestions below. You described that your neighbor can still connect to the machine but you not. This doesn't seem like a normal behavior of an SQL Server. This just brings me to another conclusion. It seems to be more likely a network error. In fact, you also described that you could connect to the server too, just before an hour.
I would suggest the following solution approaches:
cmd
and typingnslookup serverx
. Compare it with the IP which was provided after you tried toping serverx
. Do they match? If not, you probably have a DNS error. Which means that Server X has another IP, but your PC hasn't recognized it in hisARP
. You may want to flush your your dns-cache. You can do this usingipconfig /flushdns
on the command line.tracert serverx
. Check which hops occur. Try the same on your machine. Do they match or is there any difference? If you found a timeout on a special ip, you can try to ping the corresponding ip from your pc and from the pc of your neighbor. If you can't reach the ip, but your neighbor can - it looks like a port error on a specific switch between you and your neighbor. By the way, the whole story at all seems to be a defect port in my opinion. Just due to the fact that this just occurs from one minute to the next is kind of specific for an port error. Even the fact that just you cannot connect to the server. You should try this!IDS
application (Intrusion detection system) which will detect misbehavior and close specific ports. If your company use such a system and it's not proper configured it may cause such a port close. I've had a similar solution in my old company in the first days of ourIDS
. You can also try to connect to server x from your neighbors PC usingRDP
and try to ping your PC from the side of the Server.If nothing else helps, you need to contact your system administrator (if your not the one :-D) and try to figure out which cable or port is broken.
I really don't think that this is an SQL Server specific error. I would guess that this is some hardware or maybe software error in your network/pc.