topic Re: Wlc Radius authentication in Wireless

Wlc Radius authentication

studmuffin — Tue, 27 Sep 2022 23:03:51 GMT

I keep getting this error but i with different ID I have now idea what is cuasing it i had it working before then i moved my dc vm;s and did some work moved them back on and then it stopped working i cant figure out what is wrong

Log System Time Trap

0	Tue Sep 27 05:46:13 2022	RADIUS server 192.168.40.58:1812 failed to respond to request (ID 175) for client e6:6c:be:80:34:a0 / user 'ThePlague'
1	Tue Sep 27 05:42:37 2022	RADIUS server 192.168.40.58:1812 failed to respond to request (ID 174) for client e6:6c:be:80:34:a0 / user 'ThePlague'
2	Tue Sep 27 05:29:46 2022	RADIUS server 192.168.40.55:1812 failed to respond to request (ID 165) for client e6:6c:be:80:34:a0 / user 'ThePlague'
3	Tue Sep 27 05:16:40 2022	RADIUS server 192.168.40.55:1813 failed to respond to request (ID 18) for client a0:88:69:01:56:62 / user 'a0-88-69-01-56-62'
4	Tue Sep 27 05:16:26 2022	RADIUS server 192.168.40.55:1813 failed to respond to request (ID 17) for client a0:88:69:01:56:62 / user 'a0-88-69-01-56-62'
5	Tue Sep 27 05:12:19 2022	RADIUS server 192.168.40.55:1812 failed to respond to request (ID 164) for client e6:6c:be:80:34:a0 / user 'ThePlague'
6	Tue Sep 27 05:12:12 2022	RADIUS server 192.168.40.55:1812 failed to respond to request (ID 163) for client e6:6c:be:80:34:a0 / user 'ThePlague'
7	Tue Sep 27 05:06:32 2022	RADIUS server 192.168.40.55:1812 failed to respond to request (ID 162) for client e6:6c:be:80:34:a0 / user 'ThePlague'
8	Tue Sep 27 05:02:55 2022	RADIUS server 192.168.40.55:1812 failed to respond to request (ID 65) for client a0:88:69:01:56:62 / user 'host/Studmuffin-Lab.Studmuffin.com'
9	Tue Sep 27 05:02:38 2022	RADIUS server 192.168.40.55:1812 failed to respond to request (ID 161) for client e6:6c:be:80:34:a0 / user 'ThePlague'
10	Tue Sep 27 04:56:39 2022	RADIUS server 192.168.40.55:1812 failed to respond to request (ID 160) for client e6:6c:be:80:34:a0 / user 'ThePlague'
11	Tue Sep 27 04:56:23 2022	RADIUS server 192.168.40.55:1812 failed to respond to request (ID 159) for client e6:6c:be:80:34:a0 / user 'ThePlague'
12	Tue Sep 27 04:46:54 2022	RADIUS server 192.168.40.55:1812 failed to respond to request (ID 139) for client 80:fd:7a:4a:21:94 / user 'Studmuffin.com\ThePlague'
13	Tue Sep 27 04:46:25 2022	RADIUS server 192.168.40.55:1812 failed to respond to request (ID 138) for client 80:fd:7a:4a:21:94 / user 'Studmuffin.com\ThePlague'
14	Tue Sep 27 04:45:52 2022	RADIUS server 192.168.40.55:1812 failed to respond to request (ID 137) for client 80:fd:7a:4a:21:94 / user 'Studmuffin.com\ThePlague'
15	Tue Sep 27 04:45:11 2022	RADIUS server 192.168.40.55:1812 failed to respond to request (ID 136) for client 80:fd:7a:4a:21:94 / user 'Studmuffin.com\ThePlague'
16	Tue Sep 27 04:44:39 2022	RADIUS server 192.168.40.55:1812 failed to respond to request (ID 135) for client 80:fd:7a:4a:21:94 / user 'Studmuffin.com\ThePlague'
17	Tue Sep 27 04:44:19 2022	RADIUS server 192.168.40.55:1812 failed to respond to request (ID 134) for client 80:fd:7a:4a:21:94 / user 'Studmuffin.com\ThePlague'
18	Tue Sep 27 04:44:12 2022	RADIUS server 192.168.40.55:1812 failed to respond to request (ID 158) for client e6:6c:be:80:34:a0 / user 'ThePlague'
19	Tue Sep 27 04:42:00 2022	RADIUS acct-server 192.168.40.55:1813 available
20	Tue Sep 27 04:28:16 2022	RADIUS server 192.168.40.55:1813 failed to respond to request (ID 3) for client a0:88:69:01:56:62 / user 'a0-88-69-01-56-62'
21	Tue Sep 27 04:26:59 2022	RADIUS server 192.168.40.55:1813 failed to respond to request (ID 2) for client a0:88:69:01:56:62 / user 'a0-88-69-01-56-62'
22	Tue Sep 27 04:15:39 2022	Noise Profile Updated to Pass for Base Radio MAC: 3c:08:f6:9a:b3:e0 and slotNo: 0
23	Tue Sep 27 04:12:29 2022	Noise Profile Failed for Base Radio MAC: 3c:08:f6:9a:b3:e0 and slotNo: 0
24	Tue Sep 27 03:22:11 2022	RADIUS ACCT Server 192.168.40.55:1813 deactivated in global list
25	Tue Sep 27 03:22:11 2022	RADIUS server 192.168.40.55:1813 failed to respond to request (ID 0) for client a0:88:69:01:56:62 / user 'a0-88-69-01-56-62'
26	Tue Sep 27 03:17:54 2022	RADIUS server 192.168.40.55:1813 failed to respond to request (ID 4) for client 46:26:69:af:1a:c4 / user '46-26-69-af-1a-c4'
27	Tue Sep 27 03:17:20 2022	RADIUS server 192.168.40.55:1812 failed to respond to request (ID 157) for client e6:6c:be:80:34:a0 / user 'ThePlague'
28	Tue Sep 27 03:13:42 2022	RADIUS server 192.168.40.55:1813 failed to respond to request (ID 3) for client 46:26:69:af:1a:c4 / user '46-26-69-af-1a-c4'
29	Tue Sep 27 03:13:22 2022	RADIUS server 192.168.40.55:1812 failed to respond to request (ID 156) for client e6:6c:be:80:34:a0 / user 'ThePlague'
30	Tue Sep 27 03:10:31 2022	RADIUS ACCT Server 192.168.40.55:1813 deactivated in global list
31	Tue Sep 27 03:10:31 2022	RADIUS acct-server 192.168.40.55:1813 unavailable
32	Tue Sep 27 03:10:31 2022	RADIUS server 192.168.40.55:1813 failed to respond to request (ID 2) for client 46:26:69:af:1a:c4 / user '46-26-69-af-1a-c4'
33	Tue Sep 27 03:09:57 2022	RADIUS server 192.168.40.55:1812 failed to respond to request (ID 155) for client e6:6c:be:80:34:a0 / user 'ThePlague'
34	Tue Sep 27 03:08:13 2022	RADIUS server 192.168.40.55:1813 failed to respond to request (ID 1) for client 46:26:69:af:1a:c4 / user '46-26-69-af-1a-c4'
35	Tue Sep 27 03:07:39 2022	RADIUS server 192.168.40.55:1812 failed to respond to request (ID 154) for client e6:6c:be:80:34:a0 / user 'ThePlague'
36	Tue Sep 27 03:07:30 2022	RADIUS server 192.168.40.55:1813 failed to respond to request (ID 0) for client 46:26:69:af:1a:c4 / user '46-26-69-af-1a-c4'
37	Tue Sep 27 03:06:56 2022	RADIUS server 192.168.40.55:1812 failed to respond to request (ID 153) for client e6:6c:be:80:34:a0 / user 'ThePlague'
38	Tue Sep 27 03:05:21 2022	RADIUS server 192.168.40.55:1812 failed to respond to request (ID 152) for client e6:6c:be:80:34:a0 / user 'ThePlague'
39	Tue Sep 27 03:05:04 2022	RADIUS server 192.168.40.55:1812 failed to respond to request (ID 151) for client e6:6c:be:80:34:a0 / user 'ThePlague'
40	Tue Sep 27 03:04:47 2022	RADIUS server 192.168.40.55:1812 failed to respond to request (ID 150) for client e6:6c:be:80:34:a0 / user 'ThePlague'
41	Tue Sep 27 02:52:15 2022	RADIUS server 192.168.40.55:1812 failed to respond to request (ID 55) for client a0:88:69:01:56:62 / user 'host/Studmuffin-Lab.Studmuffin.com'
42	Tue Sep 27 02:51:53 2022	RADIUS server 192.168.40.55:1812 failed to respond to request (ID 149) for client e6:6c:be:80:34:a0 / user 'ThePlague'
43	Tue Sep 27 02:51:37 2022	RADIUS server 192.168.40.55:1812 failed to respond to request (ID 148) for client e6:6c:be:80:34:a0 / user 'ThePlague'
44	Tue Sep 27 02:49:09 2022	RADIUS server 192.168.40.55:1812 failed to respond to request (ID 147) for client e6:6c:be:80:34:a0 / user 'Studmuffin.com\ThePlague'
45	Tue Sep 27 02:47:43 2022	RADIUS server 192.168.40.55:1812 failed to respond to request (ID 146) for client e6:6c:be:80:34:a0 / user 'Studmuffin.com\ThePlague'
46	Tue Sep 27 02:47:26 2022	RADIUS server 192.168.40.55:1812 failed to respond to request (ID 145) for client e6:6c:be:80:34:a0 / user 'Studmuffin.com\ThePlague'
47	Tue Sep 27 02:45:01 2022	RADIUS server 192.168.40.55:1812 failed to respond to request (ID 13) for client f8:1a:2b:33:58:4b / user 'ThePlague'
48	Tue Sep 27 02:44:43 2022	RADIUS server 192.168.40.55:1812 failed to respond to request (ID 12) for client f8:1a:2b:33:58:4b / user 'ThePlague'
49	Tue Sep 27 02:23:56 2022	RADIUS server 192.168.40.55:1812 failed to respond to request (ID 11) for client f8:1a:2b:33:58:4b / user 'ThePlague'
50	Tue Sep 27 02:23:39 2022	RADIUS server 192.168.40.55:1812 failed to respond to request (ID 10) for client f8:1a:2b:33:58:4b / user 'ThePlague'
51	Tue Sep 27 02:22:25 2022	RADIUS server 192.168.40.55:1812 failed to respond to request (ID 144) for client e6:6c:be:80:34:a0 / user 'ThePlague'

That is just some of the logs any ides?

Re: Wlc Radius authentication

studmuffin — Wed, 28 Sep 2022 01:07:23 GMT

<Event><Timestamp data_type="4">09/27/2022 20:03:55.824</Timestamp><Computer-Name data_type="1">STUDMUFFIN-DC</Computer-Name><Event-Source data_type="1">IAS</Event-Source><User-Name data_type="1">46-26-69-af-1a-c4</User-Name><NAS-Port data_type="0">13</NAS-Port><NAS-IP-Address data_type="3">192.168.100.5</NAS-IP-Address><Framed-IP-Address data_type="3">192.168.30.50</Framed-IP-Address><Framed-IPv6-Prefix data_type="2">0040FE800000000000000000000000000000</Framed-IPv6-Prefix><NAS-Identifier data_type="1">StudmuffinWireless</NAS-Identifier><Vendor-Specific data_type="2">00003763010600000002</Vendor-Specific><Acct-Session-Id data_type="1">633253d7/46:26:69:af:1a:c4/8648</Acct-Session-Id><NAS-Port-Type data_type="0">19</NAS-Port-Type><Acct-Authentic data_type="0">3</Acct-Authentic><Tunnel-Type data_type="0">13</Tunnel-Type><Tunnel-Medium-Type data_type="0">6</Tunnel-Medium-Type><Tunnel-Pvt-Group-ID data_type="1">30</Tunnel-Pvt-Group-ID><Event-Timestamp data_type="4">09/27/2022 07:52:10</Event-Timestamp><Acct-Status-Type data_type="0">3</Acct-Status-Type><Acct-Input-Octets data_type="0">7259227</Acct-Input-Octets><Acct-Input-Gigawords data_type="0">0</Acct-Input-Gigawords><Acct-Output-Octets data_type="0">19371290</Acct-Output-Octets><Acct-Output-Gigawords data_type="0">0</Acct-Output-Gigawords><Acct-Input-Packets data_type="0">27967</Acct-Input-Packets><Acct-Output-Packets data_type="0">28876</Acct-Output-Packets><Acct-Session-Time data_type="0">22482</Acct-Session-Time><Acct-Delay-Time data_type="0">0</Acct-Delay-Time><Calling-Station-Id data_type="1">46-26-69-af-1a-c4</Calling-Station-Id><Called-Station-Id data_type="1">f4-7f-35-b6-a8-a0</Called-Station-Id><Client-IP-Address data_type="3">192.168.100.5</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name data_type="1">StudmuffinWireless</Client-Friendly-Name><Cisco-AV-Pair data_type="1">audit-session-id=c0a8640500000b90633253d7</Cisco-AV-Pair><Proxy-Policy-Name data_type="1">StudsUsers</Proxy-Policy-Name><Packet-Type data_type="0">4</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event>

That is what i get in my wireless logs from accounting so i dont think it is connection or firewall issue if i am getting updates in accounting

Re: Wlc Radius authentication

Ambuj M — Wed, 28 Sep 2022 02:14:29 GMT

can you run aaa test to your radius and share what you see on wlc as well as on radius

test aaa radius username <user name> password <password> wlan-id <wlan-id> ap-group <apgroup-name> server-index <server-index>

Re: Wlc Radius authentication

studmuffin — Wed, 28 Sep 2022 02:24:48 GMT

what is the server-index and how do i find it

Re: Wlc Radius authentication

studmuffin — Wed, 28 Sep 2022 02:30:29 GMT

Does that look correct

Re: Wlc Radius authentication

studmuffin — Wed, 28 Sep 2022 02:31:35 GMT

that is the result

Re: Wlc Radius authentication

Arshad Safrulla — Wed, 28 Sep 2022 21:24:57 GMT

Looks like your radius servers are not reachable from WLC. Please check whether the Radius source interface of WLC can reach the Radius server, if there is any firewall/ routers in the path please make sure that you have required routing/policies are created to allow the traffic. From Radius server side check it's availability and reachability to its gateway and to the NAD. If avaialble and reachability is fine, please check whether the required services are running as expected.

If the issue persists, please share more info on WLC model, code etc. and Radius server model, code etc.

Re: Wlc Radius authentication

studmuffin — Wed, 28 Sep 2022 21:35:40 GMT

there is no firewall rules in between the radius server and the wlc the wlc can ping the radius server and accounting works The radius server is running a vmware esxi vm and the hardware is connected via trunk ports to much switch the router is a cisco 2901 router doing router on a stick and there are no access lists on the interfaces there is one ip route out to the internet and no nat there is a firewall but that would have nothing to do with it i have tried it with both windows firewall on and off and no change i am not sure what services are required but i checked to make sure nps was running and i even gave it a restart

Re: Wlc Radius authentication

Ambuj M — Fri, 30 Sep 2022 13:26:57 GMT

sorry for the late reply.

Re: Wlc Radius authentication

Ambuj M — Fri, 30 Sep 2022 13:27:46 GMT

can you share the full test command you ran ?

Re: Wlc Radius authentication

bsmagulov1 — Mon, 05 Dec 2022 11:23:02 GMT

Here you can find some advice on the topic:

https://youtu.be/lZl_jv1keg8