(Microsoft SQL Server, Error: 10060)

[sqlcasey]

Every now and then I receive this error, usually when trying to establish a connection to a new server. I checked and confirmed in surface area configuration that remote connections are enabled across tcp/ip. Also there are no firewall issues. This is sql server 2005. Any
ideas? Thank you.

TITLE: Connect to Server
------------------------------

Cannot connect to magneto2.

------------------------------
ADDITIONAL INFORMATION:

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. (provider: TCP Provider, error: 0 - 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.) (Microsoft SQL Server, Error: 10060)

For help, click:

http://go.microsoft.com/fwlink?Prod...r&EvtSrc=MSSQLServer&EvtID=10060&LinkId=20476

------------------------------
BUTTONS:

OK
------------------------------

 

[ptheriault]

When you recieve this error can you ping other servers on the network? Are there any other errors in the event viewer.

- Paul
- Database performance looks fine, it must be the Network!

 

[Catadmin]

Question, are the services running on the new server? Like SQL Server service, etc.

We occasionally have this problem with our clustered servers when we fail over. Usually, if we wait a few minutes for the services to refresh, it fixes itself.

Also, could be the permissions of the account you're trying to log in as. If that account doesn't have permissions on the new server, sometimes (not always) you get that message instead of the "invalid permissions" message.



Catadmin - MCDBA, MCSA
"No, no. Yes. No, I tried that. Yes, both ways. No, I don't know. No again. Are there any more questions?"
-- Xena, "Been There, Done That"

 

[sqlcasey]

Hi,

Yes, I can ping the server, even telnet to port 1433 on the server. I verified that all the services are running, including SQL Browser service (which is important on a server with two instances, as is the case here), also checked my aliases to make sure I am connecting to the correct server name. Everything looks fine.

I have connected to this server successfully in the past.

For some reason it does not work today.

 

[sqlcasey]

I should also probably add, I am able to connect to one of the instances on the server, just not the other.

The aliases are set up as follows:

MYSERVER2 - this does not work

MYSERVER2\instance - this works

 

[ptheriault]

I've had problems in the past with alias for a default instance. Microsoft has had me delete them and then things have worked fine. Do you need to alias. Have you tried to delete the alias and connect?

- Paul
- Database performance looks fine, it must be the Network!

 

[sqlcasey]

yep, that did it