The very first thing : have you installed the latest servicepack for NT ? If yes, check the binding order of the Network,
sometime it happens that Nt has a problem binding a protocol to the NIC.
An other suggestion may be in the Technet Q148426
- Either busy and cannot respond before the rdr timeout
- The network could be busy
- Bottleneck in the network
As to troubleshooting this problem, you may want to exhaust all means before
deciding to increase the amount of time before the redirector stops
(SESSTIMEOUT). The SESSTIMEOUT parm can be set in the following registry
location:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters
Some things you can try are to obtain a trace of the packets on the network. You
want to zoom in on the amount of time it takes for the Server to respond back to
the workstation.
Another idea is to perform what ever operations that was done backwards. If you
were connecting to ServerA from ServerB, try connecting to ServerB from ServerA.
Also have another client attempt to connect to the same server to see if both
redirectors have the same problem connecting to the same server.
You may also want to check the following items:
- Check to see that the latest network driver is installed.
- Check to determine whether the network adapter has a configuration utility
that allows tuning parameters. If so, try maximizing the network performance.
