CODEWITHSUNDEEP
sql-serversql-server-2008database-connection
jamauss
jamauss

Reputation: 1043

SQL Server 2008 suddenly stopped connecting

This one is strange...

I have a server at home that's part of my home network (workgroup). It has SQL Server 2008 R2 SP1 running on it. I've been connecting to it from my (other) desktop regularly for months now and tonight all of a sudden I can't connect to it from my desktop. I can connect to it if I RDP onto the server and connect locally. I've checked the event logs on the server and nothing interesting appears.

Here's the (unhelpful) error returned by Management Studio from my desktop when trying to connect to the server:

Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. (.Net SqlClient Data Provider)

I'm kinda stumped by this really. I've tried connecting with sqlcmd - it tells me this:

Sqlcmd: Error: Microsoft SQL Server Native Client 10.0 : Unable to complete login process due to delay in opening server connection.

Not really sure what that means. I've made sure SQL Server is configured to allow remote connections and have used netstat -a and seen that it's listening on port 1433 (for all IPs).

Anyone got any helpful ideas? I've rebooted the server too, but that didn't change anything.

EDIT/UPDATE: from my desktop I can ping the server by host name and I get something like this:

Reply from fe80::9077:4449:4b37:cad1%12: time<1ms

but if I try to ping it by it's IP address it times out. I wonder if that points to some kind of IPv4 vs. IPv6 issue?

Upvotes: 0

Views: 3821

Answers (1)

Steve B
Steve B

Reputation: 37690

Is the IP adress resolved from your desktop the actual ipadress of the server ?

Run a ipconfig /all from the server, and do a nslookup from your desktop to see if IP addresses are matching. I had cases when the DNS was messed up, and IP address resolution was wrong.

Upvotes: 1

Related Questions