Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Airport Problems : All Intel Models Affected.
- Thread starter MRU
- Start date
- Sort by reaction score
Found it on the discussions. Here's the results...
PING 10.0.1.1 (10.0.1.1): 56 data bytes
64 bytes from 10.0.1.1: icmp_seq=0 ttl=64 time=197.534 ms
64 bytes from 10.0.1.1: icmp_seq=1 ttl=64 time=149.021 ms
64 bytes from 10.0.1.1: icmp_seq=2 ttl=64 time=100.993 ms
64 bytes from 10.0.1.1: icmp_seq=3 ttl=64 time=0.878 ms
64 bytes from 10.0.1.1: icmp_seq=4 ttl=64 time=54.998 ms
64 bytes from 10.0.1.1: icmp_seq=5 ttl=64 time=258.784 ms
64 bytes from 10.0.1.1: icmp_seq=6 ttl=64 time=210.735 ms
64 bytes from 10.0.1.1: icmp_seq=7 ttl=64 time=165.210 ms
64 bytes from 10.0.1.1: icmp_seq=8 ttl=64 time=119.005 ms
64 bytes from 10.0.1.1: icmp_seq=9 ttl=64 time=70.975 ms
64 bytes from 10.0.1.1: icmp_seq=10 ttl=64 time=23.022 ms
64 bytes from 10.0.1.1: icmp_seq=11 ttl=64 time=0.886 ms
64 bytes from 10.0.1.1: icmp_seq=12 ttl=64 time=0.904 ms
64 bytes from 10.0.1.1: icmp_seq=13 ttl=64 time=0.888 ms
64 bytes from 10.0.1.1: icmp_seq=14 ttl=64 time=0.968 ms
64 bytes from 10.0.1.1: icmp_seq=15 ttl=64 time=24.167 ms
64 bytes from 10.0.1.1: icmp_seq=16 ttl=64 time=0.937 ms
64 bytes from 10.0.1.1: icmp_seq=17 ttl=64 time=245.680 ms
64 bytes from 10.0.1.1: icmp_seq=18 ttl=64 time=197.731 ms
64 bytes from 10.0.1.1: icmp_seq=19 ttl=64 time=150.404 ms
--- 10.0.1.1 ping statistics ---
20 packets transmitted, 20 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.878/98.686/258.784/89.650 ms
Using the leap fix.
PING 10.0.1.1 (10.0.1.1): 56 data bytes
64 bytes from 10.0.1.1: icmp_seq=0 ttl=64 time=197.534 ms
64 bytes from 10.0.1.1: icmp_seq=1 ttl=64 time=149.021 ms
64 bytes from 10.0.1.1: icmp_seq=2 ttl=64 time=100.993 ms
64 bytes from 10.0.1.1: icmp_seq=3 ttl=64 time=0.878 ms
64 bytes from 10.0.1.1: icmp_seq=4 ttl=64 time=54.998 ms
64 bytes from 10.0.1.1: icmp_seq=5 ttl=64 time=258.784 ms
64 bytes from 10.0.1.1: icmp_seq=6 ttl=64 time=210.735 ms
64 bytes from 10.0.1.1: icmp_seq=7 ttl=64 time=165.210 ms
64 bytes from 10.0.1.1: icmp_seq=8 ttl=64 time=119.005 ms
64 bytes from 10.0.1.1: icmp_seq=9 ttl=64 time=70.975 ms
64 bytes from 10.0.1.1: icmp_seq=10 ttl=64 time=23.022 ms
64 bytes from 10.0.1.1: icmp_seq=11 ttl=64 time=0.886 ms
64 bytes from 10.0.1.1: icmp_seq=12 ttl=64 time=0.904 ms
64 bytes from 10.0.1.1: icmp_seq=13 ttl=64 time=0.888 ms
64 bytes from 10.0.1.1: icmp_seq=14 ttl=64 time=0.968 ms
64 bytes from 10.0.1.1: icmp_seq=15 ttl=64 time=24.167 ms
64 bytes from 10.0.1.1: icmp_seq=16 ttl=64 time=0.937 ms
64 bytes from 10.0.1.1: icmp_seq=17 ttl=64 time=245.680 ms
64 bytes from 10.0.1.1: icmp_seq=18 ttl=64 time=197.731 ms
64 bytes from 10.0.1.1: icmp_seq=19 ttl=64 time=150.404 ms
--- 10.0.1.1 ping statistics ---
20 packets transmitted, 20 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.878/98.686/258.784/89.650 ms
Using the leap fix.
Mine is fixed! I just did a complete reinstall of Tiger and now I am usually full bars rather than just one or none. This was even after my install froze 4 consecutive times and needed a call to apple support to work out. If you hadnt tried a full erase and install Id advise it.
ieani said:
I didn't think the problems discussed here had anything to do with 4/4 or 1/4 bars, I have 4/4 bars all the time, never anything less. My problem has to do with the fluctuating DELAY as observed by the PINGs to my own router. They are still fluctuating.
Yep this is about fluctuating pings and poor download performance. Not signal strength. I jsut did a clean install of my os. Still same problems persist.
I've just got a 12 inch powerbook MRU mate - i will run some tests later after i install tiger onto the PB.
I still can't believe that there isn't a freaking fix for this yet.
I still can't believe that there isn't a freaking fix for this yet.
MacRumorUser said:
My download was slower than dial-up and my ping didnt fluctuate but my wireless indicator appeared animated with how much it was going up and down. And when did this change from general airport issues as topic suggests to specific ping issues?
Well, I have a question that's slightly on-topic.
I have an Intel Mac Mini, and my DSL provider is doing some upgrades so sometimes my internet goes down. I don't disconnect my Mini from the DSL connection. However, there is a wireless router upstairs connected to cable internet. I then select the wireless network and try and use it, but I have YET to ever get it working. It says it's connected and the bars fluctuate slightly, but I try and load up a web page and it says I am not connected to the internet. What the heck am I doing wrong?
I have an Intel Mac Mini, and my DSL provider is doing some upgrades so sometimes my internet goes down. I don't disconnect my Mini from the DSL connection. However, there is a wireless router upstairs connected to cable internet. I then select the wireless network and try and use it, but I have YET to ever get it working. It says it's connected and the bars fluctuate slightly, but I try and load up a web page and it says I am not connected to the internet. What the heck am I doing wrong?
Have you guys tried setting your base stations to use a different channel, in case you're getting intermittent signal interference?
ieani said:
Well since I started the thread all along
It changed in page 2 when I started noticing problems with specific firmware versions. However along the way people have posted regarding airport signal strength which although a pain isn't as bad as what were trying to concentrate on and what Apple Ireland Support are watching this thread for.
If your new to this thread. Firsty post you firmware version. Can be found in system profiler and what mac you are using. Also post network ping results. An explanation of how to do this can be found page 2 or three.....
..........
Bean's I know what you mean matey. I'm using a 12" ibook for most casual browsing simply because it performs better than the imac...
Come on apple release 10.4.6 tommorow!!
Although how are we all going to feel if it isn't corrected
MacRumorUser said:Well since I started the thread all along
It changed in page 2 when I started noticing problems with specific firmware versions. However along the way people have posted regarding airport signal strength which although a pain isn't as bad as what were trying to concentrate on and what Apple Ireland Support are watching this thread for.
If your new to this thread. Firsty post you firmware version. Can be found in system profiler and what mac you are using. Also post network ping results. An explanation of how to do this can be found page 2 or three.....
..........
Bean's I know what you mean matey. I'm using a 12" ibook for most casual browsing simply because it performs better than the imac...
Come on apple release 10.4.6 tommorow!!
Oh ok. Well i ran all the tests and everything was normal for me if you still want the literal ping results I can run them again. Heres my card info:
AirPort Card Information:
Wireless Card Type: AirPort Extreme (0x168C, 0x86)
Wireless Card Locale: USA
Wireless Card Firmware Version: 0.1.12
Current Wireless Network: default
Wireless Channel: 11
ping ping ping
ping
ping
is anyone out there?
ping
Well just an update to my Airport problems with the MacBook Pro. I posted a few messages here about how the laptop kept dropping off the network randomly and frequently. Well, I took it in for service. They replaced the Airport card. Works perfectly now, no problems at all. The funny thing is that the new card is the same firmware revision... it's possible the driver was updated too, but I have no idea. So I would recommend anyone who is having problems to use their warranty and get the machine repaired at an authorized service center. Worked great for me.
Regards,
snak-pak
ping
ping
is anyone out there?
ping
Well just an update to my Airport problems with the MacBook Pro. I posted a few messages here about how the laptop kept dropping off the network randomly and frequently. Well, I took it in for service. They replaced the Airport card. Works perfectly now, no problems at all. The funny thing is that the new card is the same firmware revision... it's possible the driver was updated too, but I have no idea. So I would recommend anyone who is having problems to use their warranty and get the machine repaired at an authorized service center. Worked great for me.
Regards,
snak-pak
Usually the driver for the cards is the firmware revision.
ieani - 1.12 is not the majorly bad firmware so you ouldnt be having as many problems if any compared to people with 101.3 (the badun)
I'm crossing my fingers 10.4.6 hits us next week and solves all this. If it doesnt solve the problem - I'm affraid my old intel imac'cy will be going back for replacement/repair......
ieani - 1.12 is not the majorly bad firmware so you ouldnt be having as many problems if any compared to people with 101.3 (the badun)
I'm crossing my fingers 10.4.6 hits us next week and solves all this. If it doesnt solve the problem - I'm affraid my old intel imac'cy will be going back for replacement/repair......
Keep your shirt on!
Dear everybody, I really hate to say this, but:
I have a Mini Core Solo, completely stock. Bluetooth reception on the thing is crappy at best... even one of those "100 feet range" BT dongles didn't really help, I almost need to place my apple BT keyboard/mouse on top of the Mini!
But, on the wifi topic, I have just erased and reinstalled OS X on it and to resolve my wifi problems (connection is slow, and very low/jumpy bars, jumpy pings, i.e. 2-3ms to 3-400ms between mini and powerbook, but works, does NOT disconnect. It also looses network after restart, though not after sleeping.). Reinstall did nothing.
I also noted that I have firmware 0.1.16 (after reinstall, didn't check before reinstall)
My Hi-res 15" PB is rock-solid.
On a side note, sharing my (wi-fi) internet over the mini through ethernet connected to a Airport Express produced excellent file/internet-transfer between my mini and pb (note: internet on my mini works at approximately 80-90% capacity)
Wireless Card Type: AirPort Extreme (0x168C, 0x86)
Wireless Card Locale: Worldwide
Wireless Card Firmware Version; 0.1.16
Wireless Channel: 7
I sencerely hope that this helps in some way!
Regards, Malte Eriksen
Dear everybody, I really hate to say this, but:
I have a Mini Core Solo, completely stock. Bluetooth reception on the thing is crappy at best... even one of those "100 feet range" BT dongles didn't really help, I almost need to place my apple BT keyboard/mouse on top of the Mini!
But, on the wifi topic, I have just erased and reinstalled OS X on it and to resolve my wifi problems (connection is slow, and very low/jumpy bars, jumpy pings, i.e. 2-3ms to 3-400ms between mini and powerbook, but works, does NOT disconnect. It also looses network after restart, though not after sleeping.). Reinstall did nothing.
I also noted that I have firmware 0.1.16 (after reinstall, didn't check before reinstall)
My Hi-res 15" PB is rock-solid.
On a side note, sharing my (wi-fi) internet over the mini through ethernet connected to a Airport Express produced excellent file/internet-transfer between my mini and pb (note: internet on my mini works at approximately 80-90% capacity)
Wireless Card Type: AirPort Extreme (0x168C, 0x86)
Wireless Card Locale: Worldwide
Wireless Card Firmware Version; 0.1.16
Wireless Channel: 7
I sencerely hope that this helps in some way!
Regards, Malte Eriksen
Re: Keep your shirt on
I forgot to mention, there are no other wifi networks in a radius of 50 meters of my house. I do not the think there are any interference sourses inside my house (like cordless phones).
Regards, Malte Eriksen
P.S. the airport express solution works after restart, it kinda works as if the mini's internal wifi works as it's supposed to
I forgot to mention, there are no other wifi networks in a radius of 50 meters of my house. I do not the think there are any interference sourses inside my house (like cordless phones).
Regards, Malte Eriksen
P.S. the airport express solution works after restart, it kinda works as if the mini's internal wifi works as it's supposed to
One titbit of information posted on Macintouch reports that the BT/Airport module in the mini has two antenna slots but only one fo them is wired up in the two machines that this gentleman has seen. This was also confirmed by another reader. It seems to me that this could very well be the cause of the Intel Mini issues which are afflicting a huge number of people as it would explain the greater issues for those also using Bluetooth and it would also explain the variable nature of the problem for certain users who have interference from surrounding networks whilst other have acceptable connectivity because their minis are very close to their access points.
The question is whether this antenna is missing by design or simply a build error affecting a limited run of minis.
The question is whether this antenna is missing by design or simply a build error affecting a limited run of minis.
Hello, I've just written one post and lost it thanks to Airport cutting out (*sigh*).
I've got the same stall/drop of Airport connections on a 2GHz MBP. The problem happens on two wireless networks (work and home) and it's driving me nuts. I have a 12" PowerBook and it's not showing any of the symptoms on the same networks.
I have tried creating a Network Location of "Airport Only" which "By default, join: Automatic"s and I still get the same connection problems. I have also tried the "delayed_ack=0" bodge to no avail.
Symptoms:
1. Random & lengthy stalls in TCP/IP traffic whilst Airport shows 3 or 4 bars signal strength.
2. Loss of Airport connection (no bars, no network visible) and failure to automatically reconnect when network becomes visible again.
3. Failure to automatically join a known wireless network after resume-from-sleep
4. Varying performance
Wireless Router Hardware:
Work - Cisco (unknown model) wireless router - WEP encrypted.
Home - Generic (unbranded) wireless router - unencrpyted.
Apologies for the lack of detail here, there's no visible model numbers on either of them and they're not things I purchased myself. Coincidentally both on Channel 3 - have tried the home router on different channels but no remedy. As I say, my 12" PB can sustain 24 hours of download activity without interruption on my home network anyway...
Airport Firmware:
Wireless Card Type: AirPort Extreme (0x168C, 0x86)
Wireless Card Locale: Worldwide
Wireless Card Firmware Version: 0.1.12
Ping Trace:
The following is a trace to a friend's (very reliably) hosted server. It shows some numbers that I've never seen in the wild. By which, I mean, that they're rubbish, frustrating, and driving me mad.
64 bytes from 83.170.75.35: icmp_seq=507 ttl=54 time=29.109 ms
64 bytes from 83.170.75.35: icmp_seq=508 ttl=54 time=84.683 ms
64 bytes from 83.170.75.35: icmp_seq=509 ttl=54 time=25.631 ms
64 bytes from 83.170.75.35: icmp_seq=510 ttl=54 time=38.657 ms
64 bytes from 83.170.75.35: icmp_seq=511 ttl=54 time=30.955 ms
64 bytes from 83.170.75.35: icmp_seq=531 ttl=54 time=24884.305 ms
64 bytes from 83.170.75.35: icmp_seq=532 ttl=54 time=23884.145 ms
64 bytes from 83.170.75.35: icmp_seq=533 ttl=54 time=22884.264 ms
64 bytes from 83.170.75.35: icmp_seq=534 ttl=54 time=21884.384 ms
64 bytes from 83.170.75.35: icmp_seq=535 ttl=54 time=20884.564 ms
64 bytes from 83.170.75.35: icmp_seq=536 ttl=54 time=19936.482 ms
64 bytes from 83.170.75.35: icmp_seq=537 ttl=54 time=18936.425 ms
64 bytes from 83.170.75.35: icmp_seq=538 ttl=54 time=17936.659 ms
64 bytes from 83.170.75.35: icmp_seq=539 ttl=54 time=16936.802 ms
64 bytes from 83.170.75.35: icmp_seq=540 ttl=54 time=15936.984 ms
64 bytes from 83.170.75.35: icmp_seq=541 ttl=54 time=14937.073 ms
64 bytes from 83.170.75.35: icmp_seq=542 ttl=54 time=13937.240 ms
64 bytes from 83.170.75.35: icmp_seq=543 ttl=54 time=12937.448 ms
64 bytes from 83.170.75.35: icmp_seq=544 ttl=54 time=11937.569 ms
64 bytes from 83.170.75.35: icmp_seq=545 ttl=54 time=10937.746 ms
64 bytes from 83.170.75.35: icmp_seq=546 ttl=54 time=9994.065 ms
64 bytes from 83.170.75.35: icmp_seq=547 ttl=54 time=8994.001 ms
64 bytes from 83.170.75.35: icmp_seq=548 ttl=54 time=7994.067 ms
64 bytes from 83.170.75.35: icmp_seq=549 ttl=54 time=6994.251 ms
64 bytes from 83.170.75.35: icmp_seq=550 ttl=54 time=5994.376 ms
64 bytes from 83.170.75.35: icmp_seq=551 ttl=54 time=4994.494 ms
64 bytes from 83.170.75.35: icmp_seq=552 ttl=54 time=3994.601 ms
64 bytes from 83.170.75.35: icmp_seq=553 ttl=54 time=2994.705 ms
64 bytes from 83.170.75.35: icmp_seq=554 ttl=54 time=1994.905 ms
64 bytes from 83.170.75.35: icmp_seq=555 ttl=54 time=995.041 ms
64 bytes from 83.170.75.35: icmp_seq=556 ttl=54 time=34.202 ms
64 bytes from 83.170.75.35: icmp_seq=557 ttl=54 time=37.937 ms
64 bytes from 83.170.75.35: icmp_seq=558 ttl=54 time=26.787 ms
64 bytes from 83.170.75.35: icmp_seq=559 ttl=54 time=36.737 ms
...
580 packets transmitted, 300 packets received, 48% packet loss
round-trip min/avg/max/stddev = 22.115/1516.430/24884.305/4286.822 ms
I eagerly await the next software update. Other than this, I'm very happy with the MBP but it is beginning to get very frustrating when I keep losing network connections to everything.
I've got the same stall/drop of Airport connections on a 2GHz MBP. The problem happens on two wireless networks (work and home) and it's driving me nuts. I have a 12" PowerBook and it's not showing any of the symptoms on the same networks.
I have tried creating a Network Location of "Airport Only" which "By default, join: Automatic"s and I still get the same connection problems. I have also tried the "delayed_ack=0" bodge to no avail.
Symptoms:
1. Random & lengthy stalls in TCP/IP traffic whilst Airport shows 3 or 4 bars signal strength.
2. Loss of Airport connection (no bars, no network visible) and failure to automatically reconnect when network becomes visible again.
3. Failure to automatically join a known wireless network after resume-from-sleep
4. Varying performance
Wireless Router Hardware:
Work - Cisco (unknown model) wireless router - WEP encrypted.
Home - Generic (unbranded) wireless router - unencrpyted.
Apologies for the lack of detail here, there's no visible model numbers on either of them and they're not things I purchased myself. Coincidentally both on Channel 3 - have tried the home router on different channels but no remedy. As I say, my 12" PB can sustain 24 hours of download activity without interruption on my home network anyway...
Airport Firmware:
Wireless Card Type: AirPort Extreme (0x168C, 0x86)
Wireless Card Locale: Worldwide
Wireless Card Firmware Version: 0.1.12
Ping Trace:
The following is a trace to a friend's (very reliably) hosted server. It shows some numbers that I've never seen in the wild. By which, I mean, that they're rubbish, frustrating, and driving me mad.
64 bytes from 83.170.75.35: icmp_seq=507 ttl=54 time=29.109 ms
64 bytes from 83.170.75.35: icmp_seq=508 ttl=54 time=84.683 ms
64 bytes from 83.170.75.35: icmp_seq=509 ttl=54 time=25.631 ms
64 bytes from 83.170.75.35: icmp_seq=510 ttl=54 time=38.657 ms
64 bytes from 83.170.75.35: icmp_seq=511 ttl=54 time=30.955 ms
64 bytes from 83.170.75.35: icmp_seq=531 ttl=54 time=24884.305 ms
64 bytes from 83.170.75.35: icmp_seq=532 ttl=54 time=23884.145 ms
64 bytes from 83.170.75.35: icmp_seq=533 ttl=54 time=22884.264 ms
64 bytes from 83.170.75.35: icmp_seq=534 ttl=54 time=21884.384 ms
64 bytes from 83.170.75.35: icmp_seq=535 ttl=54 time=20884.564 ms
64 bytes from 83.170.75.35: icmp_seq=536 ttl=54 time=19936.482 ms
64 bytes from 83.170.75.35: icmp_seq=537 ttl=54 time=18936.425 ms
64 bytes from 83.170.75.35: icmp_seq=538 ttl=54 time=17936.659 ms
64 bytes from 83.170.75.35: icmp_seq=539 ttl=54 time=16936.802 ms
64 bytes from 83.170.75.35: icmp_seq=540 ttl=54 time=15936.984 ms
64 bytes from 83.170.75.35: icmp_seq=541 ttl=54 time=14937.073 ms
64 bytes from 83.170.75.35: icmp_seq=542 ttl=54 time=13937.240 ms
64 bytes from 83.170.75.35: icmp_seq=543 ttl=54 time=12937.448 ms
64 bytes from 83.170.75.35: icmp_seq=544 ttl=54 time=11937.569 ms
64 bytes from 83.170.75.35: icmp_seq=545 ttl=54 time=10937.746 ms
64 bytes from 83.170.75.35: icmp_seq=546 ttl=54 time=9994.065 ms
64 bytes from 83.170.75.35: icmp_seq=547 ttl=54 time=8994.001 ms
64 bytes from 83.170.75.35: icmp_seq=548 ttl=54 time=7994.067 ms
64 bytes from 83.170.75.35: icmp_seq=549 ttl=54 time=6994.251 ms
64 bytes from 83.170.75.35: icmp_seq=550 ttl=54 time=5994.376 ms
64 bytes from 83.170.75.35: icmp_seq=551 ttl=54 time=4994.494 ms
64 bytes from 83.170.75.35: icmp_seq=552 ttl=54 time=3994.601 ms
64 bytes from 83.170.75.35: icmp_seq=553 ttl=54 time=2994.705 ms
64 bytes from 83.170.75.35: icmp_seq=554 ttl=54 time=1994.905 ms
64 bytes from 83.170.75.35: icmp_seq=555 ttl=54 time=995.041 ms
64 bytes from 83.170.75.35: icmp_seq=556 ttl=54 time=34.202 ms
64 bytes from 83.170.75.35: icmp_seq=557 ttl=54 time=37.937 ms
64 bytes from 83.170.75.35: icmp_seq=558 ttl=54 time=26.787 ms
64 bytes from 83.170.75.35: icmp_seq=559 ttl=54 time=36.737 ms
...
580 packets transmitted, 300 packets received, 48% packet loss
round-trip min/avg/max/stddev = 22.115/1516.430/24884.305/4286.822 ms
I eagerly await the next software update. Other than this, I'm very happy with the MBP but it is beginning to get very frustrating when I keep losing network connections to everything.
MacRumorUser said:Usually the driver for the cards is the firmware revision.
ieani - 1.12 is not the majorly bad firmware so you ouldnt be having as many problems if any compared to people with 101.3 (the badun)
I'm crossing my fingers 10.4.6 hits us next week and solves all this. If it doesnt solve the problem - I'm affraid my old intel imac'cy will be going back for replacement/repair......
So does 10.4.6 fix it?
Shaddow825 said:
YES!
My intel mini is getting better reception than I have ever seen! Before I would get 20% or less from just 20 feet away and frequent dropouts. Now I am at 60% to 80%, on par with my Powermac G5 and iBook! Not a single dropout yet since 10.4.6 has been released!
Installed 10.4.6 and I'm getting normal pings now, looks like it did the trick.
Firmware reads as 103.2 (3.120.28.3)
Firmware reads as 103.2 (3.120.28.3)
