|
Replies
:
54
-
Pages
:
4
[
1
2
3
4
|
Next
]
-
Last Post
:
Jan 7, 2009 1:12 AM
by: dnovelta
|
|
|
Posts:
16
Registered:
Aug 24, 2006
|
|
|
|
Poor wireless performance
Posted:
Oct 23, 2008 3:19 PM
|
|
|
I've noticed this new MBP I got earlier this week (2.53Ghz) seems to have trouble with its wireless networking. It struggled to hold a wireless AP as I walked around work (we have a large distributed AP, I could see at least 6 APs at any time). Just now I'm connected to my home wireless and I'm getting terrible ping response times just trying to ping the AP... Here is the output of the ping:
PING 10.0.0.1 (10.0.0.1): 56 data bytes
64 bytes from 10.0.0.1: icmp_seq=0 ttl=64 time=45.089 ms
64 bytes from 10.0.0.1: icmp_seq=1 ttl=64 time=43.146 ms
64 bytes from 10.0.0.1: icmp_seq=2 ttl=64 time=1.519 ms
64 bytes from 10.0.0.1: icmp_seq=3 ttl=64 time=1.208 ms
64 bytes from 10.0.0.1: icmp_seq=4 ttl=64 time=1.098 ms
64 bytes from 10.0.0.1: icmp_seq=5 ttl=64 time=1.159 ms
64 bytes from 10.0.0.1: icmp_seq=6 ttl=64 time=1.203 ms
64 bytes from 10.0.0.1: icmp_seq=7 ttl=64 time=4.133 ms
64 bytes from 10.0.0.1: icmp_seq=8 ttl=64 time=4.139 ms
64 bytes from 10.0.0.1: icmp_seq=9 ttl=64 time=3675.515 ms
64 bytes from 10.0.0.1: icmp_seq=10 ttl=64 time=10323.391 ms
64 bytes from 10.0.0.1: icmp_seq=11 ttl=64 time=12288.428 ms
64 bytes from 10.0.0.1: icmp_seq=12 ttl=64 time=11296.786 ms
64 bytes from 10.0.0.1: icmp_seq=13 ttl=64 time=18303.294 ms
64 bytes from 10.0.0.1: icmp_seq=14 ttl=64 time=18368.191 ms
64 bytes from 10.0.0.1: icmp_seq=17 ttl=64 time=25133.894 ms
64 bytes from 10.0.0.1: icmp_seq=18 ttl=64 time=24134.535 ms
64 bytes from 10.0.0.1: icmp_seq=19 ttl=64 time=23141.567 ms
64 bytes from 10.0.0.1: icmp_seq=20 ttl=64 time=22142.081 ms
64 bytes from 10.0.0.1: icmp_seq=21 ttl=64 time=21142.780 ms
64 bytes from 10.0.0.1: icmp_seq=22 ttl=64 time=20146.645 ms
64 bytes from 10.0.0.1: icmp_seq=25 ttl=64 time=17238.295 ms
64 bytes from 10.0.0.1: icmp_seq=27 ttl=64 time=15497.042 ms
64 bytes from 10.0.0.1: icmp_seq=28 ttl=64 time=14497.898 ms
64 bytes from 10.0.0.1: icmp_seq=29 ttl=64 time=14348.350 ms
64 bytes from 10.0.0.1: icmp_seq=30 ttl=64 time=13349.217 ms
64 bytes from 10.0.0.1: icmp_seq=31 ttl=64 time=12416.782 ms
64 bytes from 10.0.0.1: icmp_seq=32 ttl=64 time=11425.327 ms
64 bytes from 10.0.0.1: icmp_seq=33 ttl=64 time=10444.753 ms
64 bytes from 10.0.0.1: icmp_seq=34 ttl=64 time=9482.520 ms
64 bytes from 10.0.0.1: icmp_seq=35 ttl=64 time=8483.348 ms
64 bytes from 10.0.0.1: icmp_seq=36 ttl=64 time=8052.900 ms
^C
-
-
- 10.0.0.1 ping statistics ---
49 packets transmitted, 32 packets received, 34% packet loss
round-trip min/avg/max/stddev = 1.098/10794.882/25133.894/8267.383 ms
I got my old Powerbook G4 out and it gets an average ping of ~3ms. When I plug in to the network I can ping the router at ~0.7ms.
Will this be fixed by the Airport Extreme patch that Apple pulled a few days ago? Or is this another issue entirely?
Any help is greatly appreciate! Thanks!
MBP 2.53 Late 2008
Mac OS X (10.5.5)
4GB RAM
|
|
Posts:
2
From:
USA
Registered:
Oct 26, 2008
|
|
|
|
Re: Poor wireless performance
Posted:
Oct 26, 2008 8:32 AM
in response to: X9
|
|
|
I'm sorry I don't have a solution, but I wanted to post as I have a (possibly related?) issue.
My new MBP has no problem connecting to Wi-Fi at home, and seems speedy enough, but for the life of me I can only get a connection at school in a couple of very small areas of campus... even though my old HP notebook could get and hold a connection in every classroom. Occasionally, I can "see" the Wi-Fi network appear as available, but I can never connect, and then the network disappears.
Is the Wi-Fi signal on these machines really THAT weak? I've heard complaints, often attributed to the aluminum casing, but I cannot believe that these machines are completely incapable of receiving "marginal" signals that cause other machines no trouble at all.
BTW, I installed the latest update released a couple days ago, and nothing changed.
Anyone have any ideas?
MacBook Pro 15" 2.53Ghz (Late 2008)
Mac OS X (10.5.5)
|
|
Posts:
16
Registered:
Aug 24, 2006
|
|
|
|
Re: Poor wireless performance
Posted:
Oct 27, 2008 9:20 AM
in response to: X9
|
|
|
I don't experience this very often, but it just happened now while at a completely different location. Doing 25 pings to a wired machine in the same network gives me about 15 pings above 100ms, and even some around 2000-3000ms!! The last 10 pings seem to taper off to around 3-5ms, which I would expect to be more normal.
I did this because I noticed while working on a sshfs mount (hosted on the same machine I'm pinging) that my saves took a lot longer than they should.
What is going on with these MBPs?
I never had any trouble doing this with my older Powerbook.
MBP 2.53 Late 2008
Mac OS X (10.5.5)
4GB RAM
|
|
Posts:
16
Registered:
Aug 24, 2006
|
|
|
|
Re: Poor wireless performance
Posted:
Oct 27, 2008 9:36 AM
in response to: X9
|
|
|
Here is a recent attempt at pinging a local server 100 times. I apologize for the length of the message but I think it illustrates a bit better what is going on. I've removed the IP address since it is accessible to the public also.
It seems that no packets are getting lost, but they're being held up somewhere. My guess is either the MBP itself or the wireless AP point, since this exhibits the same behavior as when I attempted to ping my own wireless AP in the first post.
If anyone has suggestions for displaying this data better than in the body of this post please let me know. I don't want people to think I'm post spamming.
PING <hostname removed> (<IP Removed>): 56 data bytes
64 bytes from <IP Removed>: icmp_seq=0 ttl=60 time=39290.763 ms
64 bytes from <IP Removed>: icmp_seq=1 ttl=60 time=38299.150 ms
64 bytes from <IP Removed>: icmp_seq=2 ttl=60 time=37598.983 ms
64 bytes from <IP Removed>: icmp_seq=3 ttl=60 time=36605.864 ms
64 bytes from <IP Removed>: icmp_seq=4 ttl=60 time=35700.392 ms
64 bytes from <IP Removed>: icmp_seq=5 ttl=60 time=34700.526 ms
64 bytes from <IP Removed>: icmp_seq=6 ttl=60 time=33816.754 ms
64 bytes from <IP Removed>: icmp_seq=7 ttl=60 time=32822.383 ms
64 bytes from <IP Removed>: icmp_seq=8 ttl=60 time=32029.424 ms
64 bytes from <IP Removed>: icmp_seq=9 ttl=60 time=31029.615 ms
64 bytes from <IP Removed>: icmp_seq=10 ttl=60 time=30036.472 ms
64 bytes from <IP Removed>: icmp_seq=11 ttl=60 time=30543.678 ms
64 bytes from <IP Removed>: icmp_seq=12 ttl=60 time=29547.292 ms
64 bytes from <IP Removed>: icmp_seq=13 ttl=60 time=28648.814 ms
64 bytes from <IP Removed>: icmp_seq=14 ttl=60 time=29101.320 ms
64 bytes from <IP Removed>: icmp_seq=15 ttl=60 time=28107.391 ms
64 bytes from <IP Removed>: icmp_seq=16 ttl=60 time=27117.262 ms
64 bytes from <IP Removed>: icmp_seq=17 ttl=60 time=26183.337 ms
64 bytes from <IP Removed>: icmp_seq=18 ttl=60 time=25487.851 ms
64 bytes from <IP Removed>: icmp_seq=19 ttl=60 time=25734.730 ms
64 bytes from <IP Removed>: icmp_seq=20 ttl=60 time=25029.655 ms
64 bytes from <IP Removed>: icmp_seq=21 ttl=60 time=24032.947 ms
64 bytes from <IP Removed>: icmp_seq=22 ttl=60 time=23234.200 ms
64 bytes from <IP Removed>: icmp_seq=23 ttl=60 time=22994.779 ms
64 bytes from <IP Removed>: icmp_seq=24 ttl=60 time=21995.516 ms
64 bytes from <IP Removed>: icmp_seq=25 ttl=60 time=21151.589 ms
64 bytes from <IP Removed>: icmp_seq=26 ttl=60 time=20152.117 ms
64 bytes from <IP Removed>: icmp_seq=27 ttl=60 time=19152.906 ms
64 bytes from <IP Removed>: icmp_seq=28 ttl=60 time=18254.306 ms
64 bytes from <IP Removed>: icmp_seq=29 ttl=60 time=17460.629 ms
64 bytes from <IP Removed>: icmp_seq=30 ttl=60 time=16464.462 ms
64 bytes from <IP Removed>: icmp_seq=31 ttl=60 time=15559.672 ms
64 bytes from <IP Removed>: icmp_seq=32 ttl=60 time=14561.928 ms
64 bytes from <IP Removed>: icmp_seq=33 ttl=60 time=13562.590 ms
64 bytes from <IP Removed>: icmp_seq=34 ttl=60 time=13182.303 ms
64 bytes from <IP Removed>: icmp_seq=35 ttl=60 time=12188.830 ms
64 bytes from <IP Removed>: icmp_seq=36 ttl=60 time=11793.440 ms
64 bytes from <IP Removed>: icmp_seq=37 ttl=60 time=10793.492 ms
64 bytes from <IP Removed>: icmp_seq=38 ttl=60 time=11424.939 ms
64 bytes from <IP Removed>: icmp_seq=39 ttl=60 time=10432.036 ms
64 bytes from <IP Removed>: icmp_seq=40 ttl=60 time=9526.646 ms
64 bytes from <IP Removed>: icmp_seq=41 ttl=60 time=9348.804 ms
64 bytes from <IP Removed>: icmp_seq=42 ttl=60 time=8350.194 ms
64 bytes from <IP Removed>: icmp_seq=43 ttl=60 time=7355.927 ms
64 bytes from <IP Removed>: icmp_seq=44 ttl=60 time=6357.874 ms
64 bytes from <IP Removed>: icmp_seq=45 ttl=60 time=5358.626 ms
64 bytes from <IP Removed>: icmp_seq=46 ttl=60 time=5896.463 ms
64 bytes from <IP Removed>: icmp_seq=47 ttl=60 time=7746.067 ms
64 bytes from <IP Removed>: icmp_seq=48 ttl=60 time=7055.860 ms
64 bytes from <IP Removed>: icmp_seq=49 ttl=60 time=6470.610 ms
64 bytes from <IP Removed>: icmp_seq=50 ttl=60 time=5772.405 ms
64 bytes from <IP Removed>: icmp_seq=51 ttl=60 time=6510.693 ms
64 bytes from <IP Removed>: icmp_seq=52 ttl=60 time=5618.897 ms
64 bytes from <IP Removed>: icmp_seq=53 ttl=60 time=5227.307 ms
64 bytes from <IP Removed>: icmp_seq=54 ttl=60 time=4536.839 ms
64 bytes from <IP Removed>: icmp_seq=55 ttl=60 time=3537.574 ms
64 bytes from <IP Removed>: icmp_seq=56 ttl=60 time=2743.677 ms
64 bytes from <IP Removed>: icmp_seq=57 ttl=60 time=1744.388 ms
64 bytes from <IP Removed>: icmp_seq=58 ttl=60 time=842.062 ms
64 bytes from <IP Removed>: icmp_seq=59 ttl=60 time=660.471 ms
64 bytes from <IP Removed>: icmp_seq=60 ttl=60 time=4767.478 ms
64 bytes from <IP Removed>: icmp_seq=61 ttl=60 time=3767.584 ms
64 bytes from <IP Removed>: icmp_seq=62 ttl=60 time=2798.865 ms
64 bytes from <IP Removed>: icmp_seq=63 ttl=60 time=3219.783 ms
64 bytes from <IP Removed>: icmp_seq=64 ttl=60 time=2424.818 ms
64 bytes from <IP Removed>: icmp_seq=65 ttl=60 time=1434.916 ms
64 bytes from <IP Removed>: icmp_seq=66 ttl=60 time=479.252 ms
64 bytes from <IP Removed>: icmp_seq=67 ttl=60 time=130.559 ms
64 bytes from <IP Removed>: icmp_seq=68 ttl=60 time=7745.535 ms
64 bytes from <IP Removed>: icmp_seq=69 ttl=60 time=6745.706 ms
64 bytes from <IP Removed>: icmp_seq=70 ttl=60 time=5749.176 ms
64 bytes from <IP Removed>: icmp_seq=71 ttl=60 time=4749.193 ms
64 bytes from <IP Removed>: icmp_seq=72 ttl=60 time=3749.472 ms
64 bytes from <IP Removed>: icmp_seq=73 ttl=60 time=2749.793 ms
64 bytes from <IP Removed>: icmp_seq=74 ttl=60 time=1750.163 ms
64 bytes from <IP Removed>: icmp_seq=75 ttl=60 time=750.606 ms
64 bytes from <IP Removed>: icmp_seq=76 ttl=60 time=3.653 ms
64 bytes from <IP Removed>: icmp_seq=77 ttl=60 time=4.323 ms
64 bytes from <IP Removed>: icmp_seq=78 ttl=60 time=4.046 ms
64 bytes from <IP Removed>: icmp_seq=79 ttl=60 time=5.577 ms
64 bytes from <IP Removed>: icmp_seq=80 ttl=60 time=16.934 ms
64 bytes from <IP Removed>: icmp_seq=81 ttl=60 time=2.438 ms
64 bytes from <IP Removed>: icmp_seq=82 ttl=60 time=3.994 ms
64 bytes from <IP Removed>: icmp_seq=83 ttl=60 time=4.089 ms
64 bytes from <IP Removed>: icmp_seq=84 ttl=60 time=2.850 ms
64 bytes from <IP Removed>: icmp_seq=85 ttl=60 time=2.052 ms
64 bytes from <IP Removed>: icmp_seq=86 ttl=60 time=4.002 ms
64 bytes from <IP Removed>: icmp_seq=87 ttl=60 time=3.965 ms
64 bytes from <IP Removed>: icmp_seq=88 ttl=60 time=3.965 ms
64 bytes from <IP Removed>: icmp_seq=89 ttl=60 time=4.217 ms
64 bytes from <IP Removed>: icmp_seq=90 ttl=60 time=1.756 ms
64 bytes from <IP Removed>: icmp_seq=91 ttl=60 time=2.458 ms
64 bytes from <IP Removed>: icmp_seq=92 ttl=60 time=2.828 ms
64 bytes from <IP Removed>: icmp_seq=93 ttl=60 time=4.263 ms
64 bytes from <IP Removed>: icmp_seq=94 ttl=60 time=1.917 ms
64 bytes from <IP Removed>: icmp_seq=95 ttl=60 time=1.836 ms
64 bytes from <IP Removed>: icmp_seq=96 ttl=60 time=4.045 ms
64 bytes from <IP Removed>: icmp_seq=97 ttl=60 time=2.105 ms
64 bytes from <IP Removed>: icmp_seq=98 ttl=60 time=1.882 ms
64 bytes from <IP Removed>: icmp_seq=99 ttl=60 time=4.047 ms
64 bytes from <IP Removed>: icmp_seq=100 ttl=60 time=6.709 ms
^C
-
-
- <hostname removed> ping statistics ---
101 packets transmitted, 101 packets received, 0% packet loss
round-trip min/avg/max/stddev = 1.756/11283.154/39290.763/12113.675 ms
MBP 2.53 Late 2008
Mac OS X (10.5.5)
4GB RAM
|
|
Posts:
31
From:
Virginia
Registered:
Jun 21, 2008
|
|
|
|
Re: Poor wireless performance
Posted:
Oct 27, 2008 9:39 AM
in response to: X9
|
|
|
You may want to take it back to talk to a genius about a replacement -- my new 2.4 MBP has solid wi-fi connectivity (as least as good as my wife's Dell laptop).
Scratch-built
4GHz E8400
|
|
Posts:
16
Registered:
Aug 24, 2006
|
|
|
|
Re: Poor wireless performance
Posted:
Oct 27, 2008 9:47 AM
in response to: MHN
|
|
|
I was afraid of that. I just got this one the way I like it and there's no genius bars within 3 and a half hours of here  . Maybe I'll give the Applecare people a call and see what they think.
Thanks for your input
MBP 2.53 Late 2008
Mac OS X (10.5.5)
4GB RAM
|
|
Posts:
15
From:
San Francisco
Registered:
Jan 4, 2006
|
|
|
Posts:
16
Registered:
Aug 24, 2006
|
|
|
|
Re: Poor wireless performance
Posted:
Oct 28, 2008 5:37 AM
in response to: ayn
|
|
|
Thanks for the tip. However I don't have this widget installed. I called AppleCare last night and they suggested I create a new network location. Since this is a very intermittent issue I'm going to see if this fixes it over the next few days. If not I have a case number I'll reference when I call back.
Here's hoping the solution was this easy!
MBP 2.53 Late 2008
Mac OS X (10.5.5)
4GB RAM
|
|
Posts:
10
From:
Colorado
Registered:
Mar 8, 2008
|
|
|
Posts:
1
From:
USA, CA
Registered:
Oct 30, 2008
|
|
|
|
Re: Poor wireless performance
Posted:
Oct 30, 2008 11:29 AM
in response to: muddy07
|
|
|
I have the same exact thing happening to me if anyone finds a solution please post it since it is driving me crazy. I basically have perfect wireless connections outside of work but the moment I go to work the latency is unbearable. Everyone else around me is using the same Macbook Pro and they do not have a problem. So it is definitely not a access point problem.
Intel based MacBook Pro
Mac OS X (10.5.5)
|
|
Posts:
82
From:
Berkhamsted (UK)
Registered:
Sep 17, 2008
|
|
|
|
Re: Poor wireless performance
Posted:
Oct 30, 2008 4:04 PM
in response to: X9
|
|
|
I just wanted to share with you a workaround that has been working for me for the last week. I am not the first to find out about this.
Just install iStumbler http://www.istumbler.net/ and leave it running in the background. The application is a freeware wireless discovery tool.
Whatever iStumbler does under the bonnet, it keeps my wifi performance at acceptable levels. I can see that performance still is not ideal, but at least it does not drop, and I (almost) have no packet loss.
You can see wifi still suffering from the output of pinging my access point:
giaceccos-macbook-pro:~ giacecco$ ping -c 100 192.168.1.1
PING 192.168.1.1 (192.168.1.1): 56 data bytes
64 bytes from 192.168.1.1: icmp_seq=0 ttl=255 time=0.979 ms
64 bytes from 192.168.1.1: icmp_seq=1 ttl=255 time=0.991 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=255 time=5.101 ms <----
64 bytes from 192.168.1.1: icmp_seq=3 ttl=255 time=131.898 ms <----
64 bytes from 192.168.1.1: icmp_seq=4 ttl=255 time=0.560 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=255 time=1.109 ms
64 bytes from 192.168.1.1: icmp_seq=6 ttl=255 time=1.155 ms
64 bytes from 192.168.1.1: icmp_seq=7 ttl=255 time=8.160 ms <----
64 bytes from 192.168.1.1: icmp_seq=8 ttl=255 time=136.637 ms <----
64 bytes from 192.168.1.1: icmp_seq=9 ttl=255 time=0.750 ms
64 bytes from 192.168.1.1: icmp_seq=10 ttl=255 time=0.746 ms
64 bytes from 192.168.1.1: icmp_seq=11 ttl=255 time=1.223 ms
64 bytes from 192.168.1.1: icmp_seq=12 ttl=255 time=3.525 ms <----
64 bytes from 192.168.1.1: icmp_seq=13 ttl=255 time=128.260 ms <----
64 bytes from 192.168.1.1: icmp_seq=14 ttl=255 time=0.554 ms
...
Clearly there is a pattern there. If the Apple guys read this forum (and I do not mean the censors but the techies) they may find this very very useful.
Giacecco
MacBook Pro 17" 2.5Ghz Santa Rosa with the notoriuos wifi issue
Mac OS X (10.5.5)
|
|
Posts:
1,100
From:
Hamburg, Germany
Registered:
Oct 17, 2004
|
|
|
|
Re: Poor wireless performance
Posted:
Oct 30, 2008 4:18 PM
in response to: X9
|
|
|
I'm having the same intermittent problem, though not on my MacBook Pro (Late 2008), but on a MacBook Air (1st gen). This problem wasn't there from the beginning - it appeared sometime during the last 2-3 months. Disabling and re-enabling AirPort always fixes it, so I think it's a software issue.
Mac Pro 2.66; Cinema Display 23"; MacBook Pro 15" (Late 2008); iPod classic 160G
Mac OS X (10.5.5)
|
|
Posts:
10
From:
Colorado
Registered:
Mar 8, 2008
|
|
|
|
Re: Poor wireless performance
Posted:
Nov 1, 2008 11:27 PM
in response to: Tim Lorenzen
|
|
|
I finally found a solution that worked for me (suggested on one of the Intel iMac forums). My Time Capsule was set to "automatic" for channel selection. I kept switching channels on my router till I found one that worked. In my case it was channel 1 that did the trick.
Not only am I keeping a constant connection, but my connection speeds are much higher now.
Late 2008 Macbook Pro
Mac OS X (10.5.5)
|
|
Posts:
16
Registered:
Aug 24, 2006
|
|
|
|
Re: Poor wireless performance
Posted:
Nov 3, 2008 10:34 AM
in response to: muddy07
|
|
|
Well I'm still having troubles after doing a repair disk permissions, PRAM Reset, creating a new network location, and using only an open unsecured AP. It seems to happen the majority of the time while I'm at work, where they use distributed APs (lots of APs all with the same SSID).
Earlier today when I was last experiencing this terrible disconnect, I was seeing pings of 70+ seconds (thats right, seconds, not milliseconds) to the first network hop, and I was running a Wireless network scanner (KisMAC) which revealed I couldn't see ANY access points. When the interruption stopped, all the APs came back (usually I see about 20) and the network was accessible again.
I'm now running iStumbler in the background as suggested above to see if I can gather anymore information.
This is becoming severely irritating especially since my old Powerbook had no problem and a colleague that sits right next to me at work has one of the newer MacBooks (not Pro) and he isn't experiencing anything of the sorts.
I plan on calling Apple tonight.
Edit: Also turning my wireless off and back on didn't help. Once I logged out and logged back in however, it stopped the network interruption... for now.
Message was edited by: X9
MBP 2.53 Late 2008
Mac OS X (10.5.5)
4GB RAM
|
|
Posts:
14
From:
Indiana
Registered:
Sep 8, 2008
|
|
|
|
Re: Poor wireless performance
Posted:
Nov 4, 2008 2:46 PM
in response to: X9
|
|
|
I am having similar problems....can't keep a strong signal using my new MBP. The earlier version kept a constant 300 mbps until it died. When Apple replaced with this late '08 model I was psyched....until I saw the wireless performance. I am down to 81 - 162 mbps and very inconsistent at holding a level. No new changes to network or devices that could be interfering. Did all of the tricks listed in these thread. Talked to Apple today and after some troubleshooting, was left with the idea of corrupted software. Completely rebuilt the system and, of course, no change. Waiting for a friend to bring their new device over and compare side-by-side. Don't know if it is my machine or those whole aluminum casing thing. Any other ideas directed to enhance HARDWARE performance??
Macbook Pro Intel 2.6/4GB
Mac OS X (10.5.4)
|
|
|
