Server Listing for TCP connection

I'm having trouble with an ODBC User that can't connect to 2003
Windows Server with SQL2000.

The ODBC fails when he tries to contact with TCP client connection.
When I view the Network Connection it is displaying TCP is checked,
but when I view the error log is doesn't display that it is listening
for TCP.

Is there any way to prove that my TCP connections are working
correctly or a way to make sure that my SQL server is listening for
TCP?

Thanks for reading my note and any help with this issue is greatly
appreciated.
.

Relevant Pages

  • Re: WSUS ports
    ... Tcp 80 if you have not configured use of SSL else Tcp 443. ... Roger Abell ... Microsoft MVP (Windows Server: Security) ...
    (microsoft.public.security)
  • Re: Inbound connections limit in Windows XP
    ... > Does anybody have practical experience with this limitation at TCP ... > for kicking out client connections, and does he then have to take ... > into account the number of clients on other services (file sharing, ... It means that Microsoft would prefer that you use Windows Server as the ...
    (borland.public.delphi.non-technical)
  • [Full-disclosure] Cisco PIX TCP Connection Prevention
    ... Cisco PIX TCP ... Connection Prevention, posted on November 22, 2005. ... By sending a TCP SYN packet with an incorrect checksum through a PIX ...
    (Full-Disclosure)
  • [Full-disclosure] Cisco PIX TCP Connection Prevention
    ... Cisco PIX TCP ... Connection Prevention, posted on November 22, 2005. ... By sending a TCP SYN packet with an incorrect checksum through a PIX ...
    (Full-Disclosure)
  • [NEWS] Cisco PIX TCP Connection DoS
    ... Get your security news from a reliable source. ... By crafting a special TCP packet and sending it to a vulnerable Cisco PIX, ... embryonic connection open until the embryonic connection timeout which is ...
    (Securiteam)