Microsoft KB Archive/305164

= SMS: Remote Control Clients That Are Configured for NetBIOS May Not Be Contacted by the Administrator Console =

Article ID: 305164

Article Last Modified on 10/27/2006

-

APPLIES TO


 * Microsoft Systems Management Server 2.0 Standard Edition
 * Microsoft Systems Management Server 2.0 Service Pack 1
 * Microsoft Systems Management Server 2.0 Service Pack 2
 * Microsoft Systems Management Server 2.0 Service Pack 3
 * Microsoft Systems Management Server 2.0 Service Pack 4

-



This article was previously published under Q305164



SYMPTOMS
Systems Management Server (SMS) 2.0 clients that are configured to use NetBIOS for remote control (instead of TCP/IP) may not be found when you try a remote control session from an SMS Administrator console. You receive a &quot;Remote Control Agent not found&quot; error message when you try a remote control session. If you run the netstat -a command on the target client, you see that Wuser32 is registered by using an uppercase NetBIOS name. If you view a Network Monitor capture from the Administrator console, you see that the Remote.exe process is trying to contact the Remote Control agent by using a lowercase NetBIOS name. This causes the Administrator console not to be able to connect to the client.



CAUSE
The NetBIOS name that is stored in the SMS database for the client uses lowercase letters. The problem occurs if the site server uses only network discovery and if Domain Name System (DNS) is being used for name resolution. When network discovery creates the discovery record for a computer, the name is recorded in lowercase letters. Network discovery obtains the lowercase entry from DNS, which can store information in lowercase letters.

You can also confirm that the client's resource information is in lowercase letters by starting the SMS Administrator console, expanding Collections, expanding All Systems (or any collection in which this computer name appears), and then locating the client. If the client is listed in lowercase letters, the problem may occur.



RESOLUTION
To 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:

288239 How to Obtain the Latest Systems Management Server 2.0 Service Pack

Hotfix Information
A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Systems Management Server service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS

NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix should have the following file attributes or later:   Date       Time   Version         Size     File name   Platform ---  01-Mar-01  15:00  2.00.1493.3212   78,944  Remote.exe  I386 01-Mar-01 15:00  2.00.1493.3212  127,760  Remote.exe  Alpha NOTE: Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.



WORKAROUND
To work around this problem, use either of the following methods:
 * Configure the site to use TCP/IP as the default remote access protocol.
 * Use Remote.exe at a command prompt to manually change the NetBIOS name to uppercase letters. For example, type Remote 3 SERVER1.



STATUS
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.

Additional query words: prodsms communicate connect

Keywords: kbsms200presp5fix kbdiscovery kbbug kbfix kbsms200fix KB305164

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.