Yuck. Currently sitting in a hospital whose network blocks non-standard web ports (including the Sophos SSL VPN port 8443) and so I am unable to connect to my VPN.
At some later date I may try the workaround suggested by MarcBorgers but this is not ideal and I wonder whether this will disable the User Portal on port 443. (Although perhaps the solution there is to change the User Portal HTTPS port to something else, and then use 443 for the VPN using the forwarding policy?)
In any case this is a mess, and there should be a configuration option for the SSL VPN Port as well, so that admins can decide which services to expose on the standard web ports. Ideally if the User Portal and VPN can both share 443 and the software can recognize the VPN traffic and deal with it appropriately in order to distinguish it from the User Portal traffic, then both of those services can be made available to someone in my current situation.
Yuck. Currently sitting in a hospital whose network blocks non-standard web ports (including the Sophos SSL VPN port 8443) and so I am unable to connect to my VPN.
At some later date I may try the workaround suggested by MarcBorgers but this is not ideal and I wonder whether this will disable the User Portal on port 443. (Although perhaps the solution there is to change the User Portal HTTPS port to something else, and then use 443 for the VPN using the forwarding policy?)
In any case this is a mess, and there should be a configuration option for the SSL VPN Port as well, so that admins can decide which services to expose on the standard web ports. Ideally if the User Portal and VPN can both share 443 and the software can recognize the VPN traffic and deal with it appropriately in order to distinguish it from the User Portal traffic, then both of those services can be made available to someone in my current situation.
