NetIQ AppManager server cannot communicate with your NetIQ AppManager client on Windows XP Service Pack 2 (873183)


The information in this article applies to:

  • Microsoft Windows XP Professional Service Pack 2 (SP2)
  • Microsoft Windows XP Home Edition SP2
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 Description of the Microsoft Windows Registry

Important This article contains information that shows you how to help lower security settings or how to turn off security features on a computer. You can make these changes to work around a specific problem. Before you make these changes, we recommend that you evaluate the risks that are associated with implementing this workaround in your particular environment. If you implement this workaround, take any appropriate additional steps to help protect your system.

SYMPTOMS

The NetIQ AppManager 5.0.1 server may not be able to monitor or communicate with your NetIQ AppManager client that is installed on a computer that is running Microsoft Windows XP Service Pack 2 (SP2). When you view the Master tree in the NetIQ AppManager console on the NetIQ AppManager server computer, the icon that represents your NetIQ AppManager client computer may be shaded. The shaded icon indicates that your client is disconnected.

CAUSE

This problem occurs because the NetIQ AppManager server program explicitly tries to set up an anonymous connection with the client. By default, Windows XP SP 2 does not permit anonymous connections.

WORKAROUND

Warning 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.
Warning This workaround may make your computer or your network more vulnerable to attack by malicious users or by malicious software such as viruses. We do not recommend this workaround but are providing this information so that you can implement this workaround at your own discretion. Use this workaround at your own risk.
To work around this issue, add SRVSVC to the NullSessionPipes entry on the computer that is running Windows XP SP2. To do this, follow these steps:
  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate and then click the following subkey in the registry:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Lanmanserver\Parameters

  3. On the right pane, right-click NullSessionPipes, and then click Modify.
  4. Click below the last entry in the NullSessionPipes list, type SRVSVC, and then click OK.
  5. Quit Registry Editor.

MORE INFORMATION

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.
Modification Type:MinorLast Reviewed:8/27/2004
Keywords:kbRemoting kbAppCompatibility kbnetwork kbconnectivity kb3rdparty kbtshoot kbprb KB873183 kbAudITPRO kbAudEndUser
©2004 Microsoft Corporation. All rights reserved.