Results 1 to 6 of 6

Thread: Open VPN Issue

  1. #1
    Untanglit
    Join Date
    Jul 2017
    Posts
    23

    Default Open VPN Issue

    Looking for an answer.

    Server: Windows Server 2016 Standard
    Remote: Windows 10 Pro

    I setup the OpenVPN App, connected the client. The issue I am having is that I can browse to the server only by the IP address of the server not the hostname. I receive an error when browsing the hostname.

    I added the hostname to the hosts file which worked but this is just a workaround. Is there something I am missing during the OpenVPN app setup that is causing this?

    Thanks,

  2. #2
    Untangle Ninja sky-knight's Avatar
    Join Date
    Apr 2008
    Location
    Phoenix, AZ
    Posts
    25,259

    Default

    This forum is for Untangle's OpenVPN module, if you need help with OpenVPN itself, give these forums a try: https://forums.openvpn.net/
    Rob Sandling, BS:SWE, MCP
    NexgenAppliances.com
    Phone: 866-794-8879 x201
    Email: support@nexgenappliances.com

  3. #3
    Untangler jcoffin's Avatar
    Join Date
    Aug 2008
    Location
    Sunnyvale, CA
    Posts
    9,199

    Default

    Add the hostname to the Untangle DNS in /admin/index.do#config/network/dns-server .

    NetBIOS protocol (WIndows naming system) does not transverse VPN tunnels.
    Last edited by jcoffin; 01-19-2020 at 10:15 AM.
    Attention: Support and help on the Untangle Forums is provided by
    volunteers and community members like yourself.
    If you need Untangle support please call or email support@untangle.com

  4. #4
    Untangle Ninja
    Join Date
    May 2008
    Posts
    1,333

    Default

    I think he means the Untangle openvpn app. It is a dms issue.

  5. #5
    Untangle Ninja sky-knight's Avatar
    Join Date
    Apr 2008
    Location
    Phoenix, AZ
    Posts
    25,259

    Default

    That's not quite accurate, Windows doesn't really have NetBIOS anymore. But, it does use the broadcast based name resolution mechanism to find what we'd call NetBIOS names. Untangle's VPNs being routed, won't allow this broadcast to propagate. But that isn't to say other VPN would do the same, that's why from time to time we have people asking for bridge based VPNs.

    But yes, this is a DNS problem.

    Step 1.) IP connectivity *Working*
    Step 2.) DNS resolution of fully qualified names
    Step 3.) DNS resolution of short names

    I think we can safely say the OP is stuck in step two. Which is resolved as JCoffin indicated, config -> network -> DNS, and filling in an entry for a Domain DNS Server, pointing the appropriate domain name to the DNS server that supports it, usually the domain controller. Then assuming default configuration for the OpenVPN group (Apps, OpenVPN, Settings, Server tab, Groups subtab, edit on the group the OpenVPN client is a member of.) Default is push DNS, and push DNS of OpenVPN server. Again, this is LONG NAMES, server.domain.com

    Then onto step 3, while you're looking at the group... make sure the Push DNS domain field has the correct DNS suffix in it for your DNS domain. Then assuming the remote device can resolve names at all, it'll resolve short ones too. That is a lookup for "server" will try to find server.domain.com as configured in this box, and should that record exist, magic happens.
    Rob Sandling, BS:SWE, MCP
    NexgenAppliances.com
    Phone: 866-794-8879 x201
    Email: support@nexgenappliances.com

  6. #6
    Untanglit
    Join Date
    Jul 2017
    Posts
    23

    Default

    Thanks for the answers, Ninja's steps worked perfectly. Thank you!
    Jim.Alles likes this.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

SEO by vBSEO 3.6.0 PL2