I have set up my WAP and RADIUS windows server 2008.
the WAP is not actually talking properly to the clients... the laptops can see the WAP but it isn't connected properly. The client won't get an IP, and has limited connectivity.
I tried changing the vLAN settings on the WAP, double checked it is on the right gateway, etc. it is very frustrating. I don't know why it won't 'talk' properly to its clients. obviously i took off Windows firewall just in case on the client.
I have also checked the RADIUS server settings again; it is all set to authenticate users and machines in the domain, has its certificate, is set to PEAP, has the WAP added as a RADIUS client.
I am not quite sure what has happened.
the switch it is on is set to DHCP leasing by the way.
Just beat me to it Gavin Yes, please check NPS logs for any success or failure and provide EAP failure code/description if present.
If your NPS authentication looks successful, then you need to troubleshoot why you aren't getting a DHCP address. I presume this is an autonomous setup? Could you provide the run-config of your AP and the AP switchport run-config? Also the run-config of the gateway interface and the DHCP scope config.
NPS logs on the server have errors all over it; resetting WAP security to see if i can fix it. the WAP isn't here with me, so I am getting someone on site to use their laptop and see if I can get a connection happening.
Transferring Crash file from standby: Login to the Active WLC in HA.
From CLI: (Cisco Controller) >transfer upload datatype crash (Cisco
Controller) >transfer upload filename (Cisco
Controller) >transfer upload mode tftp (Cisco Controller) >transfer
This is the start of a display filter cross reference between Wireshark
and OmniPeek. The 1st installment is a table of advanced filters. More
filters will be added as time allows. It is a living doc, so check back
for changes every so often Please feel f...