IBM 3.8 Garage Door Opener User Manual


 
158 IBM Tivoli Remote Control Across Firewalls
From this log we are able to gather information regarding the Proxy name, Proxy
type, the number of sessions that this Proxy can handle at the same time, and
the communication status.
The last few lines of the rcproxy.log, marked in bold, show that the
communication between Controller and Target Proxy is working.
5.2.2 The remcon.trc
This is a generic trace file used to log information related to the Remote Control
Controller or Target machine.
On Windows platforms, for example, you can enable the logging of remote
control events or errors that occur during a session by setting the keywords of
the GENERIC section in the <Windows_installation_directory>\remcon.ini
file of the Controller and Target workstation.
By default, the debug level of this file is set to 0 (disabled), but this can be
changed to different values. For more information on this matter, you can refer to
the
IBM Tivoli Remote Control Users Guide
, SC23-4842.
In this section we analyze the Controller trace file only, since the objective is to
verify if the Controller is connecting to the Target Proxy.
Controller trace file
The remcon.trc could be useful when the proxies communication is working but
we are still not able to attempt a remote control session through the firewall. The
problem, in this case, could be in the Controller area. It could be possible that the
Controller is not able to connect to the Target Proxy.
Example 5-4 shows the remcon.trc file of Controller machine. From this file, we
need to look at the following parameter settings:
/C Identifies the Target Proxy port (rc_def_proxy policy method)
/B Identifies the Endpoint object dispatcher number
/D Identifies the Gateway Proxy this Endpoint belongs to (if any is specified)
Verify they are the correct ones, comparing them with the rc_def_proxy policy
method and rcproxy.log (Target Proxy):
Example 5-4 The remcon.trc file for the Controller machine
[2808] Thu Feb 06 17:10:45 2003 3 found /C parameter
[2808] Thu Feb 06 17:10:45 2003 3 Proxy port is: [5020]
[2808] Thu Feb 06 17:10:45 2003 3 found /E parameter
[2808] Thu Feb 06 17:10:45 2003 3 found /B parameter