meastaugh1
Technical User
- Apr 21, 2002
- 316
I have a Win2K SP4 DC, hosting FSMO, DHCP, DNS et al. Every few days the server will freeze. By this I mean, IIS will stop delivering pages, clients sometimes experience problems accessing shares hosted on the server, drives do not appear in My Computer, and DNS stops servicing requests. Attempts to logoff or restart the server will result in it hanging and never completing the operation. Stopping a service will invariably result in it sticking in the 'Stopping' state.
If I try to use the server interactively when it's in this state, the interface performance will rapidly degrade and applications become unresponsive. I've found that if I disable the network adapter, then re-enable, the server comes back to life. However, it fails to service DNS requests correctly, restarting the DNS server fixes this. If I physically unplug the network connection, or disable/enable the connection at the switch end, this does not fix the problem. It seems to be something specific about disabling/enabling the connection on the server.
I've tried using another network interface on the server, with the same results. To me, this would suggest it's a software problem. My support provider suggested the server had too many TCP connections in the TIME_WAIT state. I've reduced the number of connections, plus adjusted the registry to reduce the amount of time that connections be in this state, but this hasn't made any difference.
The problem's been apparent for over a year now. When I first experienced it, the problem would occur once every 1-2 months. Now, it's guaranteed to happen at least once a week.
Any suggestions or thoughts on this would be very welcome. Thanks
If I try to use the server interactively when it's in this state, the interface performance will rapidly degrade and applications become unresponsive. I've found that if I disable the network adapter, then re-enable, the server comes back to life. However, it fails to service DNS requests correctly, restarting the DNS server fixes this. If I physically unplug the network connection, or disable/enable the connection at the switch end, this does not fix the problem. It seems to be something specific about disabling/enabling the connection on the server.
I've tried using another network interface on the server, with the same results. To me, this would suggest it's a software problem. My support provider suggested the server had too many TCP connections in the TIME_WAIT state. I've reduced the number of connections, plus adjusted the registry to reduce the amount of time that connections be in this state, but this hasn't made any difference.
The problem's been apparent for over a year now. When I first experienced it, the problem would occur once every 1-2 months. Now, it's guaranteed to happen at least once a week.
Any suggestions or thoughts on this would be very welcome. Thanks