Watchguard Mobile Vpn Client Mac

This topic describes common problems and solutions for Mobile VPN with SSL:

The WatchGuard IPSec VPN Client is a premium service that gives both the organization and its remote employees a higher level of protection and a better VPN experience. Compatible with Windows and Mac OS X, the IPSec VPN is the ideal solution for employees who frequently work remotely or require remote access to sensitive resources. WatchGuard IPSec VPN Client for Mac In order to use your client software, you need a serial number and a license key. The license is released by the activation code sent via by us to the client on the endpoint.

Download Issues

Cheap Vpn University Of Utah Mac And Watchguard Mobile Vpn Client Mac Os X Vpn Un. Hello, When installing the WatchGuard SSL VPN 12.2 under OSX software 10.14.6, I received an alert detailing that the support of Watchguard was ending soon and to advise with the vendor software administrator for support. A volume named WatchGuard Mobile VPN is created on your desktop. In the WatchGuard Mobile VPN volume, double-click WatchGuard Mobile VPN with SSL Installer.mpkg. The client installer starts. Accept the default settings on each screen of the installer. Finish and exit the installer.

If users cannot download the Mobile VPN with SSL client from the Firebox:

Make sure users connect to your Firebox with the correct URL and port number. In the Mobile VPN with SSL configuration, the Configuration Channel setting specifies the port number for client downloads. If you keep the default port number (443), make sure users connect tohttps://[Firebox IP address]/sslvpn.html to download the Mobile VPN with SSL client.
If you specify a configuration channel port other then 443, make sure that users connect to https://[Firebox IP address]:[port]/sslvpn.html to download the Mobile VPN with SSL client.
Make sure you have not disabled the Mobile VPN with SSL software downloads page hosted by the Firebox. If you disable this page, users cannot download the Mobile VPN with SSL client from the Firebox. For more information about the CLI command that disables the download page, see Plan Your Mobile VPN with SSL Configuration.

If users still cannot download the Mobile VPN with SSL client from the Firebox:

Users can download the client from the WatchGuard software downloads page.
You can manually distribute the client software and updated configuration file to users. For more information, see Manually Distribute and Install the Mobile VPN with SSL Client Software and Configuration File.

If users have installed the Mobile VPN with SSL client but cannot download an updated configuration:

If the error 'Could not download the configuration from the server. Do you want to try to connect using the most recent configuration?' appears, tell users to click Yes to make a VPN connection unless you have changed the Mobile VPN with SSL settings in your Firebox configuration. If users click Yes, the client does not automatically receive configuration changes. If you change the Mobile VPN with SSL configuration on the Firebox, you must manually distribute the update to users who cannot download it from the Firebox.

In Fireware versions lower than v11.x, the authentication and client configuration port is 4100.

Installation Issues

For information about which operating systems are compatible with each mobile VPN type, see the Operating System Compatibility list in the Fireware Release Notes. You can find the Release Notes for your version of Fireware OS on the Fireware Release Notes page of the WatchGuard website.

The Firebox has version requirements for TLS connections:

SSL VPN client connections

In Fireware v12.5.4 or higher, the Firebox requires the SSL VPN client to support TLS 1.2 or higher.

In earlier Fireware v12 releases, the Firebox requires the SSL VPN client to support TLS 1.1 or higher.

SSL VPN client download page

In Fireware v12.5.5 or higher, to download the client from the Firebox, your browser must support TLS 1.2 or higher. In earlier Fireware v12 releases, to download the client from the Firebox, your browser must support TLS 1.1 or higher.

To install the Mobile VPN with SSL client on macOS, you must have administrator privileges.

In macOS 10.15 (Catalina) or higher, you must install v12.5.2 or higher of the WatchGuard Mobile VPN with SSL client. For more compatibility information, see the Fireware Release Notes.

Upgrade Issues

To upgrade the Mobile VPN with SSL Windows client, you must have administrator privileges.

If a minor version update is available, but you cannot update the client version, you can still connect to the VPN tunnel.
If a major version update is available, but you cannot update the client version, you cannot connect to the VPN tunnel.

In Fireware v12.5.3 or higher, if the client automatically detects that an upgrade is available, but you do not have administrator privileges, a message appears that tells you to contact your system administrator for assistance. If a minor version update is available, you can select the Don't show this message again check box. This check box does not appear if a major version update is available.

In Fireware v12.5.2 or lower, if the client automatically detects that an upgrade is available, a message appears that asks you to upgrade. However, if you do not have administrator privileges, you cannot upgrade the client.

Connection Issues

The VPN client cannot connect. These error messages might appear on the client or in the client logs: Failed: Cannot perform HTTP request, Cannot perform HTTP request 12157, Cannot perform HTTP request 12031, Timeout 12002, Failed to get domain name, or System tried to join.

This log message indicates that the client cannot make an HTTPS connection to the IP address specified in the Server text box in the Mobile VPN with SSL client. Confirm that the policy configuration on the Firebox allows connections from Any-External to Firebox, and that no other policy handles traffic from the IP addresses you configured as the virtual IP address pool for Mobile VPN with SSL.

If you specify a TCP port other than 443 as the Configuration Channel in the Mobile VPN with SSL settings, mobile users must specify the port number as part of the address in the Server text box in the Mobile VPN with SSL client. For example, if the port is TCP 444, specify 203.0.113.2:444 on the client.

In Fireware v12.1.x, settings shared by the Access Portal and Mobile VPN over SSL appear on a page named VPN Portal. The Configuration Data Channel for Mobile VPN with SSL was renamed as the VPN Portal port and appears in the VPN Portal settings. In Fireware v12.2, the VPN Portal settings moved to the Access Portal and Mobile VPN with SSL configurations. For configuration instructions that apply to Fireware v12.1.x, see Configure the VPN Portal settings in Fireware v12.1.x in the WatchGuard Knowledge Base.

If the operating system on your computer does not support TLS 1.2, or TLS 1.2 or higher is not enabled, you might see this error message. In Fireware v12.5.4 or higher, Mobile VPN with SSL requires TLS 1.2 or higher. To avoid security vulnerabilities in TLS 1.1 or lower, we recommend that you disable TLS 1.1 or lower and only enable TLS 1.2 or higher.

Some older operating systems do not support TLS 1.2 or higher. For more information about TLS in older operating systems, see Mobile VPN with SSL connections fail from some versions of Windows and macOS in the WatchGuard Knowledge Base.

The VPN client cannot connect with a valid user name and password.

This problem can be caused by a static NAT (SNAT) action for inbound HTTPS traffic, or it can be a problem with client authentication.

When the Firebox receives an HTTPS request, it could forward that request to an internal server if your configuration includes an HTTPS policy with a static NAT action. If this occurs for traffic from the Mobile VPN with SSL client, the client fails to connect and an authentication failure message appears:

(SSLVPN authentication failed) Could not download the configuration from the server. Do you want to try to connect using the most recent configuration?

Check your configuration to make sure that a policy does not forward HTTPS requests on the port used by the Mobile VPN with SSL client to another server.

This authentication error message could also indicate a problem with authentication.

To troubleshoot client authentication:

Connect to the Firebox.
Review the configuration for Mobile VPN with SSL.
Record the configured Primary and Backup IP addresses.
The address can also be a domain name. If it is a domain name, confirm which IP address the domain name resolves to.
Record the configured Configuration channel TCP port.
In Fireware v12.1.x, select Authentication > Configure and record the configured VPN Portal port. In Fireware v12.1.x, the configuration channel setting was named as the VPN Portal port.
In your web browser, type https://<ip-address>/sslvpn.html where <ip-address> is the Primary IP address in the Mobile VPN with SSL configuration. If the Configuration channel TCP port is not 443, add the port number to the address, separated by a colon. For example, if the Configuration channel is TCP port 444, in the browser type https://<ip-address>:444/sslvpn.html.
- If the WatchGuard Authentication Portal page for your Firebox appears, continue to Step 6.
- If a page other than the WatchGuard Authentication Portal page appears, review your Firebox configuration to identify why the traffic was forwarded to this location. Consider a change to the configured IP address for the VPN.
On the WatchGuard Authentication Portal page, log in with client credentials.
If more than one type of authentication is configured, or if your authentication server is not the default option, select the authentication server from the drop-down list.
- If user authentication succeeds, continue to Step 7.
- If user authentication fails, verify the user credentials on the Firebox, or the external authentication server. For users on an external authentication server, verify whether other users who use that server are able to log in. There may be a problem with authentication in general.
In your web browser, type https://<ip-address>/sslvpn.html. If the Configuration channel TCP port is not 443, add the port number to the address, separated by a colon.
For example, if the Configuration channel is TCP port 444, type https://<ip-address>:444/sslvpn.html.
The WatchGuard Authentication Portal appears.
Log in with the client credentials you used in Step 5.

If the user authentication fails on the Mobile VPN with SSL-specific authentication page, but the same credentials worked on the WatchGuard Authentication Portal page, the issue is almost certainly group membership. Confirm that the user is part of the configured group for Mobile VPN with SSL. By default, this group is SSLVPN-Users.

The VPN client cannot connect and this log message appears: SSL VPN Error: connect() failed. ret = -1 errno=10061

This message indicates an issue on the client computer. To troubleshoot on the client computer, verify that:

The SSL VPN service is started
The TAP driver is installed properly
Another VPN client on the computer has not installed drivers that caused a conflict
Security software such as anti-virus or firewall software does not block the TAP driver
In Internet Explorer, in the Internet Options > Advanced settings, SSL 3.0 is not selected.

The VPN client cannot connect, the message Waiting for initial response from server appears, and the VPN client has the IP address 0.0.0.0.

This issue can occur if a router or modem on the user's local network prevents return communication from the Firebox to the VPN client.

In Windows Device Manager, verify the status of the virtual adapter to make sure a local router or modem does not inspect, filter, or proxy the VPN traffic. You might have to adjust security settings on the local router or modem.

In Fireware v12.5 or higher, you must configure a RADIUS domain name. If your Firebox configuration includes a RADIUS server, and you upgrade from Fireware v12.4.1 or lower to Fireware v12.5 or higher, the Firebox automatically uses RADIUS as the domain name for that server. To authenticate to that server, users must type RADIUS as the domain name. In this case, if users type a domain name other than RADIUS, authentication fails. For more information, see Download, Install, and Connect the Mobile VPN with SSL Client.

To troubleshoot mobile VPN connection issues related to TDR Host Sensor Enforcement, see Troubleshoot TDR Host Sensor Enforcement.

Issues After Connection

The VPN client can connect, but users cannot connect to internal resources by name.

If the VPN client can connect to a resource by IP address but not by name, you must provide the client with the IP addresses of valid DNS or WINS servers that can resolve the destination name. When the client connects and receives a virtual IP address from the Firebox, it also receives the IP addresses for the DNS and WINS servers configured globally on the Firebox or in the Mobile VPN with SSL configuration.

When you configure Mobile VPN with SSL in Fireware v12.2.1 or higher, you can select to:

Assign the client device the WINS server, DNS server, and DNS suffix configured in the Mobile VPN with SSL settings on the Firebox
Assign the client device the WINS server, DNS server, and DNS suffix configured in the Network (global) DNS/WINS settings on the Firebox
Assign no DNS or WINS settings to the client device

For information about how to configure WINS and DNS IP addresses, see Name Resolution for Mobile VPN with SSL.

For more information about global DNS settings on the Firebox, see Configure Network DNS and WINS Servers.

The VPN client can connect, but VPN users cannot connect to internal resources with a single-part host name.

If users cannot use a single-part host name to connect to internal network resources, but can use a Fully Qualified Domain Name (FQDN) to connect, this indicates that the DNS suffix is not defined on the client. When you configure Mobile VPN with SSL in Fireware v12.2.1 or higher, you can select to:

Assign the client device the WINS server, DNS server, and DNS suffix configured in the Mobile VPN with SSL settings on the Firebox
Assign the client device the WINS server, DNS server, and DNS suffix configured in the Network (global) DNS/WINS settings on the Firebox
Assign no DNS or WINS settings to the client device

A client without a DNS suffix assigned must use the entire DNS name to resolve the name to an IP address. For example, if your terminal server has a DNS name of RDP.example.net, users cannot type the address RDP to connect with their terminal server clients. Users must also type the DNS suffix example.net.

For more information about DNS for Mobile VPN with SSL, see Name Resolution for Mobile VPN with SSL.

For more information about global DNS settings on the Firebox, see Configure Network DNS and WINS Servers.

In Fireware v12.2 or lower, if you do not configure WINS and DNS settings in the Mobile VPN with SSL configuration, the SSL VPN client is assigned the Network (global) DNS/WINS settings. This includes the DNS server, WINS server, and domain suffix. If you specify a DNS suffix in the Network (global) WINS/DNS settings for the Firebox, but do not specify a DNS suffix in the Mobile VPN with SSL settings, the VPN client does not receive the DNS suffix unless all other DNS and WINS settings in the Mobile VPN with SSL configuration are also not configured.

The VPN client can connect, but all traffic fails. The Unhandled External Packet log message is generated and includes other details that indicate a group membership problem.

If client traffic through the Mobile VPN with SSL connection is denied as unhandled, the problem is almost always related to group membership. By default, Mobile VPN with SSL requires that a user be a member of a group called SSLVPN-Users. If you use a RADIUS, SecurID, or VASCO server, the group membership must be returned as the Filter-ID attribute.

For more information about how to configure external authentication servers, see Configure the External Authentication Server.

The VPN client can connect, but Office 365 traffic does not go through the SSL VPN tunnel.

If you configure Mobile VPN with SSL to send all traffic through the tunnel, but Office 365 traffic does not go through the tunnel, you have these options:

Enable the default-route-client option in the Fireware CLI (Fireware v12.5.3 or higher)
Manually configure a default gateway on the client
Use a different Fireware mobile VPN method

For more information, and to configure the first two solutions, see Office 365 fails for Mobile VPN with SSL users in the WatchGuard Knowledge Base.

The VPN client can connect, but users cannot connect to some internal resources. The log messages do not show traffic allowed or denied.

If you select Routed VPN traffic in the Mobile VPN with SSL network settings, the Firebox routes traffic from Mobile VPN with SSL clients to allowed networks and resources.

Make sure that users have v11.10 or higher of the Mobile VPN with SSL client. The Mobile VPN with SSL client v11.10 and higher supports more than 24 routes. Previous versions of the Mobile VPN with SSL client support a maximum of 24 routes.

For users with Mobile VPN with SSL client v11.9.x and lower, your configuration must include fewer than 24 routes to resources for the Mobile VPN with SSL client. If the total number of networks or allowed resources exceeds 24, the VPN client cannot route traffic to all of the allowed resources. For users with Mobile VPN with SSL client v11.9.x and lower, your Mobile VPN with SSL configuration might include too many routes if:

Watchguard Mobile Vpn

In the Mobile VPN with SSL configuration, you select Allow access to networks connected through Trusted, Optional, and VLANs, and you have more than 24 resources in the Allowed Resources list.
In the Mobile VPN with SSL configuration, you selected Specify allowed resources, and added more than 24 resources.

The WINS and DNS settings can also add up to five additional routes to the total if two DNS servers, two WINS servers, and a domain suffix are all configured. This further reduces the number of allowed resources the client can route to.

To reduce the number of routes, you can specify allowed resources in a way that generates fewer routes. To do this, select Specify allowed resources and then use supernets to specify the allowed resources as fewer entries. For example, if your Allowed Resources list includes the resources 192.168.1.0/24, 192.168.25.0/24, and 192.168.26.0/24, you can express this as a single resource, 192.168.0.0/22, which includes all addresses from 192.168.1.0 to 192.168.31.255.

For more information about how to specify resources for Mobile VPN with SSL, see Manually Configure the Firebox for Mobile VPN with SSL.

The VPN client can connect, but all traffic fails. The Unhandled External Packet log message is generated, and includes other details that indicate a problem with the policy configuration.

When you enable Mobile VPN with SSL, the Allow SSLVPN-Users policy is automatically created to allow traffic from the clients to internal or external network resources. If you disable or remove this policy, clients cannot send traffic to internal or external networks.

Watchguard Mobile Vpn Client Mac Free

To solve this problem, make sure that the policy exists and allows traffic to network resources.

For more information about the this policy, see Manually Configure the Firebox for Mobile VPN with SSL and Options for Internet Access Through a Mobile VPN with SSL Tunnel.

The VPN client can connect, and the traffic appears to be allowed, but the client never gets a response, or some network resources fail.

If your VPN clients can connect to some but not all parts of the network, or traffic otherwise fails when log messages show traffic is allowed, this can indicate a routing problem. Confirm that each of these items is true:

The virtual IP address pool for Mobile VPN with SSL clients does not overlap with any IP addresses assigned to internal network users.
The virtual IP address pool does not overlap or conflict with any other routed or VPN networks configured on the Firebox.
If the Mobile VPN with SSL users must access a routed or VPN network, the hosts in that routed or VPN network must have a valid route to the virtual IP address pool, or the Firebox must be the default route to the Internet for those hosts.

For more information about how to configure the IP address pool, see Manually Configure the Firebox for Mobile VPN with SSL.

We recommend that you do not use the private network ranges 192.168.0.0/24 or 192.168.1.0/24 on your corporate or guest networks. These ranges are commonly used on home networks. If a mobile VPN user has a home network range that overlaps with your corporate network range, traffic from the user does not go through the VPN tunnel. To resolve this issue, we recommend that you Migrate to a New Local Network Range.

The VPN client can connect, but some users cannot connect to any resources, and the client frequently disconnects.

Determine whether the issue affects some or all VPN users. If the issue affects only some of your VPN users or affects users at a specific location:

Make sure any firewalls at the user’s location allow the VPN connection.
Determine whether affected users have an uncommon subnet that overlaps with the network behind your Firebox.

If the issue affects most or all of your users, determine whether the network behind your Firebox has a subnet commonly used for home networks.

If you cannot connect to network resources through an established VPN tunnel, see Troubleshoot Network Connectivity for information about other steps you can take to identify and resolve the issue.

EmXwTk