The Tftp Application And Groupwise Notify Do Not Work In Enterprise Mode; Ssl Vpn Not Reporting; Verifying And Restarting Jcc; Verifying And Restarting The Ssl Vpn Server - Novell ACCESS MANAGER 3.1 SP2 - SSL VPN SERVER GUIDE 2010 Manual

A.6 The TFTP Application and GroupWise Notify
Do Not Work in Enterprise Mode
If the TFTP application and GroupWise
have done the following:
You have configured a route using the default gateway. For more information, see
"Configuring Route and Source NAT for Enterprise Mode," on page
You are not using source NAT to route packets.
A.7 SSL VPN Not Reporting
If SSL VPN is not reporting, you must verify the status of JCC and the SSL VPN server and restart
them if they are down. If restarting any of these components does not work, reconfigure SSL VPN.
If none of these work, you must delete and reimport the SSL VPN server.
Section A.7.1, "Verifying and Restarting JCC," on page 105
Section A.7.2, "Verifying and Restarting the SSL VPN Server," on page 105
A.7.1 Verifying and Restarting JCC
To check the status of JCC, enter the following command:
/etc/init.d/novell-jcc status.
If it is not running, enter the following command to restart JCC:
/etc/init.d/novell-jcc restart
A.7.2 Verifying and Restarting the SSL VPN Server
To verify the status of the SSL VPN server, enter the following command:
/etc/init.d/novell-sslvpn status
If any component is down, stop and start the SSL VPN server by using the following commands:
novell-sslvpn stop
novell-sslvpn start
A.8 Verifying SSL VPN Components
Use the commands and processes described in the following sections to verify that the SSL VPN
components are running:
Section A.8.1, "SSL VPN Server," on page 106
Section A.8.2, "SSL VPN Linux Client," on page 106
Section A.8.3, "SSL VPN Macintosh Client," on page 106
Section A.8.4, "SSL VPN Windows Client," on page 106
®
Notify do not work in Enterprise mode, make sure you
Section 2.4,
32.
Troubleshooting SSL VPN Configuration 105