asked
Login timeout error in SQL Server 2008 R2
Hi, I am not able to connect to a SQL instance (SQL 2008 R2) remotely properly. I am able to connect to it locally. Actually, remotely we CAN connect but only when we keep the Connetion timeout settings to something like 1500 secs. The connection is too slow and I cannot run any queries using Management studio. There is NO network issue as I am able to connect to other servers in that network. When I try OSQL/SQLCMD I get the below error: D:\Documents and Settings\ >osql /S ,1433 /E [SQL Native Client]TCP Provider: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. [SQL Native Client]Login timeout expired [SQL Native Client]An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. I have tried without PORT number too, same result. SQL browser is working, I have added SSMS,SQLCMD/OSQL to firewall exceptions on the target server. Any idea, what could be the problem???
If you are 100% that there are no general network issues, and you can connect to other machines from the same client, then by process of elimination, I would start to look at the specifics - check the network card on the SQL Server. Can you connect from another client machine in your environment? Or is it the same. You are looking for facts that either isolate or eliminate different scenarios. If you haven't ruled out those possibilities entirely then you may be chasing your tail.
On different client machines, its the same...we cannot connect. the said server is a virtual machine without the network...we can ping the server..and the client machines can also be pinged from the server.
I am sorry, I did not understand...what does "throttling requests" mean?
sorry. Is the virtual host configured to allow the volume of network traffic that you need or is it set at a threshold?
A few rambling thoughts: If you're having the same problem from various machines, then you need to look at the server side. You say it's a virtual server - is the virtual host restricting your server's access to the network? Is there another machine running on that virtual environment that's hogging all the bandwidth? Do other servers in the environment have the same problem, or is it just that one? If it's other servers, then you'll need to look at the wider environment - is the Virtual Environment itself starved of bandwidth? Have you got an overly-complex network route between clients & the servers? Lots of firewalls in the way? If, once the connection is open, the server is nicely responsive, then it could be a problem with authentication timeouts - what's the path like between the SQL Server and the AD controller?
It was a Firewall issue on the server side...thanks a lot everyone for helping...maybe I did not look into all options..
Firewalls are one of the more common causes of this error. Microsoft discusses this at
http://msdn.microsoft.com/en-us/library/ms190181.aspx
1 Person is following this question.
