Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
3.4 was fine...

You know, I think what I am seeing here is someone blaming a temporary network problem and not an airport problem. Why blame the update? Did you check everything? I had Samba shares work fine. Printing worked fine. Limewire and other P2P software may have had other issues. Don't be so quick to judge the update. I am glad 3.4.1 appears to have fixed the "problems" but I personally think the following were not problems with the update perse:

Signal Strength drops: This could happen because of Microwaves being run, because of wireless video cams in the 2.4 GHz band, cordless phones and a myriad of other devices that could all cause interference to the WiFi (airport) base station or card. There are also many other reasons for the signal strength to "drop". If you are losing connections, try turning on/off other features and see if it returns. This may help Apple determine what the problem with an update may be if the update really caused an issue.

Limewire/P2P Software: I ain't even going there. If these don't work it ain't Apple's responsibility to fix. Plus, their rep on Windows platforms for bringing down spyware during installs is something I don't want them even thinking of doing on Mac OS X. We don't need Windows problems to migrate to the Mac.

Samba Shares: Mine worked fine. Again, I think this was temporary network issues on your side.

Accessing a Windows Printing Share: Never had an issue.

Give Apple the benefit of the doubt and try not to pay to much attention to the signal strength meter. If it works (ie your connected and the speed is fine), then don't bitch about the meter dropping. If your having issues connecting, I would try increasin the AP's profile. Rubber ducks are pretty bad antennas. Thing about replacing them with some other WiFi/2.4 GHz band antennas. As far as the Apple Airport Base Stations, I don't know...can you have a external antenna??
 
mgescuro said:
I don't see much of a difference either. In class at school, I'd have 2-3 bars with 3.3. With 3.4, I'd get 0-2 bars. Now with 3.4.1, I get about 1-2 bars, with the occasionaly 0 bars/loss of signal. yes, it's temporary... but it's annoying when you're trying to watch a baseball game in class.... and it stalls the feed. :rolleyes:

With that poor a signal, I'm not surprised. Even 3 bars is going to be of marginal use.
 
I wish I could throw this info into the apple tech's face, him saying that it was my walls was making me lose my basestation was pissing me off. I've had this basestation for over a year and have never had the problem until that last update. Apple techs suck if you ask me; they are never up-to-date.
 
gorkonapple said:
You know, I think what I am seeing here is someone blaming a temporary network problem and not an airport problem. Why blame the update? Did you check everything? I had Samba shares work fine. Printing worked fine. Limewire and other P2P software may have had other issues. Don't be so quick to judge the update. I am glad 3.4.1 appears to have fixed the "problems" but I personally think the following were not problems with the update perse:

[snip]

Usually, I'd be sympathetic to the point you're making. But there was a real issue with 3.4 for many users including myself. This makes only my second update problem (the other being the infamous 10.2.6 ... or was it 10.2.5? ... update). So by and large, I've been problem-free since upgrading all the way from 10.0.3.

Luckily, there's a great web page describing restoring the 3.3 software, which I used immediately after I realised the 3.4 update caused a decreased signal range that affected my network. Glad to see Apple have released an updated 3.4.1 to correct the problem -- I'll be updating when I get home from work.

Previously, I'd had zero problems with Airport updates. My network was fine. The 3.4 update caused problems, reverting to 3.3 fixed it. That, plus the comments from dozens of people at the Airport support forums at apple.com, not to mention the fact that this 3.4.1 update was released at all makes it pretty clear that there was something amiss in the initial update (at least for some configurations).

Don't be so quick to dismiss others' problems just because you've not been affected ;) :)

Incidentally, one of my favourite things about OS X is that random weirdness is very rare. The system's stable enough that if something goes wrong, I can almost always trace it back to a change that I've made and undo that change. I didn't need to go around and re-check everything that had been working previously, since I could rely on OS X not to have suddenly decided to break un-related services just because a different componen't driver had been updated. Updating a few Airport kext's won't magically change my samba config.
 
displaced said:
Usually, I'd be sympathetic to the point you're making. But there was a real issue with 3.4 for many users including myself. This makes only my second update problem (the other being the infamous 10.2.6 ... or was it 10.2.5? ... update). So by and large, I've been problem-free since upgrading all the way from 10.0.3.

Luckily, there's a great web page describing restoring the 3.3 software, which I used immediately after I realised the 3.4 update caused a decreased signal range that affected my network. Glad to see Apple have released an updated 3.4.1 to correct the problem -- I'll be updating when I get home from work.

Previously, I'd had zero problems with Airport updates. My network was fine. The 3.4 update caused problems, reverting to 3.3 fixed it. That, plus the comments from dozens of people at the Airport support forums at apple.com, not to mention the fact that this 3.4.1 update was released at all makes it pretty clear that there was something amiss in the initial update (at least for some configurations).

Don't be so quick to dismiss others' problems just because you've not been affected ;) :)

Incidentally, one of my favourite things about OS X is that random weirdness is very rare. The system's stable enough that if something goes wrong, I can almost always trace it back to a change that I've made and undo that change. I didn't need to go around and re-check everything that had been working previously, since I could rely on OS X not to have suddenly decided to break un-related services just because a different componen't driver had been updated. Updating a few Airport kext's won't magically change my samba config.

Well said I must say.
 
For real - my reception went seriously down!

I have in my home network (Airport Extreme Base Station) hooked up several computers. Particularly an iBook used by my wife lost the bars needed for her to work in her study (of the max 15 bars she usually had 5 which was enough for her network activity). This happened immediately after the update (from 5 to 2 bars). I never thought that the update could be the problem. I therefore searched the house, all antennas (radio frequency emitters) in the neighborhood and even tried to track other Wi-Fi nets in the area. Nothing helped.

My wife steadily complained about bad reception and I tried to ignore her.... since I could not find the source for the problem.

Yesterday, she was really irritated about the bad reception and I went and purchased a second Base Station to be linked to the first one. Lo and behold, life was livable again! She went from 2 to 13 bars in her study and now I had covered the whole yard and possibly the whole neighborhood.

Thus to my relief (frustration), I found a release of 3.4.1. on my update. I disconnected my second basestation. Did the update. Rebooted the machine. And yeupphs - 5 bars back again!

So the second Base Station bought for no use (except giving all my neighbors a net on their display saying "apple network"). Well, it could be useful later.

Anyhow, the update for real changed everything for me. The 3.4 took appr. 20% of the signal strength away, and the 3.4.1. brought it back again.

If not scientifically proven it cost me an extra Base Station.
 
Had no trouble here -

G5DP2w/ AE on cable modem - software base
iBookG3-800 w/ AirPort -> E-net to PM7500 (2 meters - 4 bars)
G4DP550 w/ AirPort -> E-net to PM8500 (12 meters - 3 bars)

New update changed nothing I can see. All is good.
 
Just installed on my 1GHz 12" PB. It fixed the problems from the last update, I'm back up to 3 bars from 1 bar.
 
I too had 3.4 problems, when you can have something work perfectly one minute, update, then have things not work as well the next minute, you can DIRECTLY relate that to the update...not my fictitious burrito cooking in the microwave.

3.4.1 is better, I have my bars back, but I don't think I have the speed back, I don't know, maybe Im just being paranoid. I glad Apple is trying to fix this, I have been rather frustrated with them as of late.
 
gorkonapple said:
You know, I think what I am seeing here is someone blaming a temporary network problem and not an airport problem. Why blame the update? Did you check everything? I had Samba shares work fine. Printing worked fine. Limewire and other P2P software may have had other issues. Don't be so quick to judge the update. I am glad 3.4.1 appears to have fixed the "problems" but I personally think the following were not problems with the update perse:

Signal Strength drops: This could happen because of Microwaves being run, because of wireless video cams in the 2.4 GHz band, cordless phones and a myriad of other devices that could all cause interference to the WiFi (airport) base station or card. There are also many other reasons for the signal strength to "drop". If you are losing connections, try turning on/off other features and see if it returns. This may help Apple determine what the problem with an update may be if the update really caused an issue.

Limewire/P2P Software: I ain't even going there. If these don't work it ain't Apple's responsibility to fix. Plus, their rep on Windows platforms for bringing down spyware during installs is something I don't want them even thinking of doing on Mac OS X. We don't need Windows problems to migrate to the Mac.

Samba Shares: Mine worked fine. Again, I think this was temporary network issues on your side.

Accessing a Windows Printing Share: Never had an issue.

Give Apple the benefit of the doubt and try not to pay to much attention to the signal strength meter. If it works (ie your connected and the speed is fine), then don't bitch about the meter dropping. If your having issues connecting, I would try increasin the AP's profile. Rubber ducks are pretty bad antennas. Thing about replacing them with some other WiFi/2.4 GHz band antennas. As far as the Apple Airport Base Stations, I don't know...can you have a external antenna??


Thanks for that great its your fault response. I for one don't know what the problem with airport is, but if nothing else changed except for the update, then it probably was the software. I have been having connection problems since 3.3. I have down graded to 3.2 because this seems to be more reliable for me. I have also notice that I can not log into the base station after several days. It just won't let me. I get the same error no matter if I try with my power book or with the hard line iMac that is attached to the base station. The only thing that works for me is to hard reboot the base station. But this is just what happens for me. Also you can have an external antenna.
 
A quick note to say 3.4.1's working fine -- none of the signal strength problems of the 3.4 release.

Firstly, thanks to the guy who put up a page on how to revert to v3.3 -- got things working until Apple could come up with a fix, and a grudging thanks to Apple for getting a fix out the door in just a week or so. I hope there's a long hall at 1 Infinite Loop with a Mac at one end, a base station at the other, and a big sign saying "Airport Engineers: If Your Update Breaks This Network, Don't Release It!"

:)
 
Since Apple posted a 3.4.1 so quickly, I think we can assume there really were problems with 3.4. Software companies don't do patches for no reason...

That said, signal strength is a tricky thing, and a lot of factors can come into play.

I was going to post that the update to 3.4.1 from 3.3.1 had increased my recieved strength, as before the update MacStumbler was showing a strength averaging around 40 (3 bars), and now it's spending most of the time over 50 (4 bars).

Then I realized that my sitting position had changed slightly, and my LCD is tilted back farther, so the integrated antenna is showing a better cross-section to the location of my router upstairs. Moving back to the original position goes back to the original signal strength.

So for those people who are seeing really different behaviour (signal strength went up for 3.4, down for 3.4.1 etc), remember, computer configuration, orientation, position, temperature, and even some weather patterns can affect reception.
 
displaced said:
Usually, I'd be sympathetic to the point you're making. But there was a real issue with 3.4 for many users including myself. This makes only my second update problem (the other being the infamous 10.2.6 ... or was it 10.2.5? ... update). So by and large, I've been problem-free since upgrading all the way from 10.0.3.

I believe it was 10.2.8....
 
Anyone using one of your macs as a software base station with this update? Have any PC's in the mix? I am using a PB and a Dell laptop (work) wirelessly from my iMac. Don't want to lose anything here.
 
displaced said:
Previously, I'd had zero problems with Airport updates. My network was fine. The 3.4 update caused problems, reverting to 3.3 fixed it. That, plus the comments from dozens of people at the Airport support forums at apple.com, not to mention the fact that this 3.4.1 update was released at all makes it pretty clear that there was something amiss in the initial update (at least for some configurations).

Don't be so quick to dismiss others' problems just because you've not been affected ;) :)

I may agree that it may have made a difference in your reception...but if your EXPECTING to get good reception with only 5 bars of signal, you must be joking (although the signal meter is just a estimate of your signal reception). This problem itself sounds like, to me, that it could be with a Airport base station. I did not see the point of spending a lot of cash on the airport base as it was definitely not adequate for my own network. I have a Linksys WRT54G and we use Cisco Aironet at work and in either case, I have had no issues either with 3.4 or 3.4.1. I'll have to poke around and find this evidence you say, but would be more interested in seeing info depending on what AP was in use be it a Airport Base or a Linksys WAP. I mean, the Airport base looks cool and all. but if you get a terrible signal (sorry, 5 bars in the same house as the AP is not acceptable) then what is the use? I tend to go for best of breed rather then the whole package and I have had nothing but great things to say about my Linksys in how it works together with my Powerbook. What's even better is I am using the Linux firmware and it is better then what Linksys shipped. Linksys has alot of experience making both switches and wireless AP's. Apple has not. So you get weirdness when you update things.
 
dudemac said:
Thanks for that great its your fault response. I for one don't know what the problem with airport is, but if nothing else changed except for the update, then it probably was the software. I have been having connection problems since 3.3. I have down graded to 3.2 because this seems to be more reliable for me. I have also notice that I can not log into the base station after several days. It just won't let me. I get the same error no matter if I try with my power book or with the hard line iMac that is attached to the base station. The only thing that works for me is to hard reboot the base station. But this is just what happens for me. Also you can have an external antenna.

Good thing on the external antenna and I highly reccomend adding a external one. There seems to be a equal number of people on both sides. I guess there can be a problem with the update, but people. if your connecting and working decently and only getting 3-4 bars, and a update all of a sudden causes you to loose that critical bar, then the problem is not as much the update, but with the physical location of your network or the AP. Software can change things I will agree. But if your in the same room as the AP and your not getting enough signal then the problem is not with your PowerBook or Powermac, it's the AP. If your in the same room, you should have considerable signal to work with. In my case, I am in the same room as my AP and I have 12 bars on Internet Connect with my Linksys WRT54G.

I have also seen several instances of problems similar to what your reporting specifically with the Airport Base Station. Random lockups and the like and even poor reception being reported as well specifically from Airport base stations. I love my Mac but I do not ever say everything Apple makes is good. I won't put up with bad performing hardware be it a laptop or a piece of network equipment. I am glad I bought my Linksys versus spending twice as much on something with not near as many options as my Linksys.
 
stcanard said:
Since Apple posted a 3.4.1 so quickly, I think we can assume there really were problems with 3.4. Software companies don't do patches for no reason...

That said, signal strength is a tricky thing, and a lot of factors can come into play.

I was going to post that the update to 3.4.1 from 3.3.1 had increased my recieved strength, as before the update MacStumbler was showing a strength averaging around 40 (3 bars), and now it's spending most of the time over 50 (4 bars).

Then I realized that my sitting position had changed slightly, and my LCD is tilted back farther, so the integrated antenna is showing a better cross-section to the location of my router upstairs. Moving back to the original position goes back to the original signal strength.

So for those people who are seeing really different behaviour (signal strength went up for 3.4, down for 3.4.1 etc), remember, computer configuration, orientation, position, temperature, and even some weather patterns can affect reception.

Exactly my point. Just to let everyone on the forum know, I am a Amateur Radio Operator and have a EE degree. I have been messing with RF for a long time. I have one specific place in my house that I sit where I get into a repeater outside of my house that's about 8 miles away(our current south side recieve site is down)so I have to go from where I live in the southend of Columbus to downtown Columbus with only a 5 watt handheld. If I move 5 feet in either direction I have problems. I'd love to increase my profile and often do with directional antennas. The problem isn't the radio, but it's my location. Using the same radio and putting a yagi antenna on it, it makes me able to hit it with only using half the power that the radio is capable of producing. So antennas are extremely important! Remember WiFi is not rocket science. It's pretty simple to change your antenna around for several commercially available antennas and there are several sites that have plans for making your own antennas.

That's not to say that there wasn't a problem. There must have been otherwise Apple would not have issued a patch. But, to me, the types of signal reports I am hearing indicates more then just a software update issue. I'll have to check out what my signal looks like in other parts of the house but I have not had an issue anywhere with connectivity. I even fired up the PB in the driveway while sitting in the car (the walls of the house and the car's frame around me) and had no issues.
 
Airport Extreme Base Station - Firmware update 5.4.

kcmac said:
Anyone using one of your macs as a software base station with this update? Have any PC's in the mix? I am using a PB and a Dell laptop (work) wirelessly from my iMac. Don't want to lose anything here.

kcmac - I have my iBook as the software base station. I have also a Windows PC in the mix with my Mac's. It worked fine for me.

I post this reply because there has come a firmware update to the Airport Extreme Base Station, but I only got the update notice when I plugged in the Ethernet cable to the base station. When the firmware was upgraded from 5.2 to 5.4 I noticed significant positive change. Combined with update 3.4.1. it has worked wonderfully for me.

Good luck!
 
Thanks Mac. Looks like I will give it a try. I usually update right away. Having a PC in the house that might be affected makes me a little more hesitant.
 
gorkonapple,

Be glad you get any good results with your linksys products as in my experience with any piece of their equipment I have found the quality very shoddy. I'd rather go with netgear or D-Link for any wireless/wired technology. You can even see the difference in build quality of the devices themselves.

Also, if someone is updating and doesn't move from where they are, as is usually the case with laptop users upgrading their AirPort firmware, and their signal strength drops when they restart, it's obviously a problem with the software on the computer unless they simultaneously updated the base station's firmware as well. In either case, signal strength dropping when people haven't moved indicates a problem with whatever occurred just prior to the drop, i.e. the upgrades. There was obviously a problem because they released a patch, 3.4.1 when the original update was 3.4. The .1 change indicates an update to the update, i.e. a patch on the update, therefore there must have been some problem.
 
Update help?

When I installed the upgrade, I had two strange things:

- Airport Software update was not automatically checked in Software update, which wouldn't be so strange except...

- When I re-booted, and ran the admin utility, it still says ver. 3.4

Strange? But when I run the udpated again it says I am up to date.

Where is the utility supposed to be located? Mine is in Applications/Utilities. I've noticed this kind of problem sometimes if I move the location of an application -- I made an "iApps" folder and put all of them in it, and it started saying they were all out of date and if I d/l'd the new version, it just made another copy of it in the original place. :(
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.