Remote Networking

New Contributor

Remote AP's not working since ISA sever implemented

On friday I implemented an ISA server and since then my RAPS don't work. UDP 4500 is open an I can see the RAP contacting the controller. Also when I provision a new RAP it doesn't show up on the controller, when the RAP reboots only the power and ethernet lights come on. :confused:

Remote AP's not working since ISA sever implemented

By ISA, I assume you actually mean IAS server (aka. Radius server).

If that is the case I would think that the source of the problem is that
the RAPs are now being directed at the new IAS server for authentication
instead of the controller, and thus they fail to connect. The good
news is that the remedy is pretty easy/quick.

First, I would check the authentication areas of the controller
configuration to see if the RAPs are no longer authenticating with the
internal database and are instead trying to authenticate against the
*new* IAS server.

You could do this by two means:
1) Audit the logs on your new IAS server... you would see the RAPs
coming in and being denied, or
2) Check the aaa settings for VPN connectivity and ensure that IAS is
-not- at the top of the list, but rather that internal DB is (which is
where you would have had the RAP 'user' accounts).

The remedy is to ensure the RAPs/VPN is set to authenticate against the
internal/local database dB.

New Contributor

ISA (Internet Security and Acceleration Server)

Thanks for the quick response but it's a ISA server i.e firewall
Guru Elite


Ok, do you have UDP 4500 open in both directions?

Is your setup like the article here:

*Answers and views expressed by me on this forum are my own and not necessarily the position of Aruba Networks or Hewlett Packard Enterprise.*
ArubaOS 8.5 User Guide
InstantOS 8.5 User Guide
Airheads Knowledgebase
Airheads Learning Videos
Aruba Central Documentation
ArubaOS Consolidated Release Notes
Aruba Technical Webinars
Search Airheads
Showing results for 
Search instead for 
Did you mean: