Ruckus Cloud timing out connecting to our School network

[hardware]

Hi guys

Anyone using Ruckus cloud for their school?

 

Currently at the school we have the following setup

 

1. SSID - Mobile (For mobile devices)

2. SSID - Guest (Guest Users

3. SSID - Curriciulum (Hidden network for curriculum use)

 

1 and 2 works fine users connect enters the password and they are through

 

With 3 it is integrated via Radius NPS which we have installed on our domain controller - radius is working fine as we have tested it

 

Originally we had the controller hosted internally via an IP and we would manage all the APs via the controller which worked fine, but now we have moved over to the cloud having major issues with the cloud controller connecting and speaking to our network all it does is returns "Timeout error messages" when we try to authenticate it both using AD and also Radius

 

The internal controller is still active and for testing purposes we are able to speak to the radius server and authenticate under active directory but its just the cloud controller which is having issues speaking back

 

We have one Host Server and a DC and Data Server machine within the host

Firewall is switched off at the DC including domain firewall everything!

 

Issue is the schools wifi is managed by a 3rd party who has access to the controller but we got access to their Servers and everything so all we do is provide them with a secret key, radius / ad server IP address and a test login which we have and when testing against radius all it does is returns with timeout

 

Anyone come across anything ike this or have any suggestions

 

going crazy

[wright-fi]

I would guess that this issue is due to the different way that the controller architectures talk to the radius server, let me explain my logic first.

 

So with some of the original physical controllers from Ruckus (such as the ZoneDirectors) the AP would talk to the controller and the controller would talk to the RADIUS Server. AP -> Physical Controller -> RADIUS Server

 

With the Cloud it would be very inefficient for this traffic to go to from the AP to the Ruckus Cloud (outside of your network) and then back inside your network to the RADIUS Server. So the AP talks directly to the Radius Server. AP -> RADIUS Server

 

So I would firstly go to the GUI of one of your APs and ping the radius server (just to establish that a connection can be made). Then I would go to your RADIUS Server and confirm that the Ruckus APs have been added as RADIUS clients, previously you probably only added the physical controller as a client.

 

Here are more detailed instructions on how to add new RADIUS Clients: https://docs.microsoft.com/en-us/windows-server/networking/technologies/nps/nps-radius-clients-configure