Has anyone successfully setup an 802.1x configuration for PEAP on their MacBook Pro? I have a PEAP config that works for my PowerBook, but the EXACT SAME configuration is not working for the MacBook Pro. It looks as if everything is fine (no authentication errors or anything), but no dhcp IP address is ever assigned to the wireless (en1); instead it has a 169.x.x.x address??
Any ideas?
PowerBook G4/Sager 5600/Custom Intel Machines/NEW MACBOOK PRO 2.16/7200rpm/2gb,
Mac OS X (10.4.5)
Working on this roblem right now, I deleted all the configurations and then deleted all the keychain files related to wireless. server certificates Usually that will fix PEAP connectivity problems. but I am still struggling with this one. Hope someone jumps IN on this that can help.
I am having exactly the same issue. PEAP does not work. I can authenticate and connect to the Radius server. Unfortunately, the MacBook Pro never sends a DHCP request.
In the LEAP topic someone mentioned that interface robustness fixed their PEAP problem but it doesn't seem to help me.
Please post any ideas or fixes if you come across them.
Yes, I am currently having the same problem. It fully connects, and the certificates are accepted, but I never get a real world IP address. I'v tried many things and nothing works. It looks to me like a problem with the OS on intel. Does this problem also occur on the intel iMacs?
I have the exact same problem. My (now sold) powerbook g4 worked fine with peap at my office. Now, I am able to show connected, and the timer is incrementing, but "ifconfig en1" shows no ip address.
This issue coupled with the 802.1q voip phone problem on the ethernet port makes like very difficult with my new MBP. $3000 is a lot of money to pay for a notebook that cannot connect to the internet at work.
I am having the same problem as well. I've spent several hours today with apple and with my network administrator and we still haven't resolved anything. Apple is saying that it is a problem with the network and using PEAP for authentication. He suggested getting the network admin. to change to another form of authentication. However, my conversation with my network administrator didnt go very well either. This was the first macbook pro he had seen and he had no idea what to do with it.
If you have this problem, please post to get this on the radar at apple.
Same problem here. Using MacBook trying to associate to Cisco AP infrastructure using 802.1X (PEAP) or LEAP. On my end, I don't see the client authenticate to my Cisco ACS radius server. Nor do I see the client attached to the AP. But the client thinks it is associated. The client shows a 169.x.x.x ip and of course, cannot communicate on the WLAN.
Same problem here. Works on a G4 powerbook running 10.4.5, but the MacBook Pro running the same MacOS version with the exact same settings does not work. Any idea when apple will fix this?
You guys who are having problems, what kind of access points and radius servers are you using? I was able to connect my MBP to an AirPort Express using Elektron as its radius server with PEAP without any problem. Also, it might be helpful to see output from the following command in terminal, "sudo tcpdump -i en1", during and shortly after you successfully authenticate but can't get an IP address.
Running Microsoft IAS Server 2003 SP1 with Cisco AireSpace AP's if that helps. No Windows Machines or older MacOSX machines are having troubles but I can not get any of these MacBook's on the wireless.
Yay! Someone from Apple shot me an email asking me if I was interested in helping the AirPort engineers out by running some debug apps and some terminal commands for them! They are aware of this thread and are interested in getting to the bottom of it!
Hi, I'm new to the laptop world so I'm preety green when it comes to wireless networking. I tried to connect to the network here at campus and I get the exactly same results as you guys. (connected but 169.* ip)
My windows loving brethren have their laptop's set up to use PEAP with (MS-CHAP-V2) authentication protocol.
On my machine it says it is connected with PEAP (GTC). The widows machine won't connect if they are set to GTC, and I haven't found a way to select (MS-CHAP-V2) on the mac.
My question is,
Am I having the same problem as you guys or am I missing some trick to force MS-CHAP-V2 ?