PEAP wireless @work ...

There are more than just 1 or two people with them at WVU.. I have opened a case with apple about it, but they (probably Level 1 support) said that nothing was wrong and could not see any config problems. I have even assigned my MBP a static IP and it still does not work with that either, so it is definatly something in the OSX code for Intel that is stopping it from working. I have contacted our Apple Rep about it and he is going to try to see if there is anything he can do.

Yeah, I went to the TSC (technical Support Center) here. I had to show them how to do even the most basic stuff...and they call them selfs technicians...Anyhow, they also tried entering a manual address that they knew should work so I agree it is definately something more deep than just not getting a correct IP address.

Well that should narrow it down for Apple. Obviously not the Airports firmware rather the intel version of MacOS X thats causing this problem. Should also mean that the intel iMac shouln't be able to connect via PEAP either.

I can't connect to the PEAP at my school which makes researching in the law library and taking "laptop finals" impossible on my Mac - very frustrating.

Well - it seems that some other university's are also on top of this problem. Found the following form the Univ. of Iowa. Contains a pretty good description of the problem.

https://helpdesk.its.uiowa.edu/wireless/intelmacwep.htm

How did you install window XP on the 2nd partition?
Can you send me instructions?
Many thanks,
Nick

Nicholas,

As in my earlier post, go here:

http://onmac.net

for instructions on how to install XP on your MBP - click on the "download here" link and get the Winxponmac_0.1.zip file. Extract this and it contains detailed instructions.

I've been spending much too much time tweaking with my brand new macbookpro and reading many webpages in hopes of connecting to my schools wireless. It seems nothing will change until apple releases a new software update that is supposed to solve this problem. anyone have any ideas when this should be.

I'm trying my best to be patient but since i got my powerbook stolen in january waiting is all i seem to be doing.

I hear ya man. What I'm really waiting for is Leopard which should be better customized for MBPs (even though I'm sure they spent quite a bit of work on it, I think the MBP version of Tiger was not really customized for the MBP as it was made to be "compatible" with the MBP).

But I digress, here's what I am doing until Apple updates. My school has a secure connection that they tell everyone but then also an unsecure connection that they don't broadcast the SSID of, but they require MAC registration for. They use this mainly for guests, palms and other devices that need to connect but don't have TLS capability. I'm sure your school has to have something like this and they should broadcast it everywhere they broadcast the secure one. But since it is unsecure be sure you turn of filesharing, only access https sites, etc.

It may seem like Apple's doing nothing and they don't think the problem is big enough but they are working with several major schools and professionals from what I have read. I imagine an update no later than a month from now. Whenever I get frustrated at Apple and I'm in class I open up Photo Booth and make funny faces or use the Apps like Quicksilver to show off. Eventually someone goes "wow how did you do that" or something and I get to show off more and I become happy again. Maybe this trick will work for you.

Just wanted to add that I am experiencing the same issue.

I am trying to connect my Macbook Pro to my university's wireless network, and it fails to get a proper connection to the network, after successfully authenticating. After consulting with campus technicians, it turns out that this problem occurs with other Macbook Pro's, and they do not have a solution.

This occurs with both PEAP and LEAP authentication. My Macbook Pro works fine on all other types of wireless networks (i.e. standard WEP).

I am in touch with Apple support, and have pointed them to this thread. The person I spoke to seemed to take the matter seriously. However none of the representatives I spoke to were initially aware of this issue; hopefully this does not imply that the issue is not a high priority at Apple.

Please, if you are experiencing this problem, call Apple support and clearly describe the problem. Point them to this discussion. Ask if there are any workarounds. Ask when a fix is expected. If they are not aware of the extent of the problem, they will not escalate the issue and it might not be fixed for a long time.

Let's hope Apple rolls out a fix soon, because until they do, my Macbook is essentially useless to me.

Macbook Pro Mac OS X (10.4.5)

Macbook Pro Mac OS X (10.4.5)

I brought my MacBook Pro into the I.T. guys at the University of Victoria today. The technician said that he has seen this on no less than three Intel Macs before: two iMacs and a MacBook Pro.

According to him, he managed to get the MacBook Pro working after doing some voodoo magic, but it was not reproducible on the iMacs. He said he'd try to do it on my machine, but I didn't want to leave it overnight. He also added that they've informed Apple about the issue.

So, it seems that it's a problem with Mac OS X for x86, instead of the MacBook Pro specifically.

I've been having this problem as well (same circumstances as everybody else above, PEAP shows connected but I receive no IP).

I reported this to Apple just over a month ago, now, and like the rest of you, I've still heard nothing back, and I have to admit I'm getting pretty frustrated with the whole ordeal. It's understandable that a major new release will have glitches, and that I'll pay an early adopter cost in various inconveniences. But when I first called, they repeatedly and strenuously tried to tell me it's not their problem, that they don't support PEAP because "we can't possibly support every single feature in the operating system" (which I could accept if they were referring to some artifact of the unix underpinnings, but when it's someething that they went out of their way to give me a native OS X interface for, they are implicitly supporting it.

I can accept that their are bugs. I can accept that their support can't help me yet. But I can't help but feel robbed when they give cop out answers and tell me it's my own fault for wanting to use this type of network, rather than simply acknowledge "we're working on it" (or maybe "we will work on that").

Bah.

[end rant.]

Hey man. I have the same story and I completely agree. I called about a month ago and got the run around. They said something about how my campus's network is not updated yet...blah, blah, blah. So, I went to the tech people at my school and they told me there was no way it could be a network problem, and they couldn't very well change the way the entire campus authenticates just to accomadate the new macs. I committed to calling apple every day until I got a better response. After talking to product specialists and being told that this wasn't their problem, i finally talked to someone who had heard about this and said it had been escalated to engineering (which, from my experience with apple so far, may be another cop out answer). Bottom line....I'm a new apple user and I am completely dissatisfied with the way they have handled this.

Is apple support usually better than this, or is this par for the course?

macbook pro Mac OS X (10.4.5)

Anyway that you or the IT guys could share their voodoo magic? Like everyone else here, I'm looking for anything that will help.

Overall, I'm actually not dissatisfied with Apple's support at all. They've been great to me in the past. I've gotten the short end of the stick so far on this one, but I can honestly say I'd expect that from any company in such a situation.

Any support type role requires giving the impression of being a "genius" that can help solve all your problems, even though the first guys you might get to talk to are mostly just going to be able to help you with common software configuration and usage problems. Even if the first guy escalates you to his "product specialist", and even if that guy escalates you to his engineers (won't happen often or easily), they'll do their best to solve your problem, but if they can't, it's a rare case (in my experience) that they'll accept the blame for it. That's regardless of what company you're dealing with, in my experience.

I don't expect any company to accept blame for something easily or lightly, especially not any of the employees you might be able to get on the phone, because they're certainly not authorized to decide what Apple acknowledges as a bug worth devoting man hours to fixing.

But that doesn't make it any less frustrating to us experiencing the problem.