Network/OS Freeze Performing Operations

Gigabyte / G31m-es2l
September 22, 2009 at 18:32:53
Specs: Microsoft Windows Server 2003 R2 Enterprise Edition, 2.666 GHz / 2046 MB
Hello all,

I have an odd problem I would like some advice with. The server seems to freeze when performing certain network connection operations. I have set up a continuous ping to watch network traffic, and when I perform the operation the ping goes from a healthy return to request timed out. While the network is frozen, the system appears to freeze as well - taskbar is unresponsive and clicking on quick launch icons do nothing. When the operation is cancelled (by cancelling or yanking out the network/sync cable), the ping eventually returns to normal, and the taskbar catches up with clicks and the quick launched programs start. There is nothing in the event viewer to indicate a problem.

So far, I have noticed this happening with:

Connecting to a local (but not remote) MySQL installation
Connecting to MSN (both Miranda and Trillian)
Connecting my smartphone using Active Sync - device connects ok then causes hang during "Looking for changes".

I have tried installing a new network card incase it was an onboard nic issue but the problem persists. I have tried a few hotfixes that sounded relevant, but nothing helped.

I am curious to investigate what is causing this problem, so any insights that you can offer to help me narrow down the problem would be greatly appreciated. I imagine there is commonality to the connection method in these cases, and it is causing a conflict somewhere.

Thanks for your time,

See More: Network/OS Freeze Performing Operations

Report •

September 23, 2009 at 07:16:34
I have set up a continuous ping to watch network traffic,

That won't really help you watch network traffic. What you need to do is install the Wireshark packet sniffing tool on your server and run it. Watch the traffic on the server's network interface.

Since you've already examined Event Viewer, I would start by running packet sniffer. Begin a capture and then try to make the system freeze. Once that's done, end the capture and have a look at the traffic and see what you can find.

This could issue could be related to hardware or software running on the server but I think the best place to start looking would be at the actual packets.

Report •

September 28, 2009 at 16:39:38
Thanks for the info. I will have a look and see what I can sniff out.

Report •

Related Solutions

Ask Question