![]() |
Just purchased a Macbook (24 Feb 2007) and had the same problems as everyone else, tried ALL the solutions (thanks to all the posters - this sort of forum is invaluable to non-techs like me), to no avail. Was just about to go out and purchase a new router...
But, hooked up via cable and downloaded a software update from apple that included an airport update. Now connected wirelessly !:) |
MacBook: no wireless connection after airport update 002/2007
Hey folks,
I decided to join this thread as I experience the same issue as many of you: I get the message: "There was an error joining the Airport Network ..." when trying to connect to a wireles base station. The network I used to connect to is open/non-password-protected. Yesterday I installed the new Airport Extreme update 002/2007. After about 1 hour the connection to the router suddenly broke I could not reconnect yet. There are 2 other Laptops connecting to that network in our house and they have no problem. So it really seems to be a problem of my MacBook. I already tried some of the proposed solutions: 1. deleted all keychain entries 2. turned off and on airport/ rebooted 3. deleted the list of preferred networks from network prefs I am now trying to get rid of the updates by installing a fresh OS. Strangly when I bought the Mac I could not connect for about 3 days with a fresh system, but after it suddenly worked and never caused problems. Is there anyone who understands what is going on with the Airport and what other solutions there might be? Cheers and thanks in advance Christian |
I've come to one solution (maybe it will work for you)
Well... just like all of you I've had those 2WIRE connection problems with my new MacBook Black. Sometimes (especially when I have a blackout at my house) I lose all wireless connectivity, however what I do in order to regain access is:
1) Type: home (on any browser, this will take you to the 2WIRE network setup.) 2) Home Network --> Wireless Settings 3) Change the following: a) Network Name (SSID) b) Wireless Channel (I changed it to the highest Mhz value) c) Disable Network Security d) Change Power Setting to any value (I chose 4 [Default]) 4) Click Save changes and wait until it rearranges whatever it needs to. 5) When it reloads, click the Restore Defaults button to undo everything you did on step 3. (yeah :confused: ... weird but it works) 6) Retry connecting to your 2WIRExxx network I don't know why but this has helped me when I try it and I was able to connect again... Hope it helps you!!! |
Quote:
"Disable Network Security" I've read through all the posts in this thread and they all seem to have a similar story: Disable security and it works. This isn't a solution, its a poor work around. Opening up your wireless network to allow you to connect is like leaving your front door unlocked because your key sometimes gets stuck. The problem is either with the key (laptop) or with the lock (router) and should be addressed. I stumbled upon this thread because I'm having a similar problem albeit with a D-Link 624 router. With an Open network or with WEP it appears to work fine, however I want to use WPA-PSK. Changing the channel on the router to Ch. 7 seems to have helped. Kind of odd though isn't it? I'm able to connect to this same router with the same encryption with both my Dell Inspiron 600m (using a Dell TrueMobile Wifi NIC) and my wife's Dell Inspiron 6000 (using an Intel PRO/Wireless Wifi NIC) however my Macbook Pro (non C2D) can't. Additionally I have another router (Linksys WRT54G running DD-WRT) that's setup with WPA-PSK (TKIP+AES) in which I have no trouble at all connecting to with my Macbook Pro. I didn't have the change the channel on that router to get it to work. Right now I can connect to one of my wireless routers (Linksys) with no trouble or tweaking and the other D-Link624 as long as I leave it on Ch7. Does anyone know of a more permanent solution? Or at least whether Apple has identified this as an issue? |
I have tried most of the various fixes here in trying to get my new Macbook Pro connected to my D-Link router to no avail:
- changed to channel 7 - changed the SSID - changed the WPA password Looks like the only fix is going to be another Airport update to fix what they broke in 2007-02. This is getting really serious as I am now finding that I cannot connect to some important public access points that I was able to connect to prior to 2007-02. |
I agree this seems to be Airport related.
I have used the AT&T supplied 2WIRE wireless modem/router for years with WPA-PSK for ages.... then it stopped working with all my security enabled. I am still able to use WPA, and I automatically reconnect, but in order to do so, I must enable "broadcast SSID". |
Just got the mac book pro. Worked for 3 days and now nothing. Im glad to see Im not the only one who has been yelling at Apple and SBC. My question is simple...
Where do I go to change the SSID? Do I need to connect via Ethernet to do this? aw3 |
I just received a reply back from ADC where they stated that the 2007-02 Airport update bug is a "known issue" and "it is currently being investigated by engineering". Unfortunately, this "known issue" has broken airport for apparently everyone who uses a Macbook or Macbook Pro to connect to a variety of wireless routers with WPA. I have done quite a bit of searching around on this and there is apparently no reliable fix at the moment. Our only hope appears to be hoping that Apple will come out with a new patch and soon.
There is quite a long thread on this subject at: http://discussions.apple.com/thread....art=0&tstart=0 And understandably, there are quite a few very frustrated and irate posters there as well. |
Mac releases compatibility update
In addition to my previous post this recently came up. Apple released an update which would increase compatibility with your 2Wire. http://www.apple.com/support/downloa...te2007002.html
Apparently there were some wireless issues that this patch has fixed. I’m including my previous post for those who missed it. I read your guys problems and thought I would offer some words of advice. When they started putting the core2 duo in the Mac book I had to get one so when I did I went to set it up with my 2wire I didn’t have any issues. I was running a 2Wire 270hg and firmware 5.29.51. Upon reading your issues I decided to do some testing. I had access to a couple different model 2wires besides the one I normally use and decided to test them with my Macbook. Here are the results of what I found: Using a 2701hg-b running firmware 5.29.47 and an 1800hg running firmware 3.7.1 I was unable to recreate the issue of not working with the 2Wire. I was using a Macbook core2duo with 10.4.8. I tried it before the January 07 airport update, after the January update, and after purchasing the 802.11n upgrade. I tried wep open, wep shared, and WPA on both 2Wire. I also tried wpa2 on the 2701 since it was supported by that model HPL. I encountered no difficulties prior to the updates. After the January update I encountered some minor issues initially with wep. To fix it I cleared my preferred networks (located in system preferences, network, show airport and on the airport tab) and the keychain records of the 2Wire in osx. (Located in Apps, Utilities, then Keychain Access remove all 2Wire entries) After resetting the settings I tried WPA and it worked, then verified all the other forms of encryption worked as well. The most probable cause of the issue is either entering invalid settings or the wrong settings were being stored in the Mac preventing it from connecting. A couple other things that are useful in a situation like this is to change the SSID on the 2Wire so that your Mac treats it like a new network and selecting a custom encryption key (your 10-digit phone number for example to do so go to http://gateway.2wire.net then home network and wireless settings to do change the settings). If you specify 40/128 bit hex when entering the wep key than the $ isn’t necessary. The $ also isn’t necessary when using WPA. Next I proceeded to check the encryption after each of the OSX upgrades that are available with multiple 2Wire modems. It worked properly with the 2701 and the January upgrade and all forms of encryption after my previously mentioned trouble shooting. Upon upgrading to enable 802.11N there were no issues with the 2701 or 1800 with all forms of available encryption. If these suggestions don’t help let me know I will be checking back on this thread to see what I can do to help any one having difficulty. One last note, check your computer’s computer name located in system preferences, sharing. If there are any spaces or special characters in your name it could be causing some of your issue, use only letters and numbers not any of the following ` ~ ! @ # $ % ^ & * ( ) { } | [ ] \ ; ’ ” : ,./?>< or any others I may not have listed. If you cant get wep open to work wep shared or wpa should work fine. WEP keys need to be 10 or 26 digit hex numbers and WPA needs at least 8 digits. |
Regarding sodagreen's recommendation of the 2007-02 update (above), be VERY careful about electing to install this if you have not done so already. Rather than fix compatibility with third-party routers, this update effectively breaks the Airport card in Macbooks and Macbook Pros so that they can no longer connect to certain routers that are using WPA. This is my case, my Macbook Pro cannot connect to the wireless router at my office, as well as several other locations. D-Link routers seem particularly affected.
Because of Apple's "update", I was forced to go out and purchase a new router (and NOT an Airport Base Station, thank you) since my D-Link at home was useless for connection with my Macbook Pro following installation of the 2007-02 update. Do keep this warning in mind if you are thinking of installing the 2007-02 update. I wish I had not installed it. |
How do I change my channel? I just ran iStumbler on my macbook and 4 other networks are on the same channel as me and I think this is why I'm getting a slow connection.
|
Quote:
|
This works for me, on a 2Wire 1800 HG.
(all these settings can be found on the rooter, accessible from your browser at http://home) from the local network area 'tab', wireless (Reseau domestique in french). - I have a custom ssid. - I am on channel 7. - I set the wireless mode to WPA (needs more than 8 chars). For some reason WEP mode is not allowed (maybe the OSX security patch prevent this rather insecure mode ?). |
Airport Extreme Update 2007-003 and latest Security Update.
Hello All.
I have delayed installing the most recent security update and Airport Extreme Update because of the various problems I and others have discussed in this thread. What is the current advice? Do these updates fix the problem or create more? As a side note.... My notebook now connects with NO PROBLEM to my 2Wire 1800HG. It started hooking up automatically last week after over a month of problems. I had resolved MY PROBLEM by running a wire. You know... brute force ethernet. Was it the phase of the moon or perhaps my Airport Card got jealous? Regards Mars |
THE FIX FOR THE MACBOOK PRO 1800HG WIRELESS CONNECTION ISSUES:
I to have a 2wire 1800HG. Firmware 3.7.3. I could not even connect to my 2Wire with security turned off and the SSID broadcasting. Thanks to my neighbor I was able to search this forum from his unhidden unsecured linksys. On to the good stuff: I am an AT&T DSL Subscriber. If you want this to work without changing a thing on your 2WIRE upgrade your firmware on the 1800HG to 4.25.19 I did this and was able to connect without changing the default SSID, Encryption Code or Channel on the router. I tested WPA and yes WEP Encryption without a hitch. On the WEP Code I used the $ on WPA there was no need. AT&T sent me a Blue Backup CD. In the "Utils\recovery" folder there were 3 .2sp files. The file you want to copy locally off the cd is recovery_425.2sp The only advice I can give you during the upgarde is the following: 1. Do not unplug the modem or disconnect the hardwired system that your using to perform the firmware upgrade with from the router during the upgrade. (If you do this you will be left with a paper weight) 2. open 2 seperate browser windows. http://gateway.2wire.net/ http://gateway.2wire.net/tech/upgrade.html The reason for this is if you just run the upgrade.html page there is no status. There is a text box and browse button to point to the locally stored firmware file. The modems lights will cycle amber for the length of the upgarde which in my case was 30 minutes. If you refresh the upgrade.html page during the upgrade it doesn't harm the modem but it cancels the upgrade. If you want to see status look at the http://gateway.2wire.net/ page. During the upgrade it will show you the progress of the upgrade but be patient. Wait until the lights on the modem stop cycling amber even though the status page shows 100% complete there are a few other things that need to happen before the lights go all green. I hope this helps. On a seprate note I also have my MacBook Pro Core 2 Duo fully updated Good Luck... |
2WIRE(1800) FIX with Macbook Pro
This is what i recently did, after muckign about 2 weeks on the damn thing. I'm sharing this because it drove me mad. The other way was to totally disable the wireless security, but that's dangerous. But here's another way. Tested on a Macbook Pro successfully.(but didn't work on my bootcamp WinXp OS though)
1. Go to your 2wire homepage portal. 2. Go to Wireless Settings 3. Select WPA-PSK 4. Then enter a 20 digits. (Makesure you write it down and store it somewhere safe where you won't forget) 5. SAVE. 6. FOR PCs - Click on WPA-PSK/TKIP 7. FOR MACs - Select WPA personal 7. Enter the 20 digits. It should work then. Worked on mine. Also My Macbook pro was running on Tiger 10.4.8, with the latest Airport Extreme wireless updates. |
Prodigy Infinitum 2wire Macbook pro error
a powerbook G4 works fine with 2wire modem 1700 (wireless mode) but as soon as you try to connect a macbook pro, it reads "there was a problem joining .... please try again". i tried out my macbook at a friends house, he has a newer 2wire modem and it works just fine.
I tried all the sugestions at my house, change wireless channel, turn off password wep security, etc. After a while it works.... but as soon as i turn the power of my 2wire off, and turn it back on.. problem starts again. after reading all posts in different sites i found out 2wire 1700 and 1800 are nos compatible with macbooks, they show an error to distribute correctly a new ip adress. In my experience you should all try changing your 2wire model to a newer version... i´m still waiting for a new one provided by prodigy infinitum completely free. If it works i´ll post which 2wire model works. |
Quote:
I had no more problems with the wi fi at home, except when the electricity goes off. I wanted to buy apple airport extreme base station... in order also to take advantage of the 802.11n, but if I can get a new modem for free... I will save that money for something else. sbs |
2wire oddities & quick but incomplete solution
Half-solution while working on other solutions: I found that turning off WEP security on the wireless router let me connect, as others have said, but then I could turn security back on and stay connected. That is, until the power (or IP address?) was toggled on the router, then I had to do it again.
Our 2wire 1000HG was piling up *active* connections anytime a friend came over and got on the wireless, never making them inactive or removing them. We had reached 30, which is some kind of limit. I called our ISP and had this cleared -- along with a few other simultaneous changes, these seems to have helped (sorry I can't be clearer about which helped). More details: it worked until yesterday, when a Vonage router was added and the power turned off for the 2wire. Our house will be looking for a replacement for 2wire if we find a cheap one... -Stephen Replacing cars with community |
MacBook and 2Wire
I just got a MacBook that boots to mac or windows xp. oddly, it connects to the 2wire ONLY when i boot to the mac side. the xp side will not connect!!! i kept tweaking the settings thinking it was the card or the box. wireless access is a no brainer. tried all the stuff you all suggested, but still will not connect on the pc side.
|
| All times are GMT -5. The time now is 07:13 PM. |
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.
Site design © IDG Consumer & SMB; individuals retain copyright of their postings
but consent to the possible use of their material in other areas of IDG Consumer & SMB.