Filter
Top Products
142 IBM Tivoli Remote Control Across Firewalls
5.1 Generic problem determination outline
To obtain an overall picture of what is happening on the IBM Tivoli Remote
Control side when a session is established through a firewall, there are several
troubleshooting steps to follow and logs that need to be analyzed.
You could face problems during:
Session startup
Session management
In order to help you isolate problems you experience with the Remote Control
Proxies, we provide general troubleshooting guidelines and processes that may
offer you a way to organize your problem determination strategy.
5.1.1 Session startup
As soon as the Remote Control Tool is started, the pcremote process is
triggered. It performs several checks before starting the session and connecting
the RC Controller to the RC Target machine. All the steps performed by the
pcremote process are tracked in the pcremote trace file.
This troubleshooting section does not describe the pcremote traces analysis,
since the objective here is to only debate the proxy's components. Anyway, by
providing general troubleshooting ideas for other items, like the IBM Tivoli
Management Framework, Tivoli Firewall Security Toolbox (TFST), and the RC
Proxies, this can help you to understand the whole picture of the modules
dependencies.
Next, you will find the complete process that is used to determine if there is a
problem with the Remote Control Proxies. As IBM Tivoli Remote Control 3.8 has
been designed to work with both IBM Tivoli Management Framework and the
TSFT, IBM Tivoli Remote Control’s functionality is highly dependent on those
components. Thus, before analyzing any Remote Control logs or trace files, you
need to be sure that any of the IBM Tivoli Management Framework and TFST
components are working properly.