How to create SecuRemote/Client debug log files / SR Monitor files (NG)

The old fwenc.log is no longer used for VPN-1 SecuRemote NG or VPN-1 SecureClient NG. Instead, there is a log file for each of the following processes: SR_Service, SR_WatchDog and SR_Gui. Statistically, SR_Service is used more often since it contains all of the important functionality and includes the VPN debugging output. By default, the debug info is written to: C:\Program Files\CheckPoint\securemote\sr_service_tde.log.

To have SR_Service write all the debugging output to this file, proceed as follows:

1. Kill SecuRemote/SecureClient
2. Create the following file in the C:\ (root directory): SR_tde.all
3. Launch SecuRemote/SecureClient.

The files: SR_Service_tde.log, SR_WatchDog_tde.log and SR_Gui_tde.log. will be created in $SRDIR

######################################################################################################

How to run monitor packet captures on SecuRemote / SecureClient NG FP3

In order to run the monitor packet capture on SecuRemote / SecureClient NG FP3, proceed with the following:

On the SecuRemote / SecureClient NG FP3

1. Open the command prompt

2. Change the current directory to the SecuRemote / SecureClient bin directory. This can be done with the following command (the following example assumes the SecuRemote / SecureClient was installed in the C: drive):
cd "C:\Program Files\CheckPoint\SecuRemote\bin"

3. Run the "srfw monitor" command with the following syntax:

srfw monitor -o srfwmonitor.out

4. The srfwmonitor.out file will be generated in the "C:\Program Files\CheckPoint\SecuRemote\bin" directory.

5. When sending the file please mention the source and destination address

C:\Program Files\CheckPoint\SecuRemote\bin\MtuAdjust.exe to adjust the MTU on the client... useful...

24/JULY/03

< back