Monitor Juniper Secure Connect
In case of any issues, we recommend that you follow these steps to check the log messages and locate the issue:
Check the logs in Junos OS
Check the logs in the Juniper Secure Connect application
Check Junos OS Logs
You must configure syslog to save the syslog file on your device. Currently, J-Web does not support structured logs. Only unstructured logs are supported.
Depending on the syslog format (for structured logs) you configure in the system, you might not find the log messages under Monitor > Events > System. Because of this, we recommend that you download the "messages" file from Device Administration > Operations > Files and search for the event.
For the unstructured logs (in J-Web), to find information about the success or failure of authentication:
For a Juniper Secure Connect application configuration download, search for "REMOTE_ACCESS".
For a VPN connection, search for "KMD_".
Following is the result of "REMOTE_ACCESS" search:
By default, J-Web displays warning and error messages. If you want to view info level messages, change the syslog configuration using CLI. Table 1 lists the supported log levels:
Table 1: Syslog Severity Levels
Log severity Level
Indicates conditions that require immediate correction, such as a corrupted system database.
Indicates all log levels.
Indicates critical conditions, such as hard drive errors.
Indicates system panic or other conditions that cause the routing platform to stop functioning.
Indicates standard error conditions.
Only informational messages.
Indicates conditions that should be handled specially.
Indicates conditions that warrant monitoring.
You can view the stream (traffic or routing engine) logs by navigating to Monitor > Events > IPsec VPN page.
Check Juniper Secure Connect Application Logs
- The log is continuously active in the background, even
if the log window is not open. All the relevant Juniper Secure Connect
communication events are displayed and saved for one week per operation
day, in a log file. The files older than seven online days are automatically
The log file is generated automatically in the installation directory under the
Logfolder when the communication process is completed. The log file is named in
NCPyymmdd.LOGformat, where yy=year, mm=month, and dd=date. Select Help > Logbook to view the log messages in the log book page.
You can change the storage time for log files using the Extended Log Settings option. You can open and analyze the log files using a text editor.
- From the menu bar, click Help and then select Extended Log Settings.
- Enable all options by selecting all the check boxes, and then click OK.
- Open the logbook and check for any log messages that indicate the problem. If you cannot resolve your issue based upon the log messages, start the Support Assistant by clicking Help and then selecting Support Assistant. The Support Assistant collects all the required data.
- Click Add to attach any additional files, and then click Next. The Save archive file page opens.
- Select the Only create the archive file option
button. Then, click Next.
After the archival process is completed, Juniper Secure Connect displays the archived file location.
- Click Finish.
Following are the steps to check the Juniper Secure Connect application logs on a macOS platform:
- Select Log > Logbook through the Juniper Secure
Connect application menu to open the logbook.
Check for any log messages that indicate the problem.
- If you are not able to resolve the issue, save this log
message into a file with the
ncpmonlog.txtfilename. Copy the file
ncpphone.cfgto the same location where you saved the logbook file
- To locate the
ncpphone.cfgfile, open the Finder and select Go in the menu bar and at the same time press down the “Option” key on your keyboard.
The directory location where the Juniper Secure Connect files are saved is displayed.
Following are the steps to check the Juniper Secure Connect application logs on an Android device:
In the Juniper Secure Connect application menu, click the three vertical dots at the top right corner and select Log from the menu.
The log output window appears, displaying the log messages.
The log is continuously active in the background, even if the log window is closed. All the relevant Juniper Secure Connect communication events are saved in the log file. Navigate to Diagnostics > Debugging > Error Log to view the log messages. Click on the export icon right on top of the screen to send the log file through the offered applications.
Figure 18 shows a sample log message for an active VPN connection.