RE: Unable to connect to sql server remotely
From: Kevin McDonnell [MSFT] (kevmc_at_online.microsoft.com)
Date: 07/19/04
- Next message: Kevin McDonnell [MSFT]: "RE: Timeout error in SQL Server Enterprise Manager"
- Previous message: Kevin McDonnell [MSFT]: "RE: Q: Named pipes and Windows (integrated) authentication"
- In reply to: SqlJunkies User: "Unable to connect to sql server remotely"
- Next in thread: Tom Kamps: "RE: Unable to connect to sql server remotely"
- Reply: Tom Kamps: "RE: Unable to connect to sql server remotely"
- Reply: Tom Kamps: "RE: Unable to connect to sql server remotely"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 19 Jul 2004 22:03:14 GMT
The error 10061 means that the connection was refused. This usually means :
1.) the server isn't listening on TCP/IP. Check the SQL Errorlog to verify
this.
or run : netstat -an from a DOS prompt to verify that the server is
listening on 1433.
2.) your client is connecting to the wrong server. Could be a WINS or DNS
issue. So, your client may be connecting to another computer that is not
running SQL. SQL is a Winsock application, so it needs to be listening on
a socket for the client to establish the connection.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
- Next message: Kevin McDonnell [MSFT]: "RE: Timeout error in SQL Server Enterprise Manager"
- Previous message: Kevin McDonnell [MSFT]: "RE: Q: Named pipes and Windows (integrated) authentication"
- In reply to: SqlJunkies User: "Unable to connect to sql server remotely"
- Next in thread: Tom Kamps: "RE: Unable to connect to sql server remotely"
- Reply: Tom Kamps: "RE: Unable to connect to sql server remotely"
- Reply: Tom Kamps: "RE: Unable to connect to sql server remotely"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|