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

    PfSense and Windows Network Discovery

    Scheduled Pinned Locked Moved General pfSense Questions
    5 Posts 4 Posters 5.1k 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.
    • M
      minegolder
      last edited by

      One thing I always struggled with in using pfSense is windows network discovery. I never got it to work. I have googled extensively, but did not find anything useful. I wonder what am I missing.

      I have a pfSense box as a firewall/router. It runs DHCP server. There is only one LAN interface, and only one network 10.1.1.0/24. DNS resolution works for DHCP hostnames within LAN. LAN has no firewall rules at all.

      I have two samba servers, a windows box and a linux box. I can connect directly using their hostnames, like \MyWindowsBox, or smb:\mylinuxbox.
      But no matter what system (win,linux or mac), I can never discover any samba servers on the local network.

      Any help is greatly appreciated.

      1 Reply Last reply Reply Quote 0
      • M
        minegolder
        last edited by

        I think i figured it out. As was said in the FAQ, check your firewalls.

        One of the boxes runs windows that I normally do not have a display attached. When I would change something in the network, it would bring up the UI dialogue and ask me what kind of network is it connected to: Home, Work or Public. And before I actually click on the damn thing it would filter out the discovery packets, hence no samba network discovery worked.

        1 Reply Last reply Reply Quote 0
        • M
          MarkVLK
          last edited by

          Was your issue fixed by changing the network type to "home" instead of "public"?

          1 Reply Last reply Reply Quote 0
          • johnpozJ
            johnpoz LAYER 8 Global Moderator
            last edited by

            This has nothing to do with pfsense btw.  And yeah if you want to broadcast for netbios names - you kind of have to allow that sort of traffic on the host firewalls ;)  Public setting on windows boxes pretty much prevents all inbound traffic to the interface.

            An intelligent man is sometimes forced to be drunk to spend time with his fools
            If you get confused: Listen to the Music Play
            Please don't Chat/PM me for help, unless mod related
            SG-4860 24.11 | Lab VMs 2.7.2, 24.11

            1 Reply Last reply Reply Quote 0
            • stephenw10S
              stephenw10 Netgate Administrator
              last edited by

              If you have a samba server or windows server that is up 24/7 then just have that run a WINS server and add it to the DHCP configuration in pfSense so that all clients register with it. These sorts of problems usually occur when you have a network of windows boxes behind pfSense but no domain controller and no WINS service. In that situation one box will become the 'netbios name server' but if it's turned off it can take ages for another machine to take over that duty and longer for it to have a complete list.
              It's been a while since I've had to deal with that I could be skipping a few steps!  ;)

              Steve

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