Article ID: 312512 - View products that this article applies to.
This article was previously published under Q312512
This article has been archived. It is offered "as is" and will no longer be updated.
After a Systems Management Server (SMS) 2.0 client is discovered with Network Discovery and installed by using a Microsoft Windows NT Remote Client installation, any later discovery by using Network Discovery creates the following error in the Netdisc.log on the site server:
ADM: NtBrowser: Failed to create an anonymous connection to device
Service Pack InformationTo resolve this problem, obtain the latest service pack for Microsoft Systems Management Server 2.0. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/288239/EN-US/ )How to Obtain the Latest Systems Management Server 2.0 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.
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, submit a request to 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:
http://support.microsoft.com/contactus/?ws=supportNote The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language. The English post-SP3 version of this fix should have the following file attributes or later:
NOTE: Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.
Date Time Version Size File name Platform ------------------------------------------------------------------ 01-Mar-2001 22:50 2.0.1493.3222 202,512 Ad_adm.dll Alpha 01-Mar-2001 22:50 2.0.1493.3222 125,712 Ad_cntrl.dll Alpha 01-Mar-2001 22:50 2.0.1493.3222 125,200 Ad_sim.dll Alpha 01-Mar-2001 22:50 2.0.1493.3222 346,384 Ad_utils.dll Alpha 01-Mar-2001 22:50 2.0.1493.3222 77,584 Netdisc.dll Alpha 01-Mar-2001 22:50 2.0.1493.3222 120,160 Ad_adm.dll Intel 01-Mar-2001 22:50 2.0.1493.3222 69,440 Ad_cntrl.dll Intel 01-Mar-2001 22:50 2.0.1493.3222 76,128 Ad_sim.dll Intel 01-Mar-2001 22:50 2.0.1493.3222 205,776 Ad_utils.dll Intel 01-Mar-2001 22:50 2.0.1493.3222 48,112 Netdisc.dll Intel
To work around this problem, stop, and then restart the SMS_Executive service on the site server.
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 Systems Management Server 2.0 Service Pack 5.
SMS now uses the existing connection if the anonymous connection does not work, which is typically either the SMS Service Account or the SMS Client Remote Installation account. The connection is made during a remote client installation.
Also, if anonymous connections are turned off on the target computer, SMS uses the SMS service account to connect during Network Discovery. For additional information about a related topic, click the article number below to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/311257/EN-US/ )SMS: Resources Are Not Discovered if Anonymous Connections Are Turned Off
Hotfix Installation InstructionsApply the fix in this article to all sites in the SMS hierarchy. After the fix is installed, update the collections that are affected by the problem at the site where it was created. To install the fix, use one of the following methods.
How to Use the Hotfix InstallerNOTE: You can use this method only on Intel-based computers.
How to Manually Install the Hotfix