Guest User!

You are not Sophos Staff.

This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

SSL VPN DNS suffix

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!



This thread was automatically locked due to age.
Parents
  • Hello ,

    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, 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.

Reply
  • 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.

Children