After rebuilding a server, I am consistently getting "Timeout Expired" messages when trying to connect to SQL Server through SSMS with windows authentication from a machine other than the server itself.
I can connect SSMS from another machine if I user SQL Server authentication with a username and password. I can also use SSMS with Windows Authentication on the Server itself either by connecting with RDP or sitting down directly at the server.
I looked at [troubleshoot-timeout-expired-the-timeout-period-el][1] on this site, but that didn't quite seem to apply. I also looked at [Troubleshooting: Timeout Expired][2] but those suggestions did not resolve this issue.
This does not seem to be a DNS issue since I can connect to the Server through RDP and the shared folders come up over the network (not to mention I can connect to SQL Server with SQL Server authentication).
It does not seem to be a problem with my domain account since I can log in with Windows authentication from SSMS on the server.
I double checked the firewall settings and even tried (*temporarily!*, on a server with no route to the internet) disabling the firewall. And naturally, I have verified that I have the proper server name.
So, any ideas what could cause this?
[1]: http://ask.sqlservercentral.com/questions/41373/troubleshoot-timeout-expired-the-timeout-period-el.html
[2]: http://msdn.microsoft.com/en-us/library/ms190181.aspx
↧