Texas04 said:Just to clarify, does anyone have this problem and not have an Airport base station but instead a regular router?
If you go back four or five messages, you'll see my issues. I have a netgear router.Texas04 said:Just to clarify, does anyone have this problem and not have an Airport base station but instead a regular router?
Bluured arms said:I had the wireless problem from day one. I got fed up and hooked a cable up to my linksys router and still had very erratic download speeds and upon waking my IP address would be reset. I tried everything in the Apple Discussion threads and nothing worked...until I disabled IPv6. As soon as this was gone, I was blazing through the speakeasy test and was able to watch QT movie trailers without them pausing all of the time.
Also, I bought an AEBS and everything is so much smoother, but I noticed that it requests to keep IPv6 on to "communicate better". I called my cable company and they said don't use it under any circumstance since its not supported.
Don't know if this will help!
Ron
plinden said:If you go back four or five messages, you'll see my issues. I have a netgear router.
applekid said:snip
3. My AirPort Extreme Card has been acting funny. My router and my iMac G4 is running without a problem for internet connections. But sometimes, my iMac Core Duo cannot find my router. I have Interference Robustness on. Maybe that's the problem. This problem has occurred a couple of times over the last day and it's after I had that option on.
Passante said:I saw the new Macpro books at the Apple store this weekend. Both laptops had WIRED ethernet connections. They were not using WIFI. Didn't notice how the iMacs were connected since everything is in the back.
Here is hoping for an Intel mini on Tuesday.
MacRumorUser said:The issue is only effecting the new Intel iMac's both 17" & 20". It's not the same Airport card used in all other mac's it's a new one and hence the problems. Its also the same as the one that will be used in the new macbookpro and hence it to will probably suffer the same problems with wireless. In fact it may suffer worse as it's a mobile device and hence it's location to a basestation changes more so than a desktop...
It's seems pretty much universal problem with the intel imacs and I'm sure it's a juvenile driver that's the cause. 10.4.5 for intel or a specific airport update will no doubt find it's way to us. It's just a case of make do with it at the moment.
MacRumorUser said:And why not we wonder? There is a big open case on the Airport issues and it is catagorised by Apple as somthing that has to be sorted before the next update release (so it is looking like a software problem (phew) and not hardware)..
Apple support discussions have a lot of posters with the same problem and it's good to see apple acknowledge it.
Surprised mac book pro owners haven't reported anything back yet, but I guess unless you have a comparison at hand you probably wouldnt realise there was a problem...
mkrishnan said:I think the big differences are that, in the old days, hard drives were not as fast, and programs were not as large, and so people tried to avoid using VM altogether for performance reasons. It's still true that VM drags your system down. The difference is that now, everything is built around a model of using it. Also, as far as OS X is concerned, it comes from a Unix heritage, and Unix has used this model for a long time.
No, makes no difference to my wireless download speeds - still at 1/3 - 1/4 of wired when using WPA encryption. I guess I could go to WEP encryption with SSID broadcast off and MAC address filtering.Zaty said:Apparently, the chipset seems to have problems with (certain?) 802.11g routers. Switching your network to 802.11b solves the problem! Further information can be found here:
http://discussions.apple.com/thread.jspa?messageID=1822533#1822533
Do you have a link for this? I would like to follow this to get the solution if or when it's ready.MacRumorUser said:And why not we wonder? There is a big open case on the Airport issues and it is catagorised by Apple as somthing that has to be sorted before the next update release (so it is looking like a software problem (phew) and not hardware)..
Apple support discussions have a lot of posters with the same problem and it's good to see apple acknowledge it.
Zaty said:Apparently, the chipset seems to have problems with (certain?) 802.11g routers. Switching your network to 802.11b solves the problem! Further information can be found here:
http://discussions.apple.com/thread.jspa?messageID=1822533#1822533