BRONZE PARTNER:
BRONZE PARTNER:
Industry News:
| |
| |
|
|
|
|
|
| SMS FAQ: Cannot Remote Control Some Clients, but Can Remote Control Others from Them |
|
|
|
By: Cliff Hobbs
Posted On: 8/2/2002
Problem:
I have a problem where I can't Remote Control some clients, yet I can Remote Control other clients from the machines that I can't Remote Control. For example, Computer A can Remote Control Computer B, but Computer B can't Remote Control Computer A.
Resolution:
A couple of possibilities here:
- This is probably due to the fact that the clients are listening on a different IP port number.
Re-installing the SMS Admin Console should resolve this problem. You can check which port your clients are listening on by following the procedure in
How to tell which Port a Client is Listening on for Remote Control.
- This problem can also be caused by poor connectivity to the SQL server which authenticates the security rights to the specific client. It's been seen on several occasions that where an admin machine that is a long distance from the SQL server/ SMS database (or across a slow link), will fail to Remote Control a client that is literally on the same subnet as the admin machine. The important issue is connectivity/ speed from the admin machine to the (authenticating) SQL server/ SMS database - not the proximity of the client to the admin machine. To see if this is the problem try to establish the same connection directly through "REMOTE.EXE" with the "/SMS:NOSQL" switch as though you were attempting this through the MMC.
For example:
REMOTE.EXE 0 <Resource_ID> /SMS:NOSQL
If connectivity to the SQL server was the problem, and the above command line is able to establish the connection successfully, then THAT was the problem.
|
|
|
|
|
|
