If your server is offline, it truly would be disconnected. If IP address of your server which install controller won;t change, you EAP would connect to the controller again. EAP could remenber the IP address of you controller if you set before using EAP Discover utility. So next time, you could wait for sometime. But it can;t control EAP if EAP have been disconnected.

johnson wrote

If your server is offline, it truly would be disconnected. If IP address of your server which install controller won;t change, you EAP would connect to the controller again. EAP could remenber the IP address of you controller if you set before using EAP Discover utility. So next time, you could wait for sometime. But it can;t control EAP if EAP have been disconnected.

Thanks Johnson,
The server is back online (in fact, it never actually went offline on this occasion, the remote site went offline), however, the EAP doesn't remember that it was managed and the web GUI on the EAP is now available (instead of forbidden access message).

It shouldn't act like this. Can you provide more details about your topology including the subnet assignment

OK, this had improved with the latest 2016 firmware and server 2.2.3, however, when I left work on Friday we had ~35 APs "connected" out of a total of 54 and I have come into work this morning to find only 8 are now 'connected', even though the ones showing as 'disconnected are still online. I have rebooted a couple of APs to see if that makes any difference to their connectivity but it doesn't.
EAP controller is at our Head Office on a 10.201.x.x subnet, all of the stores are on a 10.97.x.x or 10.98.x.x subnet. No problems with the traffic routing, I can see the stores from here and the stores can see the network here. The APs have been showing as 'connected for 3 or 4 weeks now until today. Any help with this would be appreciated.

Thanks

Have you setup any Reboot Schedule feature on your EAP Controller ? If you didn't, you can have a try to configure it for rebooting all of the EAP devices every day to make it work more stably.

tankyou

Thanks Johnson,
The server is back online (in fact, it never actually went offline on this occasion, the remote site went offline), however, the EAP doesn't remember that it was managed and the web GUI on the EAP is now available (instead of forbidden access message).

Thanks Johnson,