Wireless Access

last person joined: 23 hours ago 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Back to discussions
Expand all | Collapse all

network discovery and file sharing not working

This thread has been viewed 1 times

  • 1.  network discovery and file sharing not working

    Posted Jun 26, 2017 04:23 PM

    I have an aruba controller 7005 with AP 105's. I have three SSID's.  Two are trusted and one is a guest network. Neither of the trusted networks are properly doing network discovery and file sharing. 

     

    SSID1 is 10.1.10.0/24 and getting DHCP from the domain controller. 

    SSID2  is 172.16.0.0./24 and issuing it's own DHCP IP's. Both have access to the 10.1.10.0/24 core network. 

     

    The controller is connected to the core switch via port 0 and they are trunked on port 0.

     

    What can i do to get network discovery and file sharing working on the controller? 

     



  • 2.  RE: network discovery and file sharing not working

    EMPLOYEE
    Posted Jun 26, 2017 04:36 PM

    Please be more specific:

     

    What client are you using for file sharing?

    What server?

    Are they on the same subnet?



  • 3.  RE: network discovery and file sharing not working

    Posted Jun 26, 2017 05:00 PM

    The client is a Windows 10 laptop connected to the SSID with access to the 10.1.10.0/24 subnet.

     

    The file server is a file server on the 10.1.10.0 /24 subnet. 

     

    The client is on the 10.1.10.0 /24 subnet. 

     

    I can ping the file server from the client and the client from the file server. 

     

    I cannot access the shares on the file server from the client. 

     

    The DHCP server is the DC on the 10.1.10.0 /24 subnet. 

     

     

     

     

     

     



  • 4.  RE: network discovery and file sharing not working

    EMPLOYEE
    Posted Jun 26, 2017 05:12 PM

    Are you using the server name to access the share?  You need to supply the correct DNS suffix via your dhcp server so that you can address servers by their proper DNS name...