Q: 27" imac wifi problems (intermittant)

same problem here! can't believe i've paid for this suffering.

I myself am also having this problem. The new 27" imac arrived 2 days ago and looked great. Wireless worked great as well. Then i decided to update to 10.6.4 since then i have had intermittant cut outs. sometimes the airport says it has full signal yet the internet doesn't work, and yet sometimes it doesn't pick up my router at all. It's weird how it will work perfectly with full signal for around half an hour and then randomly stop also. Considering the large amount of posts in the group it isn't down to the software update alone.

This isn't what i expect from something which costs around £1500. My other imac, macbook and iphone all work perfectly in the same room, it's just the 27" imac. What are you doing to look into this apple!? I have tried all the suggestions above and nothing is working.

I recommend contacting Apple about this issue. I have done so, and although they have not yet solved the problem, they know about it. It was clear from my discussion with the tech that Apple is unaware that there is a widespread wi-fi issue with their iMacs. The more people raise it with them, the more likely it is to be addressed.

called this morning to apple brazil explaining my problem. they are really not aware about this situation. a tech guy asked me to reinstall snow leopard and see what happens.

I have a 2009 iMac 20 and have the exact same issue. I should have returned the iMac right away when it was new. No software updates have arranged anything, but I think it has to do with the antenna, or then with the airport. It appears that the position of the iMac makes a difference, more than the distance.

Bought my iMac i5 27" a month ago and experienced the wifi dropout issue about 2 weeks after the purchase. It would disconnect from my router and have trouble detecting all surrounding ones. Turning Airport on and off will not work - only a reboot will. Sometimes after a reboot, I would get a "Airport card not installed".

I've sent it to the nearest Apple authorized service provider and they have replaced the Airport card but to no avail. I have tried all methods as recommended by the folks in this thread, and also downgraded from 10.6.4 to 10.6.2 then to 10.6.3, it seems a little more stable but the problem persist.

Right now I do not know if I should get another router to test it out as my current one is a very old Linksys WRT54G.

Sigh. What happened to Apple's "It just works" ?

Same problem here (on one of the first refurbished model). I've been lazy and let it go, thinking it would be fixed with a software update. but it hasn't. I have an Airport Express running 802.11n I'll fiddle with the wireless settings tonight to see how it changes the problem.

I have 5 bars but horrific latency/loss, which makes the computer unusable.

Same problem here had my imac 27" Imac for a week connected fine for the first few days then connection dropped deleted all network settings and got it back up and running for a day but again its dropped and wont connect same story as everybody else my mac book pro and iphone in the same room connect no problem....this is such ********!!!!! Apple really have gone down hill i've been using macs since the early beige ones and have never had trouble with any of the Macs its a total joke that something that cost £1500 can have such a problem......I SOOOOOOOOOO FLIPPPPING ANGRY!!!!!!!!!!!!!!!

same problem with my imac 27 inch, bought in dec.poor speed over WiFi. tried many settings and doesnt work. but windows 7 on bootcamp installed on the same computer has very good wifi reception and speed.(similar to other pcs in the room) So likely a software issue with the OS X.
due to this issues, i am mostly using windows on my mac.

Just to add to the confusion...I have a 20" IMAC (purchased in 2007) that I JUST upgraded to Snow Leopard. Ever since...cant seem to maintain a strong and fast wireless connection. Using Netgear WGT624 v2 router. Any suggestions would be most helpful! Thanks.

Let me add to this topic. I bought an iMac 27" in January and I have been having similar problems for two months now. The machine has been in twice to have parts replaced and is going in again this week.

The symptoms are the same each time. First the wireless connection slows down, then it drops out intermittently and then it stops working altogether.

At the first repair the Airport card was replaced. At the second repair the airport card and the motherboard were replaced. I don't know what they are going to do this time. If it fails again I will be requesting a replacement computer.

I have Applecare support and they have had me trying everything. Resetting the computer, adding new locations, changing the wireless channel - you name it. I have no issue with their efforts to help me.

We have a 15" Macbook pro, iMAc 24", two iphones, a Nintendo Wii and two Nintendo DSIs that all connect fine to the Netgear router.

The thing that stands out is that I have installed iStumbler on the iMac 27" it can't detect any networks at all from that machine. iStumbler on the iMac 24" shows that there are 2+ networks available at any time. This would seem to point to issues with the Airport card or its antenna.

I'm inclined to agree with suggestions from other posters that overheating may be causing the issue/

cheers,

Darren

I am having exactly the same issue with my iMac i5...

I have a MBP and it connects fine, but the iMac doesn't, it's connection is patchy and sloooooowwwww!.

I have a linksys wag320n without security enabled (just mac address inclusion) on an 8mb line. When is connect the iMac with a cable I get consistent 7mb connection download speed using wifi i am lucky if i get 700kb.

APPLE please fix this issue.

Wanted to add my $0.02.
Here is the output from my ping test via Network Utility.

PING 192.168.1.1 (192.168.1.1): 56 data bytes
Request timeout for icmp_seq 0
64 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=1473.547 ms
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=474.457 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=0.735 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=0.762 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=2.799 ms
Request timeout for icmp_seq 6
64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=2530.812 ms
64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=1531.551 ms
64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=531.861 ms
64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=0.738 ms
64 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=0.769 ms
64 bytes from 192.168.1.1: icmp_seq=10 ttl=64 time=0.743 ms
64 bytes from 192.168.1.1: icmp_seq=11 ttl=64 time=2586.053 ms
64 bytes from 192.168.1.1: icmp_seq=12 ttl=64 time=1587.668 ms
64 bytes from 192.168.1.1: icmp_seq=13 ttl=64 time=587.912 ms
64 bytes from 192.168.1.1: icmp_seq=14 ttl=64 time=0.741 ms
64 bytes from 192.168.1.1: icmp_seq=15 ttl=64 time=0.738 ms
64 bytes from 192.168.1.1: icmp_seq=16 ttl=64 time=0.746 ms
64 bytes from 192.168.1.1: icmp_seq=17 ttl=64 time=2627.496 ms
64 bytes from 192.168.1.1: icmp_seq=18 ttl=64 time=1629.225 ms
64 bytes from 192.168.1.1: icmp_seq=19 ttl=64 time=630.138 ms

--- 192.168.1.1 ping statistics ---
20 packets transmitted, 20 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.735/809.975/2627.496/943.875 ms

Not having packet loss, per se, but there is a very distinct pattern to the latency. Any thoughts?

I have also started to see the same issue on my iMac 27" i7. The problem did go away (I think) after a reboot, but has come back recently... if I can reliably fix it with a reboot I suppose that is not too bad, but would rather that it just kept working;

My Network Utility ping to my wireless router from my iMac:

Ping has started…

PING 192.168.1.254 (192.168.1.254): 56 data bytes
Request timeout for icmp_seq 0
64 bytes from 192.168.1.254: icmp_seq=0 ttl=128 time=1003.104 ms
64 bytes from 192.168.1.254: icmp_seq=1 ttl=128 time=3.078 ms
64 bytes from 192.168.1.254: icmp_seq=2 ttl=128 time=1.271 ms
64 bytes from 192.168.1.254: icmp_seq=3 ttl=128 time=1.359 ms
64 bytes from 192.168.1.254: icmp_seq=4 ttl=128 time=1.234 ms
64 bytes from 192.168.1.254: icmp_seq=5 ttl=128 time=1293.061 ms
64 bytes from 192.168.1.254: icmp_seq=6 ttl=128 time=293.863 ms
64 bytes from 192.168.1.254: icmp_seq=7 ttl=128 time=1.237 ms
64 bytes from 192.168.1.254: icmp_seq=8 ttl=128 time=1.275 ms
64 bytes from 192.168.1.254: icmp_seq=9 ttl=128 time=1.464 ms
64 bytes from 192.168.1.254: icmp_seq=10 ttl=128 time=1587.134 ms
64 bytes from 192.168.1.254: icmp_seq=11 ttl=128 time=587.005 ms
64 bytes from 192.168.1.254: icmp_seq=12 ttl=128 time=1.256 ms
64 bytes from 192.168.1.254: icmp_seq=13 ttl=128 time=1.467 ms
64 bytes from 192.168.1.254: icmp_seq=14 ttl=128 time=1.361 ms
64 bytes from 192.168.1.254: icmp_seq=15 ttl=128 time=1876.067 ms
64 bytes from 192.168.1.254: icmp_seq=16 ttl=128 time=876.047 ms
64 bytes from 192.168.1.254: icmp_seq=17 ttl=128 time=1.260 ms
64 bytes from 192.168.1.254: icmp_seq=18 ttl=128 time=1.334 ms
64 bytes from 192.168.1.254: icmp_seq=19 ttl=128 time=1.407 ms
Request timeout for icmp_seq 21
64 bytes from 192.168.1.254: icmp_seq=20 ttl=128 time=2166.426 ms
64 bytes from 192.168.1.254: icmp_seq=21 ttl=128 time=1170.892 ms
64 bytes from 192.168.1.254: icmp_seq=22 ttl=128 time=172.154 ms
64 bytes from 192.168.1.254: icmp_seq=23 ttl=128 time=1.289 ms
64 bytes from 192.168.1.254: icmp_seq=24 ttl=128 time=1.337 ms
64 bytes from 192.168.1.254: icmp_seq=25 ttl=128 time=1.394 ms
64 bytes from 192.168.1.254: icmp_seq=26 ttl=128 time=1456.939 ms
64 bytes from 192.168.1.254: icmp_seq=27 ttl=128 time=458.572 ms
64 bytes from 192.168.1.254: icmp_seq=28 ttl=128 time=2.082 ms
64 bytes from 192.168.1.254: icmp_seq=29 ttl=128 time=1.272 ms
64 bytes from 192.168.1.254: icmp_seq=30 ttl=128 time=1.380 ms
64 bytes from 192.168.1.254: icmp_seq=31 ttl=128 time=1748.805 ms
64 bytes from 192.168.1.254: icmp_seq=32 ttl=128 time=750.289 ms
64 bytes from 192.168.1.254: icmp_seq=33 ttl=128 time=1.446 ms
64 bytes from 192.168.1.254: icmp_seq=34 ttl=128 time=1.472 ms
64 bytes from 192.168.1.254: icmp_seq=35 ttl=128 time=1.523 ms
64 bytes from 192.168.1.254: icmp_seq=36 ttl=128 time=2040.129 ms
64 bytes from 192.168.1.254: icmp_seq=37 ttl=128 time=1041.186 ms
64 bytes from 192.168.1.254: icmp_seq=38 ttl=128 time=43.157 ms

And from my 3+ yr old 1st gen MacBook sitting on the same desk...


Ping has started ...

PING 192.168.1.254 (192.168.1.254): 56 data bytes
64 bytes from 192.168.1.254: icmp_seq=0 ttl=128 time=2.726 ms
64 bytes from 192.168.1.254: icmp_seq=1 ttl=128 time=2.342 ms
64 bytes from 192.168.1.254: icmp_seq=2 ttl=128 time=2.153 ms
64 bytes from 192.168.1.254: icmp_seq=3 ttl=128 time=2.832 ms
64 bytes from 192.168.1.254: icmp_seq=4 ttl=128 time=2.092 ms
64 bytes from 192.168.1.254: icmp_seq=5 ttl=128 time=2.157 ms
64 bytes from 192.168.1.254: icmp_seq=6 ttl=128 time=2.125 ms
64 bytes from 192.168.1.254: icmp_seq=7 ttl=128 time=2.203 ms
64 bytes from 192.168.1.254: icmp_seq=8 ttl=128 time=2.110 ms
64 bytes from 192.168.1.254: icmp_seq=9 ttl=128 time=2.105 ms
64 bytes from 192.168.1.254: icmp_seq=10 ttl=128 time=2.503 ms
64 bytes from 192.168.1.254: icmp_seq=11 ttl=128 time=2.099 ms
64 bytes from 192.168.1.254: icmp_seq=12 ttl=128 time=2.251 ms
64 bytes from 192.168.1.254: icmp_seq=13 ttl=128 time=2.015 ms
64 bytes from 192.168.1.254: icmp_seq=14 ttl=128 time=2.143 ms
64 bytes from 192.168.1.254: icmp_seq=15 ttl=128 time=2.142 ms
64 bytes from 192.168.1.254: icmp_seq=16 ttl=128 time=2.168 ms
64 bytes from 192.168.1.254: icmp_seq=17 ttl=128 time=2.810 ms
64 bytes from 192.168.1.254: icmp_seq=18 ttl=128 time=2.222 ms
64 bytes from 192.168.1.254: icmp_seq=19 ttl=128 time=1.262 ms
64 bytes from 192.168.1.254: icmp_seq=20 ttl=128 time=1.934 ms
64 bytes from 192.168.1.254: icmp_seq=21 ttl=128 time=3.188 ms
64 bytes from 192.168.1.254: icmp_seq=22 ttl=128 time=1.397 ms
64 bytes from 192.168.1.254: icmp_seq=23 ttl=128 time=2.167 ms
64 bytes from 192.168.1.254: icmp_seq=24 ttl=128 time=1.341 ms
64 bytes from 192.168.1.254: icmp_seq=25 ttl=128 time=2.216 ms
64 bytes from 192.168.1.254: icmp_seq=26 ttl=128 time=2.794 ms
64 bytes from 192.168.1.254: icmp_seq=27 ttl=128 time=2.144 ms
64 bytes from 192.168.1.254: icmp_seq=28 ttl=128 time=2.026 ms
64 bytes from 192.168.1.254: icmp_seq=29 ttl=128 time=2.980 ms
64 bytes from 192.168.1.254: icmp_seq=30 ttl=128 time=1.555 ms
64 bytes from 192.168.1.254: icmp_seq=31 ttl=128 time=2.256 ms
64 bytes from 192.168.1.254: icmp_seq=32 ttl=128 time=9.443 ms
64 bytes from 192.168.1.254: icmp_seq=33 ttl=128 time=2.134 ms
64 bytes from 192.168.1.254: icmp_seq=34 ttl=128 time=2.154 ms
64 bytes from 192.168.1.254: icmp_seq=35 ttl=128 time=2.158 ms
64 bytes from 192.168.1.254: icmp_seq=36 ttl=128 time=2.732 ms

Latest news from the Apple repairer is that they are going to replace the Airport card again and an additional cable that was not replaced the last two times.

The repairer has told me that beyond that there is nothing they can do and that, in their view, the problem has to be caused by an incompatibility between my router and the new iMac. I find this a bit hard to believe as each time the computer has been returned after repair it has worked for a while before it lost connection.

I guess we'll wait and see.

Darren