all groups > sql server connect > april 2004 >
You're in the

sql server connect

group:

Problem when connecting from remote location to SQL Server 2k SP 3


Problem when connecting from remote location to SQL Server 2k SP 3 Luke
4/20/2004 9:07:18 AM
sql server connect:
This is when using SA account trying the SQL Query
Analyzer. I get the error Msg 17, Level 16, State 1. I
can locally connect fine on the server itself using SQL
Query Analyzer. I'm using SQL Authentication.

When trying to connect I get:

Unable to connect to server (name of server)
Server: Msg 17, Level 16, State 1
[Microsoft][ODBC SQL Server Driver][DBNETLIB] SQL Server
does not exist or access denied.

I verified that the port is open on the firewall pointing
to the server. Also, this just started happening and was
working fine before. I've reset the SA password and
verified that I am putting in either the DNS entry or IP
address and get the same error. Any help diagnosing this
RE: Problem when connecting from remote location to SQL Server 2k SP 3 kevmc NO[at]SPAM online.microsoft.com
4/21/2004 12:47:22 AM
Hi Luke,
Try running the following command using ISQL.exe

ISQL -Stcp:ServerNameHere -Usa -Ppassword -Q"select @@version"

Look for the OS Error returned. This will help you troubleshoot the
problem.

Thanks,

Kevin McDonnell
Microsoft Corporation

This posting is provided AS IS with no warranties, and confers no rights.


RE: Problem when connecting from remote location to SQL Server 2k SP 3 Luke
4/21/2004 1:25:13 PM
When I run that command, I get the following:

DB-Library: Unable to connect: SQL Server is unavailable
or does not exist. Una

ble to connect: SQL Server does not exist or network
access denied.

Net-Library error 10061: ConnectionOpen (Connect()).

This is when running on the server. I can't connect
RE: Problem when connecting from remote location to SQL Server 2k SP 3 kevmc NO[at]SPAM online.microsoft.com
4/21/2004 10:34:13 PM
Hi Luke,
The actual error is : 10061:

This means that the server is not listening on the port.
Restart MSSQLServer and verify that SQL is listening.

Check the NT Application logs and SQL Errorlogs. For SQL 2000 we print
this in the errorlog.
Also you can verify this by running netstat -an at the command prompt.



Thanks,

Kevin McDonnell
Microsoft Corporation

This posting is provided AS IS with no warranties, and confers no rights.


AddThis Social Bookmark Button