This article was previously published under Q328358
This article has been archived. It is offered "as is" and will no longer be updated.
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
Network Discovery does not discover the operating system and version information from client computers that have implemented a
setting of 1. For additional information about the RestrictAnonymous setting, click the following article number to view the article in the Microsoft Knowledge Base:
246261 How to Use the RestrictAnonymous Registry Value in Windows 2000
For example,the Netdisc.log file contains entries that are similar to these for a client named ComputerName:
ADM: NtBrowser: New name ComputerName found on domain DomainName. ADM: DNS: Name ComputerName resolved to address IP Address.
ADM: NtBrowser: New name ComputerName found on domain DomainName. ADM: NtBrowser: Starting to talk to Device ComputerName: ADM: NtBrowser: Failed to retrieve OS info from device ComputerName due to insufficient access.
A 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:
Note 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 version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date Time Version Size File name Platform ------------------------------------------------------------------ 01-May-2002 14:20 2.0.1493.4132 204,048 Ad_adm.dll Alpha 01-May-2002 14:20 2.0.1493.4132 125,712 Ad_cntrl.dll Alpha 01-May-2002 14:20 2.0.1493.4132 125,200 Ad_sim.dll Alpha 01-May-2002 14:20 2.0.1493.4132 347,408 Ad_utils.dll Alpha 01-May-2002 14:20 2.0.1493.4132 77,584 Netdisc.dll Alpha 01-May-2002 14:20 2.0.1493.4132 120,672 Ad_adm.dll x86 01-May-2002 14:20 2.0.1493.4132 69,440 Ad_cntrl.dll x86 01-May-2002 14:20 2.0.1493.4132 76,128 Ad_sim.dll x86 01-May-2002 14:20 2.0.1493.4132 205,776 Ad_utils.dll x86 01-May-2002 14:20 2.0.1493.4132 48,112 Netdisc.dll x86
Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
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.
To use this fix, you must add the following registry key to each site server from which Network Discovery runs. This registry change modifies the account credentials under which Network Discovery tries to connect to the clients. The account credentials are changed from using a null account to using Network Abstraction Layer (NAL) to make sure that the account credentials used have appropriate permissions. When using NAL, Network Discovery will first try the SMS site system connection accounts, and then finally the SMS service account. Add the following value and set its data value to 1: