802.1x Authentication has failed. Error: 1 on port en1

I have gone over and over many other posts on this today all to no avail as most discussions are specific to particular networks. Usually US universities.

Anyway..

I have multiple MacBook Pro's on site and have been using RADIUS authentication for some time by manually installing a certificate in the system root for the local DC, and then creating an 802.1x login window profile. Recently however a couple have stopped working.

I have 2x MacBook Pros. 1 a 15" on 10.5, another a 13" on 10.6. Both have BCM43xx AirPort cards. They were originally OK until after a Mac Update, which made us believe it was the firmware version of the airport which had caused the fault.

I have however rebuilt the 10.6 client to 10.6.0 and upgraded 1 patch at a time to 10.6.4 until it reached the identical airport utility and bcm43xx firmware version as the working clients, however still to no avail. When trying to connect to teh Wireless network, i am prompted for credentials which i enter (work on another client) and it instantly rejects them, without even thinking about it. VERY LITTLE is shown in the system.log, other than the en1 starting, then stopping within a second.

I've wasted 2x days on this now and would really appreciate some assistance if anyone has any ideas. Otherwise it looks like I may be having to create a whole new SSID with WPA2 keys, rather than RADIUS and I would prefer not to do that.

Thanks in advance,

MacBook Pro, Mac OS X (10.6), + each patch upto 10.6.5

Posted on Nov 12, 2010 9:03 AM

Reply
3 replies

Nov 12, 2010 9:28 AM in response to bezzoh

well I just found a fault with 10.6.5 update. There I could not connect on my usual channel for the 802.11g. I used to run it on channel 3, but that was crippled with 10.6.5.

Well your not using that system update so that's probably not it. But try some different channel especially if you'r running it on non default channel, that is other than channel 6.

Nov 17, 2010 1:21 AM in response to bezzoh

Thanks for the suggestion and if I get no further I may look at doing this during the school holidays, however such changes to a live service has far too many implications especially if it were to cause any type of potential outage.

While doing a bit of further testing today however, I had 2x MacBooks, one known good and one that wont work, and tried to connect both using the exact same AD username and password. The resulting IAS logs on the Domain Controller showed that the working one was authenticated using PEAP (as per my remote access policy) but the one that fails is only trying to use EAP, despite being configured in exactly the same way, hence apparently being rejected when trying to connect.

Other than firmware versions, could anyone perhaps suggest why a MacBook would choose to use EAP rather than PEAP despite the 802.1x profile setup in the network preferences specifically using PEAP only?!

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

802.1x Authentication has failed. Error: 1 on port en1

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.