WIFI Controller C5210 - "Unable to connect to RADIUS servers"
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎03-09-2016 07:38 AM
Greetings,
We are using an extremE controller C5210 with WS-AP3715I Access Points and are getting a "Unable to connect to RADIUS servers" when ever we want to connect.
We have rebooted the radius server and the controller to NO avail.
Any pointers?
Thanks,
Kombe
We are using an extremE controller C5210 with WS-AP3715I Access Points and are getting a "Unable to connect to RADIUS servers" when ever we want to connect.
We have rebooted the radius server and the controller to NO avail.
Any pointers?
Thanks,
Kombe
18 REPLIES 18
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎03-10-2016 03:27 AM
Hi
It looks like your radius server/config has some kind of issue, take a look at this thread and see if it helps (it's in multiple parts) http://lists.freeradius.org/pipermail/freeradius-users/2013-March/065439.html
-Gareth
It looks like your radius server/config has some kind of issue, take a look at this thread and see if it helps (it's in multiple parts) http://lists.freeradius.org/pipermail/freeradius-users/2013-March/065439.html
-Gareth
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎03-10-2016 03:17 AM
Tested the RADIUS WLAN-SERVICE and got:
RADIUS Test Results:
Sending EAP authentication request to Radius Server with user admin on vns_name Link
Please wait while all configured Radius Servers on this VNS are attempted as needed ...
Test Completed.
The Radius Server did not authenticate the user admin on Link VNS. Error: ACCESS_REJECTED.
RADIUS Test Results:
Sending EAP authentication request to Radius Server with user admin on vns_name Link
Please wait while all configured Radius Servers on this VNS are attempted as needed ...
Test Completed.
The Radius Server did not authenticate the user admin on Link VNS. Error: ACCESS_REJECTED.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎03-09-2016 02:16 PM
Is your Radius Server listening?
If your Radius Server is linux based, netstat -l (L for Listen) to see if that port is listening.
Telnet IP.of.radius.server Port.radius.runs.on to see if you connect. first local telnet, then remote telnet
If your Radius Server is linux based, netstat -l (L for Listen) to see if that port is listening.
Telnet IP.of.radius.server Port.radius.runs.on to see if you connect. first local telnet, then remote telnet
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎03-09-2016 01:38 PM
That's a good sign!
Next, try the following...
1. Under the VNS tab---> WLAN-Service---> Select the RADIUS WLAN-Service
2. Click on the Auth & Acct tab
3. Click on the RADIUS server in your list, then click on the TEST button.
4. Enter in a User ID:
5. The process will fail (no pass is sent) but see if you get back something similar to the following:
The Radius Server did not authenticate the user dhyde on PoE VNS. Error: ACCESS_REJECTED.
Next, try the following...
1. Under the VNS tab---> WLAN-Service---> Select the RADIUS WLAN-Service
2. Click on the Auth & Acct tab
3. Click on the RADIUS server in your list, then click on the TEST button.
4. Enter in a User ID:
5. The process will fail (no pass is sent) but see if you get back something similar to the following:
The Radius Server did not authenticate the user dhyde on PoE VNS. Error: ACCESS_REJECTED.
Doug Hyde
Director, Technical Support / Extreme Networks
Director, Technical Support / Extreme Networks
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎03-09-2016 01:32 PM
Yes it can reach.
Results:
ping
PING 10.1.0.135 (10.1.0.135) 56(84) bytes of data.
64 bytes from 10.1.0.135: icmp_seq=1 ttl=63 time=0.472 ms
64 bytes from 10.1.0.135: icmp_seq=2 ttl=63 time=0.116 ms
64 bytes from 10.1.0.135: icmp_seq=3 ttl=63 time=0.122 ms
--- 10.1.0.135 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 0.116/0.236/0.472/0.167 ms
Results:
ping
PING 10.1.0.135 (10.1.0.135) 56(84) bytes of data.
64 bytes from 10.1.0.135: icmp_seq=1 ttl=63 time=0.472 ms
64 bytes from 10.1.0.135: icmp_seq=2 ttl=63 time=0.116 ms
64 bytes from 10.1.0.135: icmp_seq=3 ttl=63 time=0.122 ms
--- 10.1.0.135 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 0.116/0.236/0.472/0.167 ms
