Remote connection timed out!

Hi all. I have an issue with this Win2k Server SP4 and its like a needle in the haystack! The problem is that it has started to stall intermittently. At the time of stall, when I try remote connecting to it, it comes up with a message "Remote connection has timed out ". See below linked screenshot taken at the time of stall.

Screenshot RDP timed out

This message appears every time whenever there is a stall and I try remote connecting to the server. An attempt made by network team was to disable Hyper threading on the server and as a result the duration of stall from 1-2 min to 30-40 secs. But then after re-enabling the hyperthreading the stalls continued to be at 30-40 stalls so not sure if HT-enablement was behind change of duration of stall.

A few more findings by Network team are:

1. Network connectivity: Pinging & tracert batch file results (at the time of stall) showed that network connectivity was present throughout stall.
2. No packet loss has been confirmed so that is also ruled out.
3. Hardware diagnostics went fine. No issue here.
4. That anti virus activity was disabled to see if it helps - it had no effect whatsoever.
Any thoughts to help solve the issue are more than welcome..

Thanks.

 

G'Day johntheguru,

Just a guess, disable any screen savers on both machines, and any other Automated utilities from Windows, like Windows or Microsoft Updates (turn this to OFF) and any other Automatic updates or Utilities like Virus definition or program updates and or Defragmenter programs that may be set on Stealth (performs defrag during idle times which is interpreted by these, when there is no keyboard activity) also disable any Scheduled activity if you have set any. Part of these automated programs are any running email programs (active) that are set to pickup mail every ? minutes, i.e. don't leave them running and close them immediately after use.

All these can be done manually during this testing configuration of Disabling all of the above, and with no outside interference of other utilities or programs trying to use the WAN or access other remote sites by consequence of their function needing to do so, we may be able to isolate the problem.

Then perform your remote connection and see if it still behaves this way.

pcbugfixer