Thread Info
  • State Verified Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 8 replies
  • Subscribers 39 subscribers
  • Views 3780 views
  • Users 0 members are here
Options
Suggested
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

Jesse Mayo

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 Reply
  • 0 in reply to Vivek Jagad

    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
Unfiltered HTML