|
|
< Day Day Up > |
|
When you use Remote Tools, the SMS Administrator Console computer and the client computer must share a common protocol. At first glance, this requirement probably seems obvious. However, it's important to note that when the client agent is installed, it automatically binds to the primary protocol on the client computer, and this is the protocol under which the Remote Tools session will be attempted. SMS 2003 clients listen only for TCP connection attempts. However, NetBIOS and IPX connections are made for backward compatibility with SMS 2.0 clients. The remainder of this discussion is apropos for SMS 2.0 clients.
Suppose that the SMS Administrator Console computer has TCP/IP installed and the SMS 2.0 client computer has NetBEUI and TCP/IP installed, with NetBEUI as the primary protocol. In this case the Remote Tools Client Agent will use NetBEUI as its protocol. When a Remote Tools session is attempted, it won't be established because the SMS Administrator Console computer and the client don't have a common Remote Tools protocol.
| Note |
You can either change the protocol order on the client or reconfigure the settings in the Advanced tab in the Remote Tools Client Agent Properties window to use a different LANA number. The problem, of course, is that these settings are sitewide, and perhaps not all your clients experience the same problem. Changing the LANA number might clear up the issue for some SMS 2.0 clients and introduce it for other clients. |
A similar issue might arise if your network has clients with more than one NIC installed. By default, the Remote Tools Client Agent binds to the first NIC in the binding order. Changing the NIC to which the client agent binds varies depending on platform.
On Windows clients, using the Registry Editor, locate the key HKEY_LOCAL_ MACHINE\Software\SMS\Client\Client Components\Remote Control. Add new string type values to this key named Subnet and SubnetMask, each containing the appropriate address value for the NIC you want the agent to bind to. This forces the client agent to bind to the NIC specified by the subnet and subnet mask.
As an SMS administrator, you might need to diagnose a problem or assist a client over a RAS connection. Remote Tools enables you to connect to client computers over such connections. Consider the following requirements when you're using Remote Tools over RAS:
To use Remote Tools over a RAS connection, the link should be at least 28.8 Kbps. Keep in mind that this is a minimum specification-as with any remote connection, faster is better. Also, remember to disable any wallpaper settings.
The SMS Administrator Console computer will connect to the RAS server, so you must install and configure the RAS client software on this computer.
The SMS Administrator Console computer, the RAS server, and the remote client computer must be running the same transport protocol.
At the site containing the remote client, a RAS server must be located on the same LAN as the remote client computer.
|
|
< Day Day Up > |
|