160 IBM Tivoli Remote C ontrol Across Firewalls
5.3 Troubleshooting examples
In this section we provide a few troubleshooting examples for Remote Control
session startup problems in a TFST environment, using the testing scenario in
Figure4-2.

5.3.1 Case 1: Controller not connecting to Target Proxy

In this case we describe a troubleshooting example of a startup session problem
when the Proxy configuration is not correct. Specifically, the Proxy port specified
in the Target Proxy configuration files does not match with the Proxy port
specified in the rc_def_proxy policy method, and the Controller is not able to
connect to the Target Proxy.
As soon as we start the session, the message box shown in Figure 5-4 is
displayed on the Controller.
Figure 5-4 Error message displayed on Controller when attempt a session
From this point we start the problem determination, following step-by-step the
diagrams reported in 5.1, “Generic problem determination outline” on page 142.
1. Check that both Target and Controller Endpoint are alive and that the
Framework down call works against these Endpoints.
Check the Controller Endpoint:
wep tic01006 status
tic01006 is alive
Check the Target Endpoint:
wep tic01007 status
tic01007 is alive
2. We assume that the Endpoint Proxy, Relay, and Gateway Proxy services and
their communication are working.
3. We assume that both Target and Controller Proxy services are up and
running.
4. We check the Target and Controller Proxy communication by looking at the
Proxy log files.