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 tried that after I posted the original message. This does allow me to connect to the LEAP wireless network, but the machine never gets an IP address or any DNS servers assigned. I tried manually setting the IP, gateway and DNS to value appropriate for our network but I still can't get to any network services.
Well that is odd. If Internet Connect is able to connect to the network, it means that the LEAP handshake completed and you should be authenticated. Do you see the connection timer start counting after click connect?
Yes, the connection timer starts but I have a self-assigned IP. The behavior does get a little stranger - the signal strength will occasionally suddenly drop (4 "bars" to 1), and the laptop will re-authenticate. It will succeed most of the time, but occasionally not.
Tomorrow I plan to try connecting to another wireless router in a different part of the building to see if I end up with a different result. I'm starting to suspect that my local router is the problem; it turned out that the coworker who said he could connect was actually in another part of the building at the time.
I tested with a different router this morning and could not connect, but was able to access it with a Powerbook. It appears that there is a software bug of some sort that prevents the DHCP information from being transferred to the MBP.
I'm in the same boat. My old 15" PB would talk to our Cisco wireless w/ LEAP no problem. I get the same error as the original post when I try with the MacBook.
Exactly the same problem. My powerbook works. My MacBook Pro doesn't.
Spent time with our IT department and Apple product specialists today. They're sending the details to the engineering folks.
I'm pretty sure there is a SW problem with the Airport driver in the intel version.
They're going to call me when they have a response from engineering.
I'm expecting a patch. I just hope it is soon.....
MacBook Pro, Power Mac Quad, Powerbook 17", Mac mini, 12 Powermac Mac OS X (10.4.5) Yes I'm an apple junky
Not sure if this is related, but I have a similar problem connecting via PEAP to my companies wireless network. The same exact setting on my buddies old powerbook connect just fine, but the macbook pro does not seem to connect and get an IP via dhcp.
I hooked up a packet sniffer to see what was happeneing and I see more then a couple "malformed packets", this also does not happen on buddies g4 powerbok w/ the same configuration.
Here is a dump from the sniffer:
No. Time Source Destination Protocol Info
9 5.825325 Cisco_00:31:f0 00:14:51:ed:43:79 EAP Request, Identity [RFC3748]
Frame 9 (68 bytes on wire, 68 bytes captured)
Ethernet II, Src: 00:13:60:00:31:f0, Dst: 00:14:51:ed:43:79
802.1x Authentication
No. Time Source Destination Protocol Info
10 5.827077 00:14:51:ed:43:79 Cisco_00:31:f0 EAP Response, Identity [RFC3748]
Frame 10 (48 bytes on wire, 48 bytes captured)
Ethernet II, Src: 00:14:51:ed:43:79, Dst: 00:13:60:00:31:f0
802.1x Authentication
No. Time Source Destination Protocol Info
11 5.833015 Cisco_00:31:f0 00:14:51:ed:43:79 EAP Request, EAP-Cisco Wireless (LEAP) [Norman]
Frame 11 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: 00:13:60:00:31:f0, Dst: 00:14:51:ed:43:79
802.1x Authentication
No. Time Source Destination Protocol Info
12 5.834553 00:14:51:ed:43:79 Cisco_00:31:f0 EAP Response, Nak (Response only) [RFC3748]
Frame 12 (24 bytes on wire, 24 bytes captured)
Ethernet II, Src: 00:14:51:ed:43:79, Dst: 00:13:60:00:31:f0
802.1x Authentication
No. Time Source Destination Protocol Info
13 5.839589 Cisco_00:31:f0 00:14:51:ed:43:79 EAP Request, PEAP [Palekar]
Frame 13 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: 00:13:60:00:31:f0, Dst: 00:14:51:ed:43:79
802.1x Authentication
No. Time Source Destination Protocol Info
14 5.849683 00:14:51:ed:43:79 Cisco_00:31:f0 TLS Client Hello
Frame 14 (120 bytes on wire, 120 bytes captured)
Ethernet II, Src: 00:14:51:ed:43:79, Dst: 00:13:60:00:31:f0
802.1x Authentication
No. Time Source Destination Protocol Info
15 5.860320 Cisco_00:31:f0 00:14:51:ed:43:79 TLS Server Hello, Certificate[Malformed Packet]
Frame 15 (1030 bytes on wire, 1030 bytes captured)
Ethernet II, Src: 00:13:60:00:31:f0, Dst: 00:14:51:ed:43:79
802.1x Authentication
[Malformed Packet: SSL]
No. Time Source Destination Protocol Info
16 5.860828 00:14:51:ed:43:79 Cisco_00:31:f0 EAP Response, PEAP [Palekar]
Frame 16 (24 bytes on wire, 24 bytes captured)
Ethernet II, Src: 00:14:51:ed:43:79, Dst: 00:13:60:00:31:f0
802.1x Authentication
No. Time Source Destination Protocol Info
17 5.869295 Cisco_00:31:f0 00:14:51:ed:43:79 TLS Server Hello, Certificate[Malformed Packet]
Frame 17 (1026 bytes on wire, 1026 bytes captured)
Ethernet II, Src: 00:13:60:00:31:f0, Dst: 00:14:51:ed:43:79
802.1x Authentication
[Malformed Packet: SSL]
No. Time Source Destination Protocol Info
18 5.869779 00:14:51:ed:43:79 Cisco_00:31:f0 EAP Response, PEAP [Palekar]
Frame 18 (24 bytes on wire, 24 bytes captured)
Ethernet II, Src: 00:14:51:ed:43:79, Dst: 00:13:60:00:31:f0
802.1x Authentication
No. Time Source Destination Protocol Info
19 5.878652 Cisco_00:31:f0 00:14:51:ed:43:79 TLS Server Hello, Certificate[Malformed Packet]
Frame 19 (707 bytes on wire, 707 bytes captured)
Ethernet II, Src: 00:13:60:00:31:f0, Dst: 00:14:51:ed:43:79
802.1x Authentication
[Malformed Packet: SSL]
No. Time Source Destination Protocol Info
20 5.882101 00:14:51:ed:43:79 Cisco_00:31:f0 TLS Client Key Exchange, Change Cipher Spec, Encrypted Handshake Message
Frame 20 (214 bytes on wire, 214 bytes captured)
Ethernet II, Src: 00:14:51:ed:43:79, Dst: 00:13:60:00:31:f0
802.1x Authentication
No. Time Source Destination Protocol Info
21 5.895575 Cisco_00:31:f0 00:14:51:ed:43:79 TLS Change Cipher Spec, Encrypted Handshake Message
Frame 21 (75 bytes on wire, 75 bytes captured)
Ethernet II, Src: 00:13:60:00:31:f0, Dst: 00:14:51:ed:43:79
802.1x Authentication
No. Time Source Destination Protocol Info
22 5.949310 00:14:51:ed:43:79 Cisco_00:31:f0 EAP Response, PEAP [Palekar]
Frame 22 (24 bytes on wire, 24 bytes captured)
Ethernet II, Src: 00:14:51:ed:43:79, Dst: 00:13:60:00:31:f0
802.1x Authentication
No. Time Source Destination Protocol Info
23 5.955622 Cisco_00:31:f0 00:14:51:ed:43:79 TLS Application Data
Frame 23 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: 00:13:60:00:31:f0, Dst: 00:14:51:ed:43:79
802.1x Authentication
No. Time Source Destination Protocol Info
24 5.956229 00:14:51:ed:43:79 Cisco_00:31:f0 TLS Application Data
Frame 24 (67 bytes on wire, 67 bytes captured)
Ethernet II, Src: 00:14:51:ed:43:79, Dst: 00:13:60:00:31:f0
802.1x Authentication
No. Time Source Destination Protocol Info
25 5.961656 Cisco_00:31:f0 00:14:51:ed:43:79 TLS Application Data
Frame 25 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: 00:13:60:00:31:f0, Dst: 00:14:51:ed:43:79
802.1x Authentication
No. Time Source Destination Protocol Info
38 11.393590 00:14:51:ed:43:79 Cisco_00:31:f0 TLS Application Data
Frame 38 (66 bytes on wire, 66 bytes captured)
Ethernet II, Src: 00:14:51:ed:43:79, Dst: 00:13:60:00:31:f0
802.1x Authentication
No. Time Source Destination Protocol Info
39 11.557358 Cisco_00:31:f0 00:14:51:ed:43:79 TLS Application Data
Frame 39 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: 00:13:60:00:31:f0, Dst: 00:14:51:ed:43:79
802.1x Authentication
No. Time Source Destination Protocol Info
40 11.557919 00:14:51:ed:43:79 Cisco_00:31:f0 EAP Response, PEAP [Palekar]
Frame 40 (24 bytes on wire, 24 bytes captured)
Ethernet II, Src: 00:14:51:ed:43:79, Dst: 00:13:60:00:31:f0
802.1x Authentication
No. Time Source Destination Protocol Info
41 11.578881 Cisco_00:31:f0 00:14:51:ed:43:79 EAP Success
Frame 41 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: 00:13:60:00:31:f0, Dst: 00:14:51:ed:43:79
802.1x Authentication
No. Time Source Destination Protocol Info
42 11.579218 Cisco_00:31:f0 00:14:51:ed:43:79 EAPOL Key
Frame 42 (75 bytes on wire, 75 bytes captured)
Ethernet II, Src: 00:13:60:00:31:f0, Dst: 00:14:51:ed:43:79
802.1x Authentication
No. Time Source Destination Protocol Info
43 11.579549 Cisco_00:31:f0 00:14:51:ed:43:79 EAPOL Key[Malformed Packet]
Frame 43 (62 bytes on wire, 62 bytes captured)
Ethernet II, Src: 00:13:60:00:31:f0, Dst: 00:14:51:ed:43:79
802.1x Authentication
[Malformed Packet: EAPOL]
Can you guys who are having trouble check with your network administrators to see if they are requiring the old style Cisco leap authentication value in the association request (0x0080)? If so, it might worth asking them to turn on open authentication with LEAP, and then check if that allows you to get on through Internet Connect.
Exactly the same problem. My powerbook works. My
MacBook Pro doesn't.
Spent time with our IT department and Apple product
specialists today. They're sending the details to the
engineering folks.
I'm pretty sure there is a SW problem with the
Airport driver in the intel version.
They're going to call me when they have a response
from engineering.
I'm expecting a patch. I just hope it is
soon.....
I have
exactly the same problem. Two machines (Macbook Pro, iBook G4) both running 10.4.5 and configured identically will respond differently.
The iBook connects fine.
The MacBook Pro "sees" the wireless, authenticates via LEAP (and starts the timer running) but is unable to get an IP address.
Setting an IP address manually doesn't fix the problem, as I get 'no route to host' messages.
Between this problem and the screeching/whining I'm really starting to regret getting rid of my PBG4. But, I'm willing to try working through it. I'd be glad to work with Nicholas or someone at Apple to provide more detailed debugging info.
When I ran tcpdump and then tried logging on using the Airport menu item, there was no response at all. Here's the tcpdump output for the case where I connected through Internet Connect using the 802.1x pane:
Ok this issue is killing me. I opnened a trouble ticket with apple about PEAP wireless networking not working (and filed a complaint I believe). Lets see what this gets us.
Its pretty clear to me that this works w/ the old G4 powerbooks and does not work w/ the macbook.