Troubleshooting Event ID 3013

ID: Q148426

The information in this article applies to:

Microsoft Windows NT operating system version 3.1
Microsoft Windows NT Advanced Server
Microsoft Windows NT Workstation versions 3.5, 3.51, 4.0
Microsoft Windows NT Server versions 3.5, 3.51, 4.0

IMPORTANT: This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information about how to do this, view the "Restoring the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key" Help topic in Regedt32.exe.

SUMMARY

WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

For information about how to edit the registry, view the "Changing Keys and Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it. If you are running Windows NT, you should also update your Emergency Repair Disk (ERD).
Error 3013, "The redirector has timed out to SERVERNAME" usually means that the Server that you are attempting to connect to is:

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.

MORE INFORMATION

Valid values for the SessTimeout registry key are:


   SessTimeout   REG_DWORD
   Range: 10 - 65535 seconds
   Default: 45

Additional query words: event id

Keywords : kbnetwork ntnetserv
Version : :; winnt:3.5,3.51,4.0
Platform : winnt
Issue type : kbinfo