Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    OpenVPN and WINs refuse to play together

    Scheduled Pinned Locked Moved OpenVPN
    15 Posts 4 Posters 2.5k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • T
      tsolrm
      last edited by

      So on my LAN I can access my NAS device like so:

      \host

      VPN clients can only access it this way: \host.domain

      Is this fixable?

      1 Reply Last reply Reply Quote 0
      • K
        kejianshi
        last edited by

        I just use IP…  I use static dhcp reservations and I'm done.

        1 Reply Last reply Reply Quote 0
        • T
          tsolrm
          last edited by

          Yes but people on the network already have their shares configured, wouldn't want them to mess about with IPs.

          1 Reply Last reply Reply Quote 0
          • K
            kejianshi
            last edited by

            do you have a properly configured wins server with access to all the devices in question?

            1 Reply Last reply Reply Quote 0
            • T
              tsolrm
              last edited by

              The NAS device must have the WINs set up. How to I get pfsense to push it to vpn clients?

              1 Reply Last reply Reply Quote 0
              • D
                doktornotor Banned
                last edited by

                As already noted on the other thread, you should use DNS and FQDNs. No idea why you started another thread about the same thing.  >:(

                https://forum.pfsense.org/index.php?topic=89868

                (Not to mention, no such thing will work with OpenVPN unless specifically enable - which is still a bad idea and completely pointless for this purpose.)

                1 Reply Last reply Reply Quote 0
                • T
                  tsolrm
                  last edited by

                  @doktornotor:

                  As already noted on the other thread, you should use DNS and FQDNs. No idea why you started another thread about the same thing.

                  https://forum.pfsense.org/index.php?topic=89868

                  My DNS and DQDN is working fine, I can access the nas device like so: \host.domain. But I want the \host to work

                  1 Reply Last reply Reply Quote 0
                  • K
                    kejianshi
                    last edited by

                    In the case that you will follow doctornotor, I would still want to assign static IPs

                    1 Reply Last reply Reply Quote 0
                    • D
                      doktornotor Banned
                      last edited by

                      @tsolrm:

                      But I want the \host to work

                      Why? It's just bad practice.

                      1 Reply Last reply Reply Quote 0
                      • K
                        kejianshi
                        last edited by

                        Running a wins server is a hassle and its not 100% reliable either.

                        I have 1 configured and haven't used it in years.

                        1 Reply Last reply Reply Quote 0
                        • T
                          tsolrm
                          last edited by

                          For the benefit of those who want this to work without a WINS server, do the following:

                          Set the pfsense domain to: lan

                          Check the option of sending a default domain name to VPN clients in the OpenVPN server config and choose 'lan' as the default domain name.

                          Works.

                          1 Reply Last reply Reply Quote 0
                          • K
                            kejianshi
                            last edited by

                            I probably would have made the domain something other than "lan", but sure.  Thats seems logical.  Its working well?

                            1 Reply Last reply Reply Quote 0
                            • T
                              tsolrm
                              last edited by

                              @kejianshi:

                              I probably would have made the domain something other than "lan", but sure.  Thats seems logical.  Its working well?

                              Actually 'lan' along with 'local' are in the list of reserved domains and that's what made the whole thing work. Don't ask me why lol

                              1 Reply Last reply Reply Quote 0
                              • K
                                kejianshi
                                last edited by

                                It works for me using DNS Resolver if I use \MachineName.DomainName without using wins and without having to use any specific reserved names.

                                I think its probably better this way but if the other way makes you happy, go for it if its not breaking anything I guess.

                                Edit:  I learned something about this…

                                Set the pfsense domain to: AnyWordYouLike

                                Check the option of sending a default domain name to VPN clients in the OpenVPN server config and choose the same word you chose for pfsense domain as the default domain name.

                                It doesn't have to be "lan"

                                1 Reply Last reply Reply Quote 0
                                • K
                                  KineticPro
                                  last edited by

                                  if this is an Active Directory just change group policy to the FQDN and problem does not matter 5 min work to you and on there next login they have the new settings

                                  1 Reply Last reply Reply Quote 0
                                  • First post
                                    Last post
                                  Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.