Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 235174 - Last Review: February 27, 2007 - Revision: 4.6
SMS: Remote Control Connection Issues with Windows 2000 and IP Security
This article was previously published under Q235174
Internet Protocol (IP) security in Microsoft Windows 2000 can cause some connection issues when you try to establish a remote control session. If IP security is enabled on a server, client, or both, you may experience an initial timeout when you try to connect to a client through remote control. It may appear as though the remote control session is unable to establish a connection. Multiple attempts are made, resulting in a connection failure, with the user prompted to retry or cancel. This issue is somewhat random, and its frequency can vary depending on how IP security is configured on the server or client.
To work around this issue and establish a remote control session, follow these steps:
- Ping server-to-client or client-to-server with the command prompt ping utility to allow IP security to establish a connection.
- When the remote control session fails to establish a connection, retry several times to allow IP security to establish a connection.
- Use the nbtstat -a client name command to view information about the computer.
This command fails until an IP security connection is established, after which, information about the computer is displayed.
NOTE:
After a connection is successfully established between a server and client, it should not be necessary to repeat these steps every time a remote control session is attempted between the two computers, because the IP Sec information is cached until shortly after the connection is dropped.
APPLIES TO
- Microsoft Systems Management Server 2003
- Microsoft Systems Management Server 2.0
| kbbug kbclient kbconfig kbhelpdesk kbinterop kbnetwork kbnofix kbprb kbremoteprog kbsecurity kbserver KB235174 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate