It seems that when using the ovpn file to make a connection, a DNS suffix isn't added to the TAP adapter in Windows. So if I try and reach a hostname without the full FQDN, then the request fails. But if I add the FQDN, it works. Wondering if anyone has experienced the same and found a workaround. We are noticing this problem with the OpenVPN client. It's an easy fix to update the .ovpn file manually to add the suffix, but that seems like a terrible solution long term.
I have even located the file within the XG's filesystem that could be updated to include this simple fix. Please help!
Hello Jesse Mayo,Thank you for reaching out to the community, What is the current version of the connect client you are using ? This was a bug reported: NCL-1383. Which is fixed in Sophos Connect 2.2. And Sophos Connect 2.2 is out now and can be downloaded via portal OR you can download from the configure > VPN > IPsec (remote access) > download client
Thanks & Regards,_______________________________________________________________
Vivek Jagad | Technical Account Manager 3 | Cyber Security Evolved
Sophos Community | Product Documentation | Sophos Techvids | SMSIf a post solves your question please use the 'Verify Answer' button.
Thanks, we are trying to transition off of the sophos connect client as it has become too problematic for our org. We regularly get tickets sent in from users saying they are getting "service unavailable" on the connect GUI. I have observed the same on my own computer from time to time.
okay but what version of Sophos connect client were you using ?
We are on 2.0.34.0910
Then Jesse Mayo, you running a very old firmware. Please upgrade to the latest to Sophos Connect 2.2 and then revert us with the status. You can simply navigate to the configure > VPN > IPsec (remote access) > download client.
Thanks, I just went and installed 2.2.75 and it does fix the DNS issue, but we will have to go through a lot of testing to verify if the "Service Unavailable" issue goes away with the new version. Any information on this would be appreciated.
I believe that too is fixed, we will be publishing the release notes of Sophos Connect 2.2 in next couple of days. But yes we are open to feedback, please revert us here if the "Service Unavailable" is still observed.
I believe these were one in the same due to the DNS issues, which has also been in 2.1. Glad they finally got 2.2 out, now if we can get some other things done that would be great. :D
UTM - 9.713-19 64-bit | Intel Xeon 4-core v3 1225 3.20Ghz 16GB Memory | 500GB SATA HDD | GB Ethernet x5