Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SQL2K SP3a connection issues 1

Status
Not open for further replies.

keebe418

IS-IT--Management
Feb 21, 2005
13
US
Hi All-
I am running 2 servers with SQL2K Server. One is running Win2003 server and the other is NT 4.0. Both servers are using the standard 1433 port for SQL. I am trying to get a third server(running NT as well) to connect to the 2003 server via SQL. I am able to connect to the 2003 through my laptop(XP SP2). At this point all attempted connections are within the same LAN. I have tried the same connection settings on a pc(XP SP2) and was getting the same error(see below).

Connection Failed:
SQLState:'01000'
SQL Server Error: 10061
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen (Connect())

Connection Failed:
SQLState:'08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server does not exist or access denied.

After searching for a while I referred to faq962-5481 which came in very useful to test the problem.

With my laptop I am able to connect via SQL, file share, etc. With any of the pc's I have tried I have been able to connect with the file share on the server, but unsuccessful to connect via SQL.

There is no firewall I have to go through to connect to the SQL server. All of the IP's are static and I do not see anything in the router that would stop the other pc's from connecting.

Plainly stated...I need get the WinNT 4.0 server to connect to the SQL on the Win2003 server. Anyone have any suggestions I would appreciate it.

-Shawn

 
I would check the Network Utility TCP/IP to make sure it is enable.
 
I have checked both the client and server network utilities. Both have tcp/ip enabled and are supposedly listening on port 1433.
 
Have a look at this thread:

thread962-1024298

Very similar situation - the server network utility was showing as listening on TCP/IP but in the SQL log it only said it was listening on Shared Memory and Named Pipes.

Installing SP3 solved the problem.

--James
 
I have a feeling it might be with the antivirus on the systems.

I have symantec internet security 2003 on the laptop with which I can allow the traffic I choose on the network to the laptop.

All the pc's that stay at the office have Symantec antivirus corporate edition. There is a software firewall that comes along with the symantec corporate edition, but it is not installed on the pc's as we have a hardware firewall for any external traffic.

I have not found a way to check if this could be the problem in the symantec corporate yet.
 
Check the SQL log and verify there is a line something like:

- SQL Server is listening on TCP/IP, Shared Memory, Named Pipes
- SQL Server is listening on x.x.x.x:1433, 127.0.0.1:1433

If not, see above thread (install SP3?).

If so, open a command prompt on the machine you're trying to connect from and enter:

Code:
telnet <sql server name/ip address> 1433

If you get a blank screen with flashing cursor the port is open. If you get an error something is blocking the port.

--James
 
Thanks guys. Got it working. You were right SP3 had been downloaded on that server but not applied. Thanks for the help

-Shawn
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top