Does not block the broadcast packets



  • Hi

    I have a firewall hardware with pfSense 2.3.2 64 bit which manages a LAN peer to peer with 5 computers that have Windows 7 SP1 Ultimate and a NAS. All of these network devices have fixed IP.

    Since yesterday, in the Network window, the NAS is not displayed among the networked computers. This fact occurs only on a single computer.

    If, however, in the Network window of this computer, I type \<nas_name>, all the NAS folders are displayed.

    So, I would like to know the reason why  Windows 7 does no more detect the NAS when it scans the network to search for the various computers.

    How do I check if my firewall does not block the broadcast packets from the NAS?

    Thanks

    Bye</nas_name>


  • Moderator

    I have a firewall hardware with pfSense 2.3.2 64 bit which manages a LAN peer to peer with 5 computers that have Windows 7 SP1 Ultimate and a NAS. All of these network devices have fixed IP.

    your NAS and clients are in the same network segment? LAN?
    Then pfSense has nothing to do with it.



  • @JeGr:

    I have a firewall hardware with pfSense 2.3.2 64 bit which manages a LAN peer to peer with 5 computers that have Windows 7 SP1 Ultimate and a NAS. All of these network devices have fixed IP.

    your NAS and clients are in the same network segment? LAN?
    Then pfSense has nothing to do with it.

    Practically

    firewall hardware: 192.168.1.1
    computers: 192.168.1.2-6
    NAS: 192.168.1.8

    A curiosity: pfSense can act as Master Browser for a LAN peer to peer with Windows?

    Thanks

    Bye


  • Moderator

    A curiosity: pfSense can act as Master Browser for a LAN peer to peer with Windows?

    Again. If all hosts are on the same LAN/subnet, that traffic does NOT go through pfSense. So it has nothing to do with it. I don't get what you are talking about master browser (that is a wording I only know from samba or AD) but as pfSense has no Samba/AD package I don't see what pfSense has to do with it.


  • Rebel Alliance Global Moderator

    No pfsense is not going to be the master browser for the moronic windows network neighborhood.

    I would suggest determine who your master browser is..  Here is a simple tool to do that with..
    https://scottiestech.info/2009/02/14/how-to-determine-the-master-browser-in-a-windows-workgroup/

    Why do you care about the stupid browse list anyway??  Do you not know the name of your NAS?  Why do not just access it via is fqdn ie nas.yourdomain.tld ??

    But to be clear, unless you installed some samba package on pfsense, it has ZERO to do with participation in maintaining the brwose list.  And it being your gateway, it has ZERO to do with broadcast traffic between devices on the same network.  You do understand that the browselist can take long time to fully populate.  Had you recently turned off machines, say your master browser and now a new election was held, then all the clients have to register themselves with the master browser, etc. etc..

    While I do not use that stupid list, I do make sure it works on my network for examples for people that do want to use it ;)  What I would suggest is you turn off the computer browser service on all boxes that you do not want to be the master browser.  You should pick a box that is on 24/7/365 or as close to that as possible to be your master browser..  For example I have my linux box as my master browser running samba.

    $ nbtstat -A 192.168.9.7

    Ethernet:
    Node IpAddress: [0.0.0.0] Scope Id: []

    Host not found.

    Local:
    Node IpAddress: [192.168.9.100] Scope Id: []

    NetBIOS Remote Machine Name Table

    Name              Type        Status
        –-------------------------------------------
        UBUNTU        <00>  UNIQUE      Registered
        UBUNTU        <03>  UNIQUE      Registered
        UBUNTU        <20>  UNIQUE      Registered
        ☺☻__MSBROWSE__☻<01>  GROUP      Registered
        LOCAL          <00>  GROUP      Registered
        LOCAL          <1D>  UNIQUE      Registered
        LOCAL          <1E>  GROUP      Registered