Article ID: 229894 - Last Review: February 27, 2007 - Revision: 3.6 CSNW Experiences Delays Opening Files on the NetworkThis article was previously published under Q229894 IMPORTANT: This article contains information about modifying the registry. Before you
modify the registry, make sure to back it up and make sure that you understand how to restore
the registry if a problem occurs. For information about how to back up, restore, and edit the
registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986
(http://support.microsoft.com/kb/256986/EN-US/
)
Description of the Microsoft Windows Registry
On This PageSYMPTOMS
When Client Services for NetWare (CSNW) opens Microsoft Office files, delays may occur. The problem generally occurs when you are opening files on NetWare servers.
CAUSE
This problem occurs because CSNW continually resolves printer names, server names, and object properties. This results in poor performance. The problem becomes more pronounced as more and more clients perform the queries.
RESOLUTIONWindows NT Server or Workstation 4.0To resolve this problem, obtain the latest service pack for Windows NT 4.0 or the individual software update. For information on obtaining the latest service pack, please go to:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS
(http://support.microsoft.com/default.aspx?scid=fh;en-us;cntactms)
Windows NT Server 4.0, Terminal Server EditionTo resolve this problem, obtain the latest service pack for Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:152734
(http://support.microsoft.com/kb/152734/EN-US/
)
How to Obtain the Latest Windows NT 4.0 Service Pack
Windows 2000To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:260910
(http://support.microsoft.com/kb/260910/EN-US/
)
How to Obtain the Latest Windows 2000 Service Pack
The English version of this fix should have the following file attributes or later:
Date Time Version Size File name ------------------------------------------------------------ 8/6/2001 04:15p 5.0.2195.4069 160,208 Nwrdr.sys 8/6/2001 04:15p 5.0.2195.4069 160,208 Nwrdr.sys STATUSWindows NT 4.0Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows NT Server version 4.0, Terminal Server Edition Service Pack 6.Windows 2000Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows 2000 Service Pack 3.MORE INFORMATIONWARNING: If you use Registry Editor incorrectly, you may cause serious problems that may
require you to reinstall your operating system. Microsoft cannot guarantee that you can solve
problems that result from using Registry Editor incorrectly. Use Registry Editor at your own
risk. These values can be modified in the following registry key: HKEY_LOCAL_MACHINE\SYSTEMCurrentControlSet\Services\NwRdr\Parameters
The NdsObjectCacheSize value should be tuned to the number of resources that you are connecting.
Value: NdsObjectCacheSize
The NdsObjectCacheTimeout value should be set according to how often the resources can change. Start with a value of 10.
Type: REG_DWORD Data: number of objects to cache Min: 0x0 Max: 0x80 Default: 0x0
Value: NdsObjectCacheTimeout Type: REG_DWORD Data: number of seconds an entry is valid Min: 0x0 Max: 0x258 Default: 0xa APPLIES TO
| Article Translations
|
| United States | Change | | | All Microsoft Sites |
Back to the top
|
