Anyone able to connect to a LEAP network? When I try to connect, I get a dialog box that says "There was an error joining the AirPort network <Name>".
My MacBook Pro had no problem connecting to my WPA2 network at home. The network appears to be fine, as a coworker was able to connect with his Powerbook.
I've got the same problem, but applecare said there was nothing they could do about it and closed the ticket. I think we're just in a wait for Apple to issue a software update. Assuming of course, that the feedback from this forum and AppleCare actually reaches someone with the authority and desire to put it on the developers' timetables.
I got a response from Apple indicating that this is a known issue, being investigated by engineering. Thanks to the folks above who reported it directly to Apple previously.
I am having the same issue. I had a powerbook G4. My company uses peap with mschap. I created an 802.x configuration with internet connect, and I get connected with a timer, but I never get an ip address, just the 169.x.x.x autoconfiguration address. This is a PITA since my company also uses Cisco SIP phones and there is a bug with the ethernet card and 802.1q vlan frames. So basically I am up the creek without a paddle. I have NO WAY to connect to the internet at work, which of course makes my Macbook useless. I hope a patch is coming VERY soon.
Same Issue for me. Powerbook worked on corp LEAP network. MacBook does not. Tried OS security update from last night (Mar 1), but still getting: "there was an error joining the airport network..." My Apple Care rep claimed that they don't support LEAP (even tho its still in the drop down), so I'm glad to hear that they have acknowleged the problem and are working on it from previous post-ers. MacWorld Review notes also mentions LEAP problems...
http://www.macworld.com/weblogs/editors/2006/02/macbooknotes/index.php
Has ANYONE successfully connected to a LEAP network, or does LEAP not work for everyone?
I can connect via LEAP and PEAP to my network at school (which uses Cisco equipment if I'm not mistaken) although it only stays connected for a few minutes. After that it goes into "authenticating" again and I have to disconnect and reconnect to get access back.
I have had access to an intel Imac (os x 10.4.4) and had the same problem with Leap authentication to the campus network. But after I installed the 10.4.5 update Leap has been working great. I did try to use the installer that came with the Imac to install a fresh copy of os x 10.4.4 on a MBP but it wouldn't let me.
Has anybody tried a force install of the 10.4.5 intel update?
20" iMac G5 & intel, 17" PB & 15" MBP, Mac OS X (10.4.5)
Well, I tried both the 10.4.5 update from software update and turning on interference robustness. While that may fix PEAP problems, my LEAP connection still exhibits the same behavior:
it connects, authenticates, and starts the timer but does not get a DHCP lease. Manual IP results in no route to host messages.
very much lik our system try deleting the keychain files related to your configuration and server certificates, It works deleting or equifax and romulus files. I delete the configurations in internet connect first then the server certificates in the Keychain.
I am trying to do some remote support for this issue right now and cannot get connected though.
deleting the certificates has worked for me now until today.
So good news and bad news on this front. Like others, we have several Powerbook G4 laptops running flawlessly with our Cisco LEAP enabled wireless network. I was the first to buy a Macbook Pro this week and get it set up. We are running Cisco Secure ACS version 3.3.2 against an Active Directory DB for user authentication. To keep this simple, the Macbook does not authenticate at all. In fact, there is no error log in the "failed attempt" log on the ACS server that even shows the Macbook tried to authenticate.
The good news??? I was able to escalate this issue within Apple support to some degree. At first they tried to blow me off. Then we discussed the differences between LEAP and WEP and why Apple should support LEAP since OSX natively supports it. Long story short, it is being escalated to engineering and is a known issue.
I was told to check back for an update, which is fine, but I am wlan-less until this is fixed. Looks like I'll be lugging around a temp dell laptop until this is resolved.
I wish they understood how much pain this is causing their Mac evangelists. This is the widest exposure that I have had since trying to convince our Dell house to let me use a Mac. Even so, I had to buy the Mac myself and support it myself. Now there are 3 of us and we're all "sunk" with this issue, with IT grinning broadly as they say, 'you wouldn't have this bother if you stuck to our recommended DELL".
2 weeks with this problem.... If Apple wants its evangelists to change the corporate culture and allow Apple's in to the mainstream, they have to do better than this. And while I'm on this topic, they need to make Safari work with many of the web based corporate reporting and information systems like TESITE, ExpenseSITE, Sharepoint etc.....
Enough of my rant - I love my MacBook Pro. I just wish I could get my work done with it too!!!
Nick
Where do you go to file a trouble ticket? I'm in the same situation, now, and I'd certainly like to be notified when I can get my shiny new MacBook working at work. After all, I bought it so I could work on it. Until I can use the network, it's a really nifty and expensive doorstop.