thak
Hey folks -
I have a Win 7 VM that I use to make use of our VPN which does not allow split tunneling. I don't like to do it from my desktop as that kills connectivity to printing and whatnot.
The connection works fine as long as we don't move the AS to TLS 1.1 or 1.2. 1.0 works fine, but 1.1 and 1.2 time out after authentication. The logs aren't verbose enough for me to really understand what's happening.
Also, it should be noted, on my Mac OS X desktop, TLS 1.2 works fine.
Any ideas?
luckman212
This is interesting. I have the exact same problem, but in reverse. I have an OpenVPN AS server 2.0.17 VM appliance fully updated/patched. If I enable TLS 1.1 or 1.2, the Mac OS X clients can no longer connect (timeout). Windows and iOS clients work fine. I opened a ticket and they are looking into it. Anyway let me know what your progress is.
luckman212
Update: opened a ticket with suport and they found this was a bug in the Mac client. It is fixed in the dev version they sent me which should be released soon along with an updated Access Server version.
The Johan
OpenVPN Technologies support here.
Access Server 2.0.20 was released a few days ago, and contains the updated Connect Client for Windows. It is able to handle TLS 1.1 and TLS 1.2 correctly.
Note that not all OpenVPN clients out there are able to connect to a TLS 1.1/1.2 configured OpenVPN server. This is mentioned in the section where you can configure the TLS options on the Access Server as well. But now at least the Connect Client bundled with the Access Server is able to connect, as are up-to-date open source OpenVPN clients. Some other client software with older bundled OpenVPN versions may have problems still, but eventually those will get updated as well, hopefully.
