RADIUS not working with new vSZ 5.2???

[john_krussaniot]

I currently have a ZoneDirector 3050 which is setup to use RADIUS and it works perfectly. I am trying to configure a new Virtual SmartZone 5.2 that I setup using Hyper-V connect using RADIUS as well, but RADIUS keeps failing. I have tried to replicate the similar settings I have on the ZD3050 but it constantly fails. Has anyone ran into this issue and resolved it successfully?  I'm thinking there are some settings i'm missing somewhere, but I feel like I have tried everything. 

[david_black_594]

This is probably a dumb question, but is the vSZ listed as a RADIUS client?  That's what I forget to do about half the time LOL. 

[john_krussaniot]

At this point, there are no dumb questions. Thank you for responding and yes it has a RADIUS Client. The RADIUS Client for the vSZ is setup almost identical to our ZD3050 RADIUS Client for the exception of the IP Address.

[vineet_nejawal2]

Hi John,

What server are you using ? Are you using proxy or non proxy settings, in non proxy AP is the authenticator and AP subnet or individual IP needs to be added as radius client.
What does the AAA test say, FYI AAA test is just to check the connection between controller and AAA server using PAP and client Auth uses EAP.

Best Regards
Vineet

[john_krussaniot]

Thank you for assisting and any help you can provide. Below are screen shots of the process i'm taking with non-proxy. I have tested proxy, but had the same results. It seems that the Virtual SmartZone does not like the "Connection Request Policy" "NAS Port Type". The ZoneDirector 3050 Controller (10.32.0.2) works perfectly, but not the vSZ (10.42.0.2). RADIUS Client settings are exactly the same except for the IP obviously. 

 













BELOW IS A SUCCESSFUL TEST FROM OUR ZD3050 (10.32.0.2) AND EVENT LOGS.