New MacBook Pro & Leopard - Airport Connection problems

problems is back but this time its not apples fault i have determined that the every one and there dog has ther router on around my apartment every thing ran fine for 3 hrs i was at my dads HOUSE with out a glich since i havent had a conection to my own all day not even under vista it stayed conected but ran real slow like dial up slow think im gonna buy an airport extreme so u can go 5ghz away from the 30 connections that show up in the menu that are at 2.4 ghz plus the hd conection is good to

you got it.

Get rid of the third party crap.

Is it worth saving some bucks and wasting your time troubleshooting that crap?

I don't think so. I've been suggesting that so many times but people don't listen.

I know airport routers have no "connection" problems. I deal with so many in so many different places, I should know.

Hi Zebra1,

"Get rid of the third party crap."

Well, Apple stuff isn't as good as promised either...
I have an AirPort Extrem Base Station, and with my MacBookPro Core2Duo 2.33 GHz tons of problems! Once in a while the MBP likes to connect to the base station, more often not. I tried all different kind of stuff, got the situation improved by reducing the WPA key timeout setting in the AEBS prefs, but the problem still persists. Every once in a while the MBP just doesn't connect to the AEBS. In my company I have a "cheap" router with which I never experienced any problems at all.

Second bad thing about my AEBS: If I upgrade the firmware to the latest revision it doesn't connect to the internet at all, I have to downgrade to a previous version to have internet working...

It's not all gold that shines 🙂

Chris

You have a local problem. That is not unusual.

You should look into solving it since there aren't "tons of problems" with either of the two pieces of hardware you have. Since the MBP works at work, I'd start with the Extreme. Wipe it clean and reinstall the firmware updates, change the protocols/frequencies, etc. I have seen environmental situations like these that were solved by going to "n" at 5GHz. Here is a link to something that resolved after much effort and the problem was totally environmental, although I do not have a clue what it was to this day, but I fixed it:

http://discussions.apple.com/message.jspa?messageID=6553680#6553680

I just couldn't blame the equipment because once you took it out of there it worked flawlessly. I was using the same MBP as yours at the time, btw. Another time, microsurges at the electrical outlet where the Airport and the cable modem were connected created internet and network havoc. It was discovered accidentally as I noticed that the problem, one time, surfaced when someone fired up a vacuum cleaner and my connection went west. Sometimes you have to think outside the box.

Food for thought.

I've tried all types of soft&hard resets, both on the AEBS & the MBP. Curious enough there's no problem at all with my other macs (iBook G3, PowerBook G4 17", DualG5 1.8) connecting to the AEBS. I think the problems is linked to the MBP using 802.11b/g mode (backward compatibility mode to the iBook). The AEBS is the "older" one not having the "n" mode, I already ordert the TimeCapsule which should fix my problem (hopefully).
Tkx. for all the suggestions 😉

I just switched my network to full "n" last week from B/G, and the 2.33Ghz I had for a year till last December worked fine with it. Is this the older AEBS or the new one? Have you tried booting from a different drive to rule out software problems on the MBP?

It's still the older one without "n" - booting from a different drive could be an option, I would need to copy OS first. I'll try this

If you copy OS it will make no difference. You need to do a fresh install on an external drive and try it out.

Tkx. for the tip, I wouldn't have thought of this... Ok, I'll need to find an external HDD still empty, mine are full with data...
I'll check this out most likely in a few days

looks like the connection problems are still occurring for me 😟 i've done a fresh install and everything so idk what to do anymore. maybe they didn't fix the problem with the router i'm using? i'm using a 2wire gateway. i also have the ability to use a wrt54gs so if anyone has had experience with this router lemme know if it works and i'll switch back to it.

if u have linksys try setting your router to wide mode under wireless after 10.5.2 update it fixed my conection issue for 3 days untill every one turned there router on at the same problem i st my router to wide mode macbook has worked 2 weeks no problem of course my wireless g pc gets 1-18 mbps with fair signal but who cares about windows other than my wife ha ha ha revenge for the trash and dishes every night!!!!!!!

There is a serious problem that appears to be related to MBP/AP and you can find a posting on this board http://discussions.apple.com/thread.jspa?threadID=1352518&tstart=105
And over on the Airport board. The airport on the MBP is going on and off and making internet connections very difficult. It appears as if the problem came with 10.5.2 update. Others have reported that AppleCare says that Apple is aware of the problem and that the "Apple Engineers" are working on it. Lets hope that a fix comes soon.

Hello,

I have the same problem, once I update my Mac, I cannot access my Westell Model: A90-327W15 it was working before until I update my Mac. I tried everything from no security, MAC Address filter, WEP, and WPA didn't work. Then I figure it might be the firmware, I am a Verizon customer and I am using their: Westell Model: A90-327W15

So I download the new Firmware (Windows XP & Ethernet Cable required) from here: ( you wont find this on Westell, they said to call Verizon)

http://download.verizon.net/webdownload/firmware/upgrades/westell/A90-327W15VER_030

Once I did the FIRMWARE update, then restart and I get connection right away. So the problem is not MAC (well, kinda) but the Access Point.

I didn't have the solution for other Accesspoint but I am sure the same thing will work.

Good luck,

FarJang

Actually, both at home (with Westell 6100>APEBSg) and at the office (with NetGEAR>?>T1), I run under static IP addresses. But, today, I did some more testing. I run VM Ware and Windows Vista and my assumption had been, since Vista, running under VM Ware, utilizes all of the Mac I/O ports, that Vista would share the same slowness with the Mac Airport Wi-Fi. I tried it today and, much to my surprise, the connection speed was great (like normal). I also tried a hardwire to the Ethernet port on the APEBSg and got the same great connection speed.

So, MBP Airport works with Vista but not with Mac OS and by-passing the Airport Wi-Fi with a hardwire works with both Vista and Mac OS. It's only the Mac OS trying to go through the onboard Airport that gets choked down to unacceptable connection speeds.

This worked for me thus far! Thanks for the help.