Watchguard Firewall - Issues with SSLVPN
Every time I run into this the fix is usually use remote.domain.com:4100. Even if your policy says to use port 22 or 443 you must still append the :4100 after just like your downloading the SSLVPN client.
Every time I run into this the fix is usually use remote.domain.com:4100. Even if your policy says to use port 22 or 443 you must still append the :4100 after just like your downloading the SSLVPN client.