TCP connections suddenly failing.

I am running a large mission critical application on a cluster. This
is a 2003 server latest SP with SQL 2000 Enterprise latest SP also.

This app has run for years with little change. Today at around 3:00
all connections stopped coming in.

After some debugging, we found that we could connect with named
pipes., but not TCP. TCP has been the default protocol for years.

We have the server monitored and no changes occurred recently. The
server has not been rebooted in months, and the last time the instance
was restarted was two months ago.

What can cause a server that has run reliably using TCP for years to
stop accepting TCP connectionsl suddenly?

The errors I am getting is a handshake error trying to connect locally
using TCP, and I get a connection failed error remotely.

Connections are instant and lovely using named pipes.

Thanks for any help.

.

Relevant Pages

  • Re: TCP/IP redundant connections
    ... The clients have persistent TCP connections to the server, ...
    (freebsd-hackers)
  • Re: freebsd-hackers Digest, Vol 233, Issue 3
    ... The clients have persistent TCP connections to the server, ... So I want to utilize IP-sharing and TCP-connection synchronization ...
    (freebsd-hackers)
  • Re: Component Efficiency
    ... Desktop OSes have TCP backlog limit of 5 outstanding ... TCP connection attempts, e.g. up to five clients may be ... simultaneously establishing connections. ... suitable for any kind of TCP server, ...
    (microsoft.public.win32.programmer.ole)
  • Re: Upgraded Win2K/ SQL 2K to Win2K3, is now one big mess
    ... TCP/IP and named pipes are both enabled, ... The TCP/IP and Named Pipe protocols need to be enabled. ... > I installed Small Business Server at home, ... the existing server connections still ...
    (microsoft.public.sqlserver.odbc)
  • 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)