same experience here with 7.401. When I've the DNAT HTTPS rule for our Outlook Web Access site enabled, the SSL client cannot connect, 'connection reset' error. Once I disable the DNAT rule I can successfully connect, but of course the outlook web access site is inaccessible which is unwanted. So for now it one or the other.
In googling about this just now, I found some claims of dramatic increases in throughput with UDP, but I would think that there would be situations where that wouldn't be true.
Same problem: Have an internal web server that I changed to require https: and changed DNAT rule accordingly. Now SSL clients do not work and the portal is inaccessible, because port 443 is routed to the web server.
So, it's clear where to change the Remote Connection port and protocol. I changed it to UDP, but the client does not connect. I do not see anywhere to edit the client config for protocol? I am reluctant to change the port because of remote firewall issues (home and hotel firewalls may block obscure ports)
That still would not resolve the problem of connecting to the portal to download a new client.
If there is no happy solution to the portal issue, I could request an additional ip address for my webserver.
Same problem: Have an internal web server that I changed to require https: and changed DNAT rule accordingly. Now SSL clients do not work and the portal is inaccessible, because port 443 is routed to the web server.
So, it's clear where to change the Remote Connection port and protocol. I changed it to UDP, but the client does not connect. I do not see anywhere to edit the client config for protocol? I am reluctant to change the port because of remote firewall issues (home and hotel firewalls may block obscure ports)
That still would not resolve the problem of connecting to the portal to download a new client.
If there is no happy solution to the portal issue, I could request an additional ip address for my webserver.
