Problem: SQL Server does not accept TCP connections

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: Internal TCP/IP send buffer?
    ... and that has to be decided at your proxy server. ... UDP or a separate TCP connection to the target and periodically ... connections) constitutes a completely different source of latency. ...
    (microsoft.public.win32.programmer.networks)
  • Re: Netzwerkproblem GBit -> 100MBit
    ... GBit-Kette - flow control zwingend notwendig sei. ... zwischen Client und Server. ... Das kann TCP an der Stelle nicht mehr leisten. ...
    (de.comp.sys.novell)
  • Re: RWW Unavailable
    ... SharePoint 444 TCP ... RWW 4125 TCP ... what did you use for your Web Server Certificate? ... This would really look like a router fault if I didn't have the same ...
    (microsoft.public.windows.server.sbs)
  • suspect bug in vge(4)
    ... The high-level view of the problem is that the client seems to stall ... HTTPS server. ... not only printed for TLS/SSL issues but simply also for broken TCP ... To me it sounds like a broken implementation of hardware generated ...
    (freebsd-current)
  • Re: Log Out Issues
    ... UDP is the way to go for internet games. ... Apparently the extra overhead in TCP can cause a lot more lag in your game, ... >> Lets say the client sends a log out request to the server reliably. ...
    (microsoft.public.win32.programmer.networks)