Why am I unable to see windows file and printer shares of devices that are on the same BSC managed network as as each other?

Version 2

    Q: Why am I unable to see windows file and printer shares of devices that are on the same BSC managed network as as each other?

     

    A: Windows uses broadcast traffic to resolve the netbios names of file and printer shares that are on the same local subnet. By default BlueSecure Access Points (BSAPs) tunnel traffic back to the BlueSecure Controller (BSC) in EtherIP (IP Protocol 97). By default the BSC does not send broadcast traffic back out the EtherIP tunnels therefore other clients will not see the traffic and not be able to see file and printer shares. In order to send broadcast traffic back out the EtherIP tunnels the following routes must be added under network>routing table>create static route entry for the appropriate managed interface.

     

    Broadcast Traffic

     

    Route Destination
    192.168.160.255

     

    Route Gateway
    255.255.255.255

     

    Netmask
    255.255.255.255

     

    Interface
    Managed

     

    This above example assumes we are referring to the managed physical network and the subnet is 192.168.160.0/24. If this is a managed vlan the Interface entry should be populated with the appropriate managed vlan. You may also be required to allow services in the firewall policy of the appropriate role. For example TCP port 139 and UDP port 137,138 for NetBIOS and TCP 445 for SMB.

     

    WARNING. Configuring this broadcast route in networks with large broadcast domains/subnets may cause performance issues.