Article ID: 330929 - View products that this article applies to.
This article was previously published under Q330929
Microsoft Windows NT-based and Microsoft Windows 2000-based servers continue to communicate file system changes to Windows XP-based clients even if an Explorer.exe window is not open on the client. This may cause extra traffic over a wide area network (WAN). This issue does not occur until the Explorer.exe window on the client is opened to a share on the server and then closed.
Network Monitor shows the following excessive SMB Notify Change traffic:
Client request SMB: C NT transact - Notify Change Server response SMB: R NT transact
Service pack informationTo resolve this problem, obtain the latest service pack for Microsoft Windows XP. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/322389/EN-US/ )How to obtain the latest Windows XP service pack
Hotfix informationA supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
Date Time Version Size File name -------------------------------------------------------------------- 01-Nov-2002 22:46 6.0.2600.105 8,223,232 Shell32.dll (pre-SP1) 01-Nov-2002 17:07 6.0.2800.1137 8,239,104 Shell32.dll (with SP1)
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/322756/ )How to back up and restore the registry in Windows
After you apply this hotfix, you can add a new
NoRemoteRecursiveEventsvalue to the Windows registry to turn off Change Notify requests for file and folder changes that occur in subfolders of a mapped network share. When you set this registry key, the server still sends a Change Notify event when a file or folder is changed in the root of the mapped network share. However, the server does not send a Change Notify event when a change is made in the second sub-folder or deeper of the mapped network share. By default, the setting for the
0. You can add the
NoRemoteRecursiveEventsvalue to either of the following registry keys:
If you add
NoRemoteRecursiveEventsvalue to the
HKEY_CURRENT_USERhive, the setting is applied only for the currently logged on user. If you add the
NoRemoteRecursiveEventsvalue to the
HKEY_LOCAL_MACHINEhive, the setting is applied for all users who log on to the computer.
How to Turn Off Change Notify Requests for the Currently Logged On User OnlyFollow these steps, and then quit Registry Editor:
How to Turn Off Change Notify Requests for All UsersFollow these steps, and then quit Registry Editor:
Microsoft 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 Microsoft Windows XP Service Pack 2.