General discussion

Locked

Redirector times-out

By wautersnn ·
Hello,

I am experiencing the following problem on my NT LAN:

1. For no apparent reason, the BDC, servers and all PCs loose connection with the PDC and the whole network.

2. The PDC however has no problem accessing the BDC, servers and PCs.

3. The event viewers record the following Redirector error ID 3013: " The redirector has timed out a request to ACL1".

4. The PDC replies to a ping from anywhere on the LAN.

4. My only solution is to reboot the PDC.

Any help will be greatly appreciated.
Nicole

This conversation is currently closed to new comments.

1 total post (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

by compgirlfhredi In reply to Redirector times-out

If an unrecoverable network error occurs while the data is being transferred to the remote server, it may cause the write request to fail and the above application popup to occur.
WARNING: This procedure should first be tested in a non-critical environment before being implemented into a production environment. In general, this change slows down network I/O.
You can disable Network Redirector File Caching by performing the following steps:
Start Registry Editor (Regedt32.exe) and go to the following subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Rdr\Paramete
Click Add Value on the Edit menu.
Enter the following:

Value Name: UseWriteBehind
Data Type: REG_DWORD
Data: 0

1-true 0-false (default: 1)

UseWriteBehind - Enables the write-behind optimization for write Only files.
Go to the following subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services \Lanmanworkstation\paramete
Click Add Value on the Edit menu.
Enter the following:

Value Name: UtilizeNTCaching
Data Type: REG_DWORD
Data: 0

1-true 0-false (default: 1)

UtilizeNTCaching - Indicates whether the redirector uses the cache manager to cache the contents of files. Disable this parameter only to guarantee that all data is flushed to the server immediately after it is written by the application.
Shut down and restart your computer.
MORE INFORMATION
When implementing this change in the registry, it is possible for the mail flow to be disrupted between Microsoft Exchange and Microsoft Mail using the Microsoft Mail Connector if there is an underlying network problem or a slow link. If the change above is made, the mail error will be manifested in the form of an NDR stating:

[005] Mail retry count exceeded Network/Postoffice
Once this registry entry is changed back to the default, mail should flow once again. However, the events will again begin to be registered in Event Viewer.

Back to Windows Forum
1 total post (Page 1 of 1)  

Related Discussions

Related Forums