TCP/IP sockets not disconnecting in 2003

Hi, we're experiencing a strange problem when trying to simulate network
failures on our Windows 2003 domain. When we physically pull out network
cables from a server (any server), the server thinks that the TCPIP socket
connection is still active. When you do a 'netstat', it still shows the
socket links to any other servers as being 'ESTABLISHED', even though you
can't ping anything, as it is physically disconnected. It does loose the name
resolution in the netstat display, so i guess it knows that it can't see the
DNS server anymore - It just replaces the server names with the IP addresses.

Our application needs to know as soon as a network socket has gone down for
redundancy purposes, and this is causing a bit of grief. Any thoughts?

Thanks,
Phil

I think the software boys have sorted this one now. Seems it was their code
that was the problem, rather than anything wrong Windows. Typical - always
pointing the finger at the system manager.


"Phil" wrote:

> Hi, we're experiencing a strange problem when trying to simulate network
> failures on our Windows 2003 domain. When we physically pull out network
> cables from a server (any server), the server thinks that the TCPIP socket
> connection is still active. When you do a 'netstat', it still shows the
> socket links to any other servers as being 'ESTABLISHED', even though you
> can't ping anything, as it is physically disconnected. It does loose the name
> resolution in the netstat display, so i guess it knows that it can't see the
> DNS server anymore - It just replaces the server names with the IP addresses.
>
> Our application needs to know as soon as a network socket has gone down for
> redundancy purposes, and this is causing a bit of grief. Any thoughts?
>
> Thanks,
> Phil