Remote Control does not work even if other remote tools are successful (276378)


The information in this article applies to:

  • Microsoft Systems Management Server 2.0
This article was previously published under Q276378

SYMPTOMS

When you try to initiate a remote control session to a client computer, the remote control icon may be depressed, but a remote control session may not be established. However, all other remote tools may appear to be working properly.

CAUSE

This issue can occur in situations where a remote administration console has been connected to a parent primary site and can successfully remote control a Systems Management Server (SMS) client of a child primary site. However, after that same administration console is connected to the child primary site's database, the remote control button can be depressed but never successfully connects. The difference is that the remote administration console is now connecting to the provider on the child site. Security requests are made from that child site's server or the server that contains the provider for that child site.

RESOLUTION

To resolve this issue:
  1. Go to the server that contains the provider for the database that the administration console is directed to when remote control does not work. If SQL and the site server are on the same computer, go to the SMS Site Server computer.
  2. Use the NLTEST tool to determine which domain controller has established a secure channel. If this domain controller is not local to the server that you located in step 1 of the preceding Microsoft Knowledge Base article, this could be causing some network latency.

  3. Use the Setprfdc.exe tool that is included with Microsoft Windows NT 4.0 Service Pack 4 to set the secure channel to a local domain controller, and then try to initiate a remote control session again.
NOTE If the preceding steps resolve the issue, you must ensure that the secure channel is always set to a local domain controller. For additional information about how to ensure that the secure channel is always set to a local domain controller, click the article number below to view the article in the Microsoft Knowledge Base:

181171 Secure Channel Manipulation with TCP/IP

Also, determine if there are multiple network adapters in the server you located in step 2 of this article. If there are, try disabling the second network adapter, and then restart the server. After the reboot, check the secure channel to see if it is set to a local domain controller.

IMPORTANT: It is very important that the WINS server contain a proper record for this local domain controller.
Modification Type:MinorLast Reviewed:6/14/2005
Keywords:kbClient kbHelpDesk kbprb kbRemoteProg kbServer kbsmsAdmin kbsmsUtil kbWBEM KB276378
©2004 Microsoft Corporation. All rights reserved.