- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi all,
I've been struggling with a problem trying to implement NAC/802.1x with Dell Optiplex 990s running 82579LM NICs with the latest drivers (and drivers from 2010 also did not work).
Basically what we're seeing is, intermittently when a machine boots up from being completely shut down, EAP information is not exchanged (never sent from the client to the switch) and it just hangs. We've had this problem using a Windows 7 native supplicant, as well as the Cisco AnyConnect supplicant. Upon debugging, Cisco's determination was that they were not seeing a "link up" event from the driver in the incidents where a failure occurred. We can get the machine to authenticate by either restarting the Wired Autoconfig service (Windows 7) or bouncing the port (Cisco supplicant).
Has anyone run into similar?
FYI - Our switches are Catalyst 2960s running 15.0(2)SE code, but we also had this issue in a 12.2 train we ran.
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I do not know anything that would be specific to the 802.1x problem, but maybe the cause is in the initial link up timing for the Ethernet.
There have been BIOS updates to some boards with 82579 network connections that might affect connectivity. Updating the BIOS might help.
If the computer has a management engine that uses the network connection for access, that might affect the initial connectivity. Make sure the management engine version and any associated drivers are the latest that Dell has for your computers.
If neither of the above ideas help, you could experiment with feature configurations that might affect the Ethernet link negotiation. For example, you could try disabling Energy Efficient Ethernet on the 82579 or try disabling PoE on the switch port. Either of these could affect the link negotiation.
I am curioius to hear back about anything that seems to fix the problem or make it happen less.
Mark H
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks, Mark.
We'll try these. I did peek through the BIOS fixes/updates and didn't see anything specific for this issue, but it's definitely worth a shot at this point.
EEE is also a good thought... and we do have PoE switches, so these two things are something we should be able to do relatively easy/quickly. Sometimes it takes a day or two for our machines to fail, but I'll keep you posted on our progress.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Just stumbled across this. We are rolling out 8021x TLS. Went nuts trying to figure it out, updated drivers, reimaged a machine, same problem. Put in a USB NIC, works perfect. Anyone ever figure this out ? When you say Bios, you mean machine Bios ? NIC Bios ?
Thanks,
Justin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi jickfoo,
I haven't worked with these devices in years, but I can answer your question about the BIOS. I was referring to the system BIOS. These devices are built in and the BIOS of the system can affect connectivity. I don't know anything specific about the 802.1x issue.
Not sure if ryantfsl is still around or if anyone else has experience with this issue and can chime in. Maybe one of the network people who monitor the forum will have an idea.
Mark
![](/skins/images/D2683F18326913BBA0436CB7114DD569/responsive_peak/images/icon_anonymous_message.png)
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page