Wireless Access

last person joined: 21 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

Website access denied on wireless, but accessible on hard wired, same subnet.

This thread has been viewed 3 times

  • 1.  Website access denied on wireless, but accessible on hard wired, same subnet.

    Posted May 03, 2019 03:03 PM

    We have setup a WPA-2 Enterprise network for our teacher computers.  We don't block Netflix, however, it is not accessible over wifi.  Our hard-wired computers are on the same subnet, and they can access Netflix. Any thoughts?  We have no "website blocking" software on the computer.



  • 2.  RE: Website access denied on wireless, but accessible on hard wired, same subnet.

    EMPLOYEE
    Posted May 03, 2019 03:17 PM

    It is possible that the Wireless LAN Controller is natting everyone out of the same private ip address, and that ip address is not allowed to use the internet.



  • 3.  RE: Website access denied on wireless, but accessible on hard wired, same subnet.

    Posted May 03, 2019 03:26 PM

    Thanks for the reply, to clarify...

     

    Netflix.com is the issue, other websites are accessible.  The teachers can log in to Netflix, but pictures and movies don't work.



  • 4.  RE: Website access denied on wireless, but accessible on hard wired, same subnet.

    EMPLOYEE
    Posted May 03, 2019 03:38 PM

    Do you have an ACL on the teach role blocking specific traffic?



  • 5.  RE: Website access denied on wireless, but accessible on hard wired, same subnet.

    Posted May 03, 2019 05:09 PM

    Sorry, newbie here, where would I find the ACL settings in the portal?



  • 6.  RE: Website access denied on wireless, but accessible on hard wired, same subnet.

    MVP EXPERT
    Posted May 05, 2019 06:02 AM

    Look at the Users on the controller and their assigned Role, different ways to do this via the GUI and verions. 

    If you do this via the CLI it will give you the info you need :

     

    show user-table <-- to identify which (User)Role is assigned to the client.
show rights [USER ROLE NAME] <-- to determine the ACL's applied to the client.