Troubleshooting TZ 180 Configuration and Settings Issues
18
SonicWALL TZ 180 Recommends Guide
Symptom: The GlobalVPN Client Asks for a Key on First Connection
Provide users with the shared secret key when using this feature. To simplify this, you can navigate to the
Advanced
tab and enable the
Use Default Key for Simple Client Provisioning
option, which allows users
to only enter a username and password to connect.
Symptom: The GlobalVPN Client Displays a Tmeout with a DHCP Error
If you are using the Virtual Adapter, verify that the appliance is set for DHCP over VPN, and then verify
that the appliance has a DHCP scope set up, or is pointed to an internal DHCP server that can issue an
address to the GlobalVPN’s Virtual Adapter. This is found on the
VPN > DHCP over VPN
page. Click
the
Configure
button next to
Central Gateway
and specify if the appliance should assign from an internal
pool or using an external DHCP server.
Symptom: The GlobalVPN Client Has Connectivity Issues or Reports Unusual
Messages upon Failure
Visit the MySonicWALL portal to see if you are using the most current version.
Symptom: GlobalVPN Users Have Problems Accessing Microsoft Networking
Resources over the Connection
Use a resolving mechanism such as WINS, Active Directory/DNS, or static HOSTS/LMHOSTS files for
the GVC. The easiest solution is to provide the appropriate WINS and DNS entries in the DHCP scope,
and to use the Virtual Adapter capability of the GroupVPN policy. The GlobalVPN clients receive the
correct IP address in the DHCP lease.
Registration Troubleshooting
Symptom: I Am Having Registration Problems with the TZ 180
Review the
“Registering and Enabling Support” section on page 4
, which provides instructions for
registering the TZ 180 security appliance.
If you are attempting to use the Registration & Licensing Wizard, or the registration link on the
System >
Status
page, there may be a connectivity issue. The most common issue is that the DNS address is not set
properly. Navigate to the
Network > Settings
page and verify that the DNS is set to a valid, known-good
DNS server that the appliance can reach. If you do not know your ISP DNS servers, you can use 4.2.2.1 and
4.2.2.2 temporarily. Also verify that the appliance is set to the proper time zone. The security appliance
cannot contact the registration servers unless these settings are correct.
Verify that the Security Appliance Is Able to Connect to the Internet
Navigate to the
System > Diagnostics
page and use the
TraceRoute
utility to see if the appliance has a
working connection, using a known-good public IP address or name on the Internet (for example,
).
