But it sure couldn't hurt to turn off the power-saving features on the NIC if they are on. Windows isn't so "logical" calculating times, sometimes.
I often get "Not responding" in explorer, then it responds. Maybe, internally, 'not responding' is a condition to turn off the NIC.

good luck


>>Well I believe it could happen if the application's NIC has power-saving turned on.
>>
>>Long ago I also saw similar reports, and other strnge things, if the server is handling a large print job, as a priner server, at the same time.
>
>This is a robot application which handles requests across that connection every minute. So, the possibility of having a NIC power-saving is probably impossible. However, the other assumption could apply. Sometimes, the robot application will execute big process and maybe this could cause that.
>
>FWIW, I also have another application running on the secondary server and when it happens to the other application, it causes the same behavior on that application. Both, once I restart them again, will work ok.