It may be that the wireless client needs to be in the same VLAN as your IAP's IP address in order to access it. With the AP in VLAN 72 and the client in VLAN 144, there may be asymetric routing, breaking the WebUI communication. If the AP is in VLAN 72 (native VLAN for the AP and switchport), you should connect the wireless client to VLAN 1 (native seen from the AP).
------------------------------
Herman Robers
------------------------
If you have urgent issues, always contact your Aruba partner, distributor, or Aruba TAC Support. Check
https://www.arubanetworks.com/support-services/contact-support/ for how to contact Aruba TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.
In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
------------------------------
Original Message:
Sent: Mar 11, 2024 02:09 PM
From: Reggie Lincoln
Subject: wireless PC cannot access aruba IAP webadmin (Aruba AP 505 AP)
PC and wireless PC are assigned the same DHCP server address. PC can access aruba IAP webadmin, but wireless PC cannot access aruba IAP webadmin
when the ap try to communicate on the network its getting assigned to vlan 72 by a switch.
When the pc is directly connected to the switch through vlan144, the login to manage aruba IAP webadmin is successful
However, I am unable to connect to aruba IAP webadmin via a wireless pc which is also vlan 144.
But I can ping aruba IAP webadmin successfully.
Does anyone know what's going on?
Please help me, thank you! (Confused boy)
But I can ping aruba IAP webadmin successfull