Re: Problem: SQL Server does not accept TCP connections

Its not listening on TCP for some reason...verify that you have SQL Server
sp3 or higher (I know you say you have SP4) by looking at the file version
of sqlservr.exe on the server

--
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm

Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com


"Ezequiel" <ezequiel.naftali@xxxxxxxxx> wrote in message
news:1167922343.027575.146800@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi,
I have a W2k3 with SQL Server 2000 SP4. I have configured the server
to use named pipes and TCP on 1433 (at least that is what the registry
and server configuration tool say)
However the server does not accept tcp connections (i tried with
telnet, query analyzer, etc).
Log says the following:

2007-01-03 19:12:55.85 server SQL server listening on Shared Memory,
Named Pipes.

0
2007-01-03 19:12:55.85 server SQL Server is ready for client
connections


Is this a SQL Server BUG or i am doing something wrong?

Thanks,

Ezequiel Naftali
enaftali@xxxxxxxxxxxx



.

Relevant Pages

  • Re: installing SQL 2008 x64 on Vista Enterprise x64-Firewall warnings
    ... I can't see the warning at the moment but my recollection is that is just warns you that the firewall is on and you might have to configure it. ... Since setup doesn't know what you want to do with SQL Server it can't tell if you have configured it correctly. ... How can I get rid of this warning and continue with my installation? ... 135 TCP - SQL Server Integration Services ...
    (microsoft.public.sqlserver.setup)
  • installing SQL 2008 x64 on Vista Enterprise x64-Firewall warnings
    ... I am installing default instance of SQL Server 2008 x64 on Windows Vista ... Firewall" generated a warning. ... How can I get rid of this warning and continue with my installation? ... 135 TCP - SQL Server Integration Services ...
    (microsoft.public.sqlserver.setup)
  • Re: SQL Server 2000 SP4 client connection problem
    ... If you can connect locally using TCP, the SQL Server must be listening on TCP properly. ... And if you see the connection attempts in the log, then TCP/IP must be passing something to SQL Server. ...
    (microsoft.public.sqlserver.connect)
  • Re: TCP Connectivity Issue
    ... No firewalling between them though.. ... It's only TCP connectivity on ... When users try to connect to SQL server they get error: ...
    (microsoft.public.sqlserver.connect)
  • RE: Cannot connect to MSDE on a W2003 server
    ... Did you apply the SP3 version of MSDE? ... If not TCP will be disabled on ... Do both remote and local connections fail for each protocol? ... Click the desired instance of Microsoft SQL Server 2000 Desktop Engine ...
    (microsoft.public.sqlserver.connect)
Loading