802.1x wired EAP requestes dropped by clients

Dears,
i am facing the following problems with most of my windows 7 machines in the network.
we have an Aruba CPPM NAC solution that we integrated with our Domain Controller.
Once a windows 7 clients try to connect to the network everything works well then after a couple of seconds the client a disconnected. i did some sniffing on the network and found that the authentication is working well and the NAC starts sending EAP requests
to the client and the client answers with EAP replies. everything works well for the first 4 requests then when the 5th request is sent to the client, the client drops it and no replies are sent back to the NAC solution.
it's a very weird problem and can't understand why it's always on the 5th EAP request the client stops replying.
I tried formatting one of the PCs and joining it to the domain and testing the solution, everything went well but it won't be possible for me to format 2000 PCs to get the solution running.
is it possible to get your support with this issue?
regards,
Joseph Salameh.

Hi,
In some cases, routers or firewalls drop packets because they are configured to discard packets that require fragmentation.
Did you use NPS for authentication?
Follow this procedure to lower the maximum size that NPS uses for EAP payloads by adjusting the Framed-MTU attribute in a network policy.
Configure the EAP Payload Size
http://technet.microsoft.com/en-us/library/cc755205%28v=ws.10%29
Hope this helps.

Similar Messages

New 802.11 AC Airport Extreme Drops Inactive client

I have a new Airport Extreme 802.11 AC less than one week. I have noticed that a ROKU 3 drops if inactive for short period. The device is about 3 ft from the new Airport.
This never happened with the previous Gen 5 Airport Extreme.
Any advice?

What version of firmware are you running on the 802.11ac?
There is a 7.7.1 update with USB fixes - http://support.apple.com/kb/DL1665
After my update to 7.7.1, I still cannot see the Seagate 3TB HDD.
The disk works on a 2nd Gen 802.11n Extreme.
This is

IAS and CTA 802.1x wired client?

Hi,
We have IAS working with 802.1X authentication. All is good except when we enable dynamic VLAN assignment we come across the Winlogon issue as per MS KB article 935638.
We do however have available the CTA 802.1X wired client. From what I have read though it requires ACS due to use of EAP-FAST. Is this correct or is there some way I can get CTA 802.1X wired client working with MS IAS RADIUS?
Thank you

You will have to use ACS for authenticating using EAP-FAST for CTA 802.1x wired clients. It is not possible to get CTA 802.1X wired client working with MS IAS RADIUS.

ISE-5443 RADIUS request dropped due to reaching EAP sessions limit

Hi Guys,
I am getting the below error message from two PSNs (out of 4) & resulting 95% failed authentications on ISE
"5443 RADIUS request dropped due to reaching EAP sessions limit"
Could not find any documents/reference & trying to get on hold TAC in the mean time.
If anyone of you know what could it be, pls share your inputs
TIA
Rasika

Hi Scott,
Thanks for that..
here is bit more information about this evnts log in ISE system (1.2 Patch 4).
Event: 5405 RADIUS Request dropped
Failure Reason :5443 RADIUS request dropped due to reaching EAP sessions limit
Resolution : Wait a few seconds before invoking another RADIUS request with new EAP session. If system overload continues to occur, try restarting the ISE Server
Root cause: A RADIUS request was dropped due to reaching EAP sessions limit. This condition can be caused by too many parallel EAP authentication requests.
Worked with TAC & restarted the service of one PSN node & that brings that node to normal condition & removed the other PSN form the F5 pool until TAC analyze gathered support bundle from that.
It is not heavily loaded environment (3k wireless clients) at the moment & bit scary since we are expecting around 15k when students are back in early March. Authentication failure rate is around 100 in every 15-20s interval. Not sure what is the limitation of the ISE system itself to handle number of EAP sessions per second.
Rasika

Problem in ACS5.1 : "EAP session timed out", "RADIUS Request dropped "

Hi .
Part of my access points do not want to authenticate wi-fi users (through Radius server and Microsoft AD) .
The scheme is: wi-fi PC-access point -ACS server 5.1 (Radius)-Microsoft AD
After I configured some AP, next logs we can see :
EAP session timed out (many)
RADIUS Request dropped (many)
Could not establish connection with ACS Active Directory agent
User's Groups retrieval from Active Directory failed
The user is not found in the internal users identity store.
Another part of devices (AP) works well.
Anyone can help me to solve this problem please?

Hi Nicolas.
In logs usually we see some steps of beginning relations between devices. But here we see only one log line:
What can it mean?
The other messages seem to indicate that there is a problem with your AD. Did you test the bind ? Can you retrieve the AD groups list from ACS ?
Yes, we tested relations between AD and ACS, AD groups list retrieve fine from AD. In addition half of devices in network works fine: wi-fi devices authenticates excellent .
Do you use AD with the ACS for another part of your network that would be working fine ?
Yes, there is single AD and ACS.

After ISE 1.2 upgrade I get "5413 RADIUS Accounting-Request dropped."

Hello,
I have a two admin node setup for ISE. I just upgraded one of my two ISE Admin nodes to Version 1.2. I still have one of my admin nodes at 1.1.4. When I disable my Version 1.1.4 node and allow wireless authentications to be handled by the Version 1.2 node I get the message..."5413 RADIUS Accounting-Request dropped". None of my wireless edge devices will be allowed on the network during this time. When I re-enable my 1.1.4 node my wireless devices are then allowed on the network.
I am currently using ISE to authenticate wireless connectivity.
I also get the failure reason... "11038 RADIUS Accounting-Request header contains invalid Authentication field".
Any ideas?
Bob

The 5413 RADIUS Accounting-Request dropped may be because the session was active on ISE1 and is now sending update messages to ISE2. Also, verify your shared secret radius key matches on both the wlc and ISE servers. I would try clearing the WLC connection for the test user when switching. Just turning off wireless and back on doesn't do it. Also, are you using PEAP-MSChapv2 or EAP-TLS for authenticating the clients. What type of certificate is presented, public or private?

Windows 7 802.1x (Wired) Authentication Failure when logging into Lync 2010

Hi
My company has implemented 802.1x Wired authentication, we use GPO to specify a
Wired Profile that uses a COMPUTER certificate.
We are finding that when a Windows 7 laptop comes out of sleep or hibernation, the laptop fails 802.1x authentication and does not connect to the network.
This issue only occurs intermittently, but have been proven to occur only when Lync 2010 is open. If we close Lync 2010 the issue does not occur. Lync 2010 installs a self signed USER certificate for authentication.
I am aware that there are some issues around Windows 7 not selecting the correct certificate when responding to authentication requests (KB2710995,
KB2769121) but these always specify that the issue occurs when 802.1x authentication uses USER certificates, not a mix of USER and COMPUTER. We have installed these hotfixes and the
issue still occurs.

Hi,
From the description, you suspect the DHCP request cause this issue. Would you please send us the packets? Since it seems that you have looked into the traffic and found some clues.
Meanwhile, I found the following hotfix which may related to this issue.
No response to 802.1X authentication requests after authentication fails on a computer that is running Windows 7 or Windows Server 2008 R2 http://support.microsoft.com/kb/980295/en-us
Next Action Plan:
1.Clean Boot
a. Click Start, click Run, type "msconfig" (without the quotation marks) in the Open box, and then click OK.
b. In the Startup tab, click the "Disable All" button.
c. In the Services tab, check the "Hide All Microsoft Services" checkbox, and then click the "Disable All" button.
======================================================
Clean Boot + binary search
In a Clean Boot, all the 3rd party services and startup programs are disabled. If the server can start normally in Clean Boot, we can be sure that the issue was caused by some 3rd party service or application. And then we can do a "binary search".
You can enable half of all the services in Services tab, and then restart the server to check the result. If the issue reoccurs, it means the culprit is in this list; if not, the culprit is in the other half. And then, we can continue the binary search, until
we find out the root cause. Please let me know if this action plan is OK for you.
2.Collect etl trace on the problematic client.
netsh trace start capture=yes overwrite=yes tracefile=c:\net.etl filemode=circular
****Try to reproduce this issue****
netsh trace stop
Please send the net.etl to us for underlying analysis.
For any concerns, please let us know.
Best regards,
Steven Song
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

ACS 5.2 Error message: 5405 RADIUS Request dropped

The error message "5405 RADIUS Request dropped", what does it meen ?.
We have implemented 802.1X on a C4506 switch running IOS 12.2(53), it has worked fine for about 3 months but now I get users not able to authenticate. In the loggs on the ACS I get the obove message.
ACS 5.2 is running 5.2.0.26 Build 3075.
Has anyone have hade the same problem ?

It's fixed in 5.3...
http://www.cisco.com/en/US/docs/net_mgmt/cisco_secure_access_control_system/5.3/release/notes/acs_53_rn.html
...or stop/start ACS as a workaround till it's happen again.
Kind regards,
Ron

802.1x and EAP

Hi every body
How is everybody doing?
Does 802.1x require the usage of EAP ? or can we use 802.1x without using EAP?
thanks and have a geat weekend.

hi sarah,
802.1x uses the EAP framework if you will. As you pointed out, it uses supplicant, authenticator, authentication server to authenticate, authorise a client.
I don't think you can use 802.1x without EAP because you have to some framework to allow the client to authenticate etc.
thats just my opinion
HTH
Kishore

EAP-Request Max Retries with no backup Radius

Hello,
Could you please explain what happens in case of a radius still alive , but not responding to a particular Eap-request ( Client in a blocked list..)
WLC is 5508 : 6.0.199
There is no backup radius
The "show advanced eap is:
EAP-Identity-Request Timeout (seconds)........... 30
EAP-Identity-Request Max Retries................. 2
EAP Key-Index for Dynamic WEP.................... 0
EAP Max-Login Ignore Identity Response........... enable
EAP-Request Timeout (seconds).................... 30
EAP-Request Max Retries.......................... 2
EAPOL-Key Timeout (milliseconds)................. 1000
EAPOL-Key Max Retries............................ 2
Does the WLC try 2 times, and than stop transmitting this particular request ?
Regards
Michel Misonne

Well, it seems that your WLC is configured so that it can retry 2 times, if no response within the timeout the deauthentication will be send to the wireless clients making the wireless client ATTEMPT to start the process again... the whole EAP process
For further details check this 2 links:
http://www.cisco.com/en/US/tech/tk722/tk809/technologies_configuration_example09186a0080665d18.shtml
https://supportforums.cisco.com/docs/DOC-12110

Invalid Message Authenticator in EAP Request

Hi,
I am attemping to configure Infratructure authentication for WDS and WPA/PEAP Client authentication using ACS 4.1(1) Build 23 from an Aironet 1210 running IOS 12.3(8)JEC.
I have a production ACS server that has both LEAP and PEAP enabled under the global configuration options.
The access point has been correctly defined as a NAS using RADIUS-Aironet on the ACS server. The Access point has ACS defined as a RADIUS server and the shared secret set the same as the NAS definition within ACS.
For both WDS Infrastructure authentications(LEAP) and client authentication requests to the access point using PEAP I receive the following message in the ACS failed log:
"Invalid message authenticator in EAP request"
A search on CCO tells me that this is normally the result of a shared secret mismatch. I have however retyped the shared secret several times , and tested with simple strings such as "cisco" and the same result is received. Both the Radius definition on the AP and the NAS definition on ACS have bee re-created with no change in result.
As a test I ran up a clean install of ACS 4.1(1)23 in a VMware session. Configured a NAS object for the AP as I had previously done on the production system and it worked first go.
Would anyone have any clues on what could be wrong with my production ACS. ?
Many Thanks,
Leon

I have a question, when you placed the AAA client under a NDG, was there any Shared Key defined on the NDG level. Because it is an expected behavior, that if you define a Shared Key on the NDG level it over-rides key at the AAA Client level.
http://www.cisco.com/en/US/docs/net_mgmt/cisco_secure_access_control_server_for_windows/4.2/user/guide/NetCfg.html#wp342738
Refer to Step4.,
"Each device that is assigned to the Network Device Group will use the shared key that you enter here. The key that was assigned to the device when it was added to the system is ignored. If the key entry is null, the AAA client key is used."
Regards,
Prem
Please rate if it helps!

Systemd with wpa_supplicant 802.1X wired and dhcpcd - Need help

Hi,
At work we use 802.1X wired authentication on the network to get access. If successfully authenticated then I get 10.x.x.x network address from DHCP,
and if not successfully authenticated, I get a 172.x.x.x address from DHCP.
Now I've configured wpa_supplicant with certificates in its configuration file so that one is working fine.
What I have problems with is the startup, this is what I need in order:
* I need wpa_supplicant to start up
* wpa_supplicant needs to authenticate completely
* now dhcpcd may run and I should get 10.x.x.x address.
I've tried two (b*ttfugly) ways of solving this under systemd:
wpa_auth.service
[Unit]
Description=WPA 802.1X
Requires=sys-subsystem-net-devices-eth0.device
After=sys-subsystem-net-devices-eth0.device
[Service]
Type=simple
ExecStart=/usr/sbin//wpa_supplicant -ieth0 -Dwired -c/etc/wpa_supplicant/wpa_supplicant.conf
[Install]
Alias=multi-user.target.wants/wpa_auth.service
And in [email protected] I've added:
After=wpa_auth.service
However this won't work since wpa_supplicant isn't done authenticating when dhcpcd starts up.
I've also tried using -B option to wpa_supplicant and forking in wpa_auth.service like this:
Type=forking
ExecStart=/usr/sbin//wpa_supplicant -B -ieth0 -Dwired -c/etc/wpa_supplicant/wpa_supplicant.conf
Now if I'm lucky this works, but it's still a race condition.
So: Next things I've tried is to make the wpa_auth.service start up a script (Type=forking) that executes wpa_supplicant, and adds a sleep 1, this gives wpa_supplicant 1 second to authenticate, but its still a shitty and unsafe solution.
Last solution I tried was using the above solution but replaced sleep with wpa_cli -a script that according to man page executes the script when it recieves an event. So right now the chain looks like this:
In chronological order:
- wpa_auth.service (systemd)
Type=forking
- script
- wpa_supplicant
- wpa_cli -a script2 (will block until recieving an CONNECTED/DISCONNECTED event from wpa_supplicant, then run script2)
- script2
-pkill wpa_cli
- exit 0
done - dhcpcd may start
I just want to find a way to start dhcpcd after wpa_supplicant has authenticated so I get a correct IP address.
How do I do this in a correct way? Can I use dbus somehow to make wpa_supplicant signal that it is done authenticating?
Thanks
Last edited by dimman (2012-11-23 15:56:01)

From the sample wpa_supplicant.conf:
# scan_ssid:
# 0 = do not scan this SSID with specific Probe Request frames (default)
# 1 = scan with SSID-specific Probe Request frames (this can be used to
# find APs that do not accept broadcast SSID or use multiple SSIDs;
# this will add latency to scanning, so enable this only when needed)
So... looks like that likely isn't the solution. Of course, this is all just speculation now, until I can resolve the hardware issues or get a new laptop.

Transport change request to two clients at the same time

Hello all,
we have two clients in QAS system - 600 and 700, now the extended transport control has been setup, once we release a TR in DEV system, there will be two entries in QAS import queue, one for 600 and one for 700, I would like to know whether there is a way to import this TR into QAS (both 600 and 700 client) at the same time, that is to say, just one import action imports the TR into both 600 and 700.
Currently we have to import one by one, click the entry for 600, import it, and then click entry 700, import it.
Thank you.
Best regards,
Fresh

Hi,
If you want to transport each and every request which is released from Development into both the clients, better schedule transports in both the clients every 1hr/with some duration. Then system automatically imports the requests into target clients without any user intervention.
Delete all the transports which are "ready to be imported" from Quality queue before you scheule the job!
Regards,
Nick Loy

ISE v1.2 - Status-Server - 5405 RADIUS Request dropped

Just a note:
Some devices send regular RADIUS status messages;
The ISE drops these as
Event: 5405 RADIUS Request dropped
Failure Reason: 11031 RADIUS packet type is not a valid Request
Root cause: RADIUS packet type is not a valid Request.
Wireshark shows:-
Code: Status-Server (12)
Attribute Value Pairs:
AVP: l=6 t=Service-Type(6): Shell-User(6)
AVP: l=18 t=Message-Authenticator(80): df48bb4b50f0a772bd7c891ef6548c68
AVP: l=6 t=NAS-IP-Address(4): 10.1.1.1
I believe that ISE should accept and respond to these messages RFC5997 up2866.
A RADIUS server or proxy implementing this specification SHOULD respond to a Status-Server packet with an Access-Accept (authentication port) or Accounting-Response (accounting port). An Access-Challenge response is NOT RECOMMENDED. An Access-Reject response MAY be used.

Neno
Nothing to do with that,
The devices will use RADIUS to authenticate fine; databass, credentials, etc fine.
However they send keepalives to validate the RADIUS server is still there. ISE doesn't implement this and ISE logs get full of rejections. The end devices are unable to prioritise which ISE to used based on up/down. But still work.
This was just a note to everyone so they are aware of the issue,

Connecting to an 802.1X wired network

Does the AirPort support connecting to a 802.1X wired network?

Try turning odd autofill since that sometimes results in entering incorrect information.

802.1x wired EAP requestes dropped by clients

Similar Messages

Maybe you are looking for