Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Won't connect reliably in library

My 2011 MBP works perfectly with an Airport at home, but it continually loses its connection in the library and I have to reconnect. Other machines I've used in the same library do not exhibit this behavior. Don't know what router the library uses.
 
Again. What defines a network issue versus not a network issue?

Network issue: All computers regardless of make/model are affected.
Not a network issue: Only specific computer is affect.



I'm wondering if you downgrade the wireless card from to the ones used in the 2010 model would fix things. After reading the support forms on apple.com it seems as if they used a newer model broadcom card for the 2011 models.
 
My 2011 MBP works perfectly with an Airport at home, but it continually loses its connection in the library and I have to reconnect. Other machines I've used in the same library do not exhibit this behavior. Don't know what router the library uses.

well if I may: that's probably an issue with your Mac + the router in question.
for example - I set up a WNDR2000 Netgear router at my brother's home. I set it up with WPA2 security and observed it for a couple of days. He continuously got disconnects from the network for unknown reasons. I switched his security to WEP and he hasn't had a problem for literally a year.

Last month I upgraded him to a WNDR3700 Netgear and secured it with WPA2 security. He hasn't had a problem yet.

Point is, some routers don't seem to work very well with certain security methods with Macs (or other computers for that matter).

If people are having trouble, they should, at minimum, try changing their security type to WEP to see if their stuff is more stable. They can also try buying a different, newer router. But based on my experience with multiple Macs over the last 4 or 5 years, they do not always play as expected with certain router models + encryption types. It's not a hardware issue, it's a software/communication issue between router and network card.
 
test while not doing any file transfers. That seems to fix the issue.

Some have speculated it's a with power saving.

I am glad someone else mentioned (power saving). I did not want to bring it up for fear of arguing with idiots.

Let me ask this question. What sense does it make to route full power to a network interface to send 56 bytes of data to your router.

That isn't to say something is wrong with cards or potentially just the kext. But give this a shot and tell me your results:

Code:
ping -s 1024 [router]

With a larger packet size you see much more consistent (and lower) ping results. Take it for what you will though.
 
I am glad someone else mentioned (power saving). I did not want to bring it up for fear of arguing with idiots.

Let me ask this question. What sense does it make to route full power to a network interface to send 56 bytes of data to your router.

That isn't to say something is wrong with cards or potentially just the kext. But give this a shot and tell me your results:

Code:
ping -s 1024 [router]

With a larger packet size you see much more consistent (and lower) ping results. Take it for what you will though.

Yes - power saving is mentioned in the Apple thread as well. To build on what you just pointed out if I ping -g -G say from 64 to 1024 - the values appear to stabilize between 222 and 232 byte payloads - adjusting in 20 byte increments - using -h.


ping -h 10 -g 64 -G 1024 192.168.1.1
PING 192.168.1.1 (192.168.1.1): (64 ... 1024) data bytes
72 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=174.808 ms
82 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=95.679 ms
92 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=17.586 ms
102 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=187.672 ms
112 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=167.606 ms
122 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=88.835 ms
132 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=10.183 ms
142 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=1.431 ms
152 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=160.243 ms
162 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=82.334 ms
172 bytes from 192.168.1.1: icmp_seq=10 ttl=64 time=3.762 ms
182 bytes from 192.168.1.1: icmp_seq=11 ttl=64 time=187.802 ms
192 bytes from 192.168.1.1: icmp_seq=12 ttl=64 time=3.898 ms
202 bytes from 192.168.1.1: icmp_seq=13 ttl=64 time=75.134 ms
212 bytes from 192.168.1.1: icmp_seq=14 ttl=64 time=187.683 ms
222 bytes from 192.168.1.1: icmp_seq=15 ttl=64 time=186.161 ms
232 bytes from 192.168.1.1: icmp_seq=16 ttl=64 time=4.639 ms
242 bytes from 192.168.1.1: icmp_seq=17 ttl=64 time=4.536 ms
252 bytes from 192.168.1.1: icmp_seq=18 ttl=64 time=4.142 ms
262 bytes from 192.168.1.1: icmp_seq=19 ttl=64 time=3.850 ms
272 bytes from 192.168.1.1: icmp_seq=20 ttl=64 time=4.001 ms
282 bytes from 192.168.1.1: icmp_seq=21 ttl=64 time=4.095 ms
292 bytes from 192.168.1.1: icmp_seq=22 ttl=64 time=4.019 ms
302 bytes from 192.168.1.1: icmp_seq=23 ttl=64 time=4.009 ms
312 bytes from 192.168.1.1: icmp_seq=24 ttl=64 time=4.231 ms
322 bytes from 192.168.1.1: icmp_seq=25 ttl=64 time=3.848 ms
 
Not completely consistent though. Need a real network expert to explain - as when I changed the increment to a single byte - the point at which it stabilized changed - while each other time it was consistent.


ping -h 1 -g 210 -G 1024 192.168.1.1
PING 192.168.1.1 (192.168.1.1): (210 ... 1024) data bytes
218 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=29.115 ms
219 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=258.136 ms
220 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=179.049 ms
221 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=100.882 ms
222 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=4.529 ms
223 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=251.057 ms
224 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=171.724 ms
225 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=93.203 ms
226 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=14.608 ms
227 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=3.910 ms
228 bytes from 192.168.1.1: icmp_seq=10 ttl=64 time=3.840 ms
229 bytes from 192.168.1.1: icmp_seq=11 ttl=64 time=4.055 ms
230 bytes from 192.168.1.1: icmp_seq=12 ttl=64 time=7.936 ms
231 bytes from 192.168.1.1: icmp_seq=13 ttl=64 time=235.921 ms
232 bytes from 192.168.1.1: icmp_seq=14 ttl=64 time=157.796 ms
233 bytes from 192.168.1.1: icmp_seq=15 ttl=64 time=3.897 ms
234 bytes from 192.168.1.1: icmp_seq=16 ttl=64 time=3.994 ms
235 bytes from 192.168.1.1: icmp_seq=17 ttl=64 time=3.959 ms
236 bytes from 192.168.1.1: icmp_seq=18 ttl=64 time=151.354 ms
237 bytes from 192.168.1.1: icmp_seq=19 ttl=64 time=71.395 ms
238 bytes from 192.168.1.1: icmp_seq=20 ttl=64 time=1.531 ms
239 bytes from 192.168.1.1: icmp_seq=21 ttl=64 time=221.061 ms
240 bytes from 192.168.1.1: icmp_seq=22 ttl=64 time=143.145 ms
241 bytes from 192.168.1.1: icmp_seq=23 ttl=64 time=64.027 ms
242 bytes from 192.168.1.1: icmp_seq=24 ttl=64 time=292.995 ms
243 bytes from 192.168.1.1: icmp_seq=25 ttl=64 time=213.885 ms
244 bytes from 192.168.1.1: icmp_seq=26 ttl=64 time=135.210 ms
245 bytes from 192.168.1.1: icmp_seq=27 ttl=64 time=56.633 ms
246 bytes from 192.168.1.1: icmp_seq=28 ttl=64 time=286.086 ms
247 bytes from 192.168.1.1: icmp_seq=29 ttl=64 time=206.774 ms
248 bytes from 192.168.1.1: icmp_seq=30 ttl=64 time=128.015 ms
249 bytes from 192.168.1.1: icmp_seq=31 ttl=64 time=4.037 ms
250 bytes from 192.168.1.1: icmp_seq=32 ttl=64 time=3.897 ms
251 bytes from 192.168.1.1: icmp_seq=33 ttl=64 time=4.025 ms
252 bytes from 192.168.1.1: icmp_seq=34 ttl=64 time=3.851 ms
253 bytes from 192.168.1.1: icmp_seq=35 ttl=64 time=4.136 ms
254 bytes from 192.168.1.1: icmp_seq=36 ttl=64 time=4.009 ms
255 bytes from 192.168.1.1: icmp_seq=37 ttl=64 time=4.127 ms
256 bytes from 192.168.1.1: icmp_seq=38 ttl=64 time=3.924 ms
257 bytes from 192.168.1.1: icmp_seq=39 ttl=64 time=4.023 ms
258 bytes from 192.168.1.1: icmp_seq=40 ttl=64 time=3.883 ms
259 bytes from 192.168.1.1: icmp_seq=41 ttl=64 time=4.123 ms
260 bytes from 192.168.1.1: icmp_seq=42 ttl=64 time=3.807 ms
261 bytes from 192.168.1.1: icmp_seq=43 ttl=64 time=4.133 ms
262 bytes from 192.168.1.1: icmp_seq=44 ttl=64 time=4.202 ms
263 bytes from 192.168.1.1: icmp_seq=45 ttl=64 time=4.664 ms
264 bytes from 192.168.1.1: icmp_seq=46 ttl=64 time=3.898 ms
265 bytes from 192.168.1.1: icmp_seq=47 ttl=64 time=4.151 ms
266 bytes from 192.168.1.1: icmp_seq=48 ttl=64 time=4.065 ms
267 bytes from 192.168.1.1: icmp_seq=49 ttl=64 time=3.985 ms
268 bytes from 192.168.1.1: icmp_seq=50 ttl=64 time=3.897 ms
269 bytes from 192.168.1.1: icmp_seq=51 ttl=64 time=4.340 ms
 
Do you think this issue may actually be dependent on the individual router and/or FW, which would explain the variation? I ask this as I am seeing all sorts of various speeds depending which network I am on, and the speed results are consistently the same ballpark on each respective network...
 
Do you think this issue may actually be dependent on the individual router and/or FW, which would explain the variation? I ask this as I am seeing all sorts of various speeds depending which network I am on, and the speed results are consistently the same ballpark on each respective network...

I stick to what I said. Certain routers just don't play nice with the Apple computers. I don't think it's security, I think it's just how the router transmits that the Apple Airport cards just don't care for. Occam's Razor.

Fact: if I hook up my Belkin N+ only, with the same connection parameters I've got on my Airport Extreme right now, the pings will be erratic and the transfer rates horrible. In fact, if I hook up any other router except the Apple branded ones, I will see terrible performance. Don't know why, and don't care really.

Just to verify, I will check with my Samsung LTE hotspot sometime this coming week. I'm 99% certain I will see the erratic pings some of you are seeing.
 
I stick to what I said. Certain routers just don't play nice with the Apple computers. I don't think it's security, I think it's just how the router transmits that the Apple Airport cards just don't care for. Occam's Razor.

Fact: if I hook up my Belkin N+ only, with the same connection parameters I've got on my Airport Extreme right now, the pings will be erratic and the transfer rates horrible. In fact, if I hook up any other router except the Apple branded ones, I will see terrible performance. Don't know why, and don't care really.

Just to verify, I will check with my Samsung LTE hotspot sometime this coming week. I'm 99% certain I will see the erratic pings some of you are seeing.

You must be right, as certain routers result in erratic performance. I just may have never noticed it until it was pointed out because most of the places I am at have a 10-40ms ping w/ a download speed of at least 15m and upload 3.

Another potential reason that this issue is being noted may be because:
1) Apples are common in education
2) Wireless internet has become more common in education
3) Colleges are accepting more people now than before, meaning that more people are on the same system
4) The infrastructure for wireless internet at colleges has not seemed to have kept up with the commonality of wireless internet, as well as cheap priced laptops (and dirt cheap notebooks) all offering wireless internet
5) Wireless internet systems at most colleges are overwhelmed with a gazillion users
6) Internet runs slow during peak usage time, which can be easy to be seen as an issue, especially if the computer is new. At the 3 colleges I am commonly at, 2 have this issue to a very severe degree, and 1 has just completely changed their entire wireless network due to this issue
 
I stick to what I said. Certain routers just don't play nice with the Apple computers. I don't think it's security, I think it's just how the router transmits that the Apple Airport cards just don't care for. Occam's Razor.

Fact: if I hook up my Belkin N+ only, with the same connection parameters I've got on my Airport Extreme right now, the pings will be erratic and the transfer rates horrible. In fact, if I hook up any other router except the Apple branded ones, I will see terrible performance. Don't know why, and don't care really.

Just to verify, I will check with my Samsung LTE hotspot sometime this coming week. I'm 99% certain I will see the erratic pings some of you are seeing.
glad someone is saying what I've been trying to say.

it's likely an issue with the routers and your Macs, guys.
 
Wirelessly posted (Mozilla/5.0 (iPhone; U; CPU iPhone OS 4_3_2 like Mac OS X; en-us) AppleWebKit/533.17.9 (KHTML, like Gecko) Version/5.0.2 Mobile/8H7 Safari/6533.18.5)

adrian1480 said:
I stick to what I said. Certain routers just don't play nice with the Apple computers. I don't think it's security, I think it's just how the router transmits that the Apple Airport cards just don't care for. Occam's Razor.

Fact: if I hook up my Belkin N+ only, with the same connection parameters I've got on my Airport Extreme right now, the pings will be erratic and the transfer rates horrible. In fact, if I hook up any other router except the Apple branded ones, I will see terrible performance. Don't know why, and don't care really.

Just to verify, I will check with my Samsung LTE hotspot sometime this coming week. I'm 99% certain I will see the erratic pings some of you are seeing.
glad someone is saying what I've been trying to say.

it's likely an issue with the routers and your Macs, guys.

It's obviously an issue with either the router or the Mac. What else could it be? My problem is with a current AEBS and a new MBP. Since the AEBS has been flawless with a dozen or so devices and computers, my money is on the MBP side. Either way, Apple has to fix it.
 
well for your sake, I hope they fix it.

because if they don't, you will have wasted a lot of time when you could have just picked up a new router and been all set.
 
Can someone tell me if this is good or bad?

Link speed: 144Mbit/s --> is that slow or good? what should i bet getting on a wireless N router?

and what about these pings? are these normal/slow/good/bad?
 

Attachments

  • Screen shot 2011-04-24 at 2.52.09 AM.png
    Screen shot 2011-04-24 at 2.52.09 AM.png
    154.3 KB · Views: 67
well for your sake, I hope they fix it.

because if they don't, you will have wasted a lot of time when you could have just picked up a new router and been all set.
That is just not true, I have tried my computer om five different networks with similar performance issues on all networks.
 
Link speed: 144Mbit/s --> is that slow or good? what should i bet getting on a wireless N router?

and what about these pings? are these normal/slow/good/bad?

144Mbits/s is pretty much the maximum theoretical data rate one can achieve with 802.11n operating under two separate 20MHz channels or a single 20MHz channel in a 2x2 MIMO (antennae) configuration.
 
Last edited:
I just replicated my erratic pings on a completely different network, using an old AEBS (A1034).

Same song. Pings are all over the map, from 1ms to hundreds of ms. All I have to to is start a download and they drop to sub 1ms consistently until the download has completed.
 
well for your sake, I hope they fix it.

because if they don't, you will have wasted a lot of time when you could have just picked up a new router and been all set.

You're going way out on a limb with no data to back you up.

Yours works fine on a particular router. Mine may not. In fact I've tried it on different routers N, G, old, new.. and it behaves exactly the same.

Honestly it doesn't really bother me and wouldn't be noticeable to most. But it still needs to be fixed.
 
You're going way out on a limb with no data to back you up.

Young man, I've been dealing with Macs and network connectivity issues for damn near 5 years. I have real-world experience spanning 8 or 9 personally-owned Macs across probably 20 different home, office and 3rd party (airports, colleges, coffee shops, malls, etc.) network environments featuring everything from Netgear and Belkin to Linksys and TrendNet. Moreover, I've worked in IT dealing with networking problems with wireless computers of all types for about a decade, across home networks and networks much, much bigger than the ones you've been connect your Mac to (40,000+). I know what I'm talking about.

Sometimes, Macs just don't play as well as you think they should with given routers, depending on their security configurations. Sometimes routers can be flaky and sensitive, no matter how much you paid for them. In such situations, sometimes a 30/30/30 router reset and reconfiguration is needed. Sometimes a change in wireless security type (like WEP instead of WPA2 or visa versa). Sometimes certain routers just won't play well at all, no matter what you try.

Here is a method of testing that will cost you no net money: Go to Best Buy and pick up a different router (like the WNDR3700 or Airport Extreme). Test it for a week or 2 with your preferred security type engaged. If you still see instability, simply return the router at exactly NO cost to you.

In the cases were Macs and routers weren't cooperating, combinations of the above resolved the situations. Your mileage may vary, as may your willingness to try a solution that goes deeper than, "it's apple's fault; I'll wait on them..." but I tell you what: one thing I've learned about Apple is that they may or may not fix an issue. They don't officially acknowledge problems until there's a fix ready to launch. And if there is never a "fix", you could find yourself waiting forever when you could have just found a solution in one of my above recommendations and been happy.

Do what you want to do. But the path of fastest solution is clear:

  1. Try hard-resetting your router and re-entering your normal security. Test. Make sure you're not using WPA2 (TKIP). Only used AES. If still abnormal, change the security type to something else (like WEP) and test again. If still abnormal...
  2. Go get one of the routers being recommended in the thread from someplace with a liberal return policy (Amazon, Best Buy, WalMart, etc.), set it up with you preferred security stuff and run the same tests.

Now, unless you have a genuine hardware issue with your Mac, one of these 2 solutions will work...and your issue can be resolved *TODAY*. Or you can wait on a "fix" from Apple, which may never come, as they may not even actually acknowledge it as an issue. That might be a long, frustrating wait and I'd recommend you avoid it. If you spent big bucks on your Mac, you might want to consider whether skimping on the quality of router is a wise decision. Worst case scenario is you have to buy a better router...but you can always return it in 30 days if you want to.

That's all that's left to be said in this thread. If I were the OP, I'd be making a list of all the routers people are saying work well, and I'd be ordering something online or riding over to a local store to pick something up. It's much faster and pro-active than sitting around, frustrated with and worried about the stability of your expensive computing device.

I think I've covered everything at this point. Do whatever makes you happy. And remember, you can always return routers to local big-box retailers for NO COST. Try #1...and if it doesn't work, try a different router and see if your situation doesn't improve.

I know dealing with networking issues is not fun. I'd recommend installing Tomato or DD-WRT on your routers if they support them, but considering the resistance to new ideas, I assume most of you aren't comfortable or familiar with flashing 3rd party firmware to your routers. If you want to learn more about those solutions (which could also solve your problems), google them. Otherwise, good luck. This will be my last post on this subject, so take care guys. If you have questions related to any of the content in this post, you can PM me.
 
I think the 2011 MBPs are using a new Broadcom card that does 3x3.

You're quite right. However, if the router has 2x MIMO antennas then only 2x streams are permissible. Hence, the 144 Mbits/s link speed. If the router had 3x antennas, then the link speed would up itself to 216 Mbits/s (assuming communications are over a single 20 MHz channel).
 
Young man, I've been dealing with Macs and network connectivity issues for damn near 5 years.

Whatever man... you still have no personal experience with this issue regardless of what you've done before. You also shouldn't make presumptions regarding others level of expertise.

The problem is completely benign for my application, other than checking to see if it exists.. since others are bothered. I do nothing with this device that would ever uncover this problem.

My troubleshooting thus far is to run ping 3-4 times. It's not worth reading your entire post over, let along swap routers.

Unless someone is seeing erratic ping times for games or VoIP, I can't imagine ever noticing this issue.
 
Young man, I've been dealing with Macs and network connectivity issues for damn near 5 years. I have real-world experience spanning 8 or 9 personally-owned Macs across probably 20 different home, office and 3rd party (airports, colleges, coffee shops, malls, etc.) network environments featuring everything from Netgear and Belkin to Linksys and TrendNet. Moreover, I've worked in IT dealing with networking problems with wireless computers of all types for about a decade, across home networks and networks much, much bigger than the ones you've been connect your Mac to (40,000+). I know what I'm talking about.

Arrogance is rarely a good substitute for knowledge. The problem is - you have leapt to conclusions and made assumptions yet have no first hand knowledge in this matter. The issue is here not a router incompatibility. If you'd like to flex your intellectual muscle on this problem - actually get a 2011 and diagnose the issue. That would be a bigger help. Like it or not - Brent is correct. You came in with a sweeping statement - but still have nothing to back it up - whereas folks who actually own the HW in question - can provide data.

Considering exiting this thread if your net contribution is - 'you're all wrong - your notebooks don't have the issue you've observed - it must be the router.' If you're really that convinced - by all means - head over to the Apple support thread and educate the masses over there as well. I'm sure Apple will appreciate you saving them some troubleshooting time.
 
I was just google search this issue and found this thread.

I just purchased a new MBP 15", and the connection is HORRIBLE compare to my old Acer laptop.

The ping issue seriously annoyed me, it also affect the download rate while 2 of my laptop works completely fine.

I was about to walk to Apple store for this issue, but I guess there is nothing they can do for now.
 
Young man, I've been dealing with Macs and network connectivity issues for damn near 5 years. I have real-world experience spanning 8 or 9 personally-owned Macs across probably 20 different home, office and 3rd party (airports, colleges, coffee shops, malls, etc.) network environments featuring everything from Netgear and Belkin to Linksys and TrendNet. Moreover, I've worked in IT dealing with networking problems with wireless computers of all types for about a decade, across home networks and networks much, much bigger than the ones you've been connect your Mac to (40,000+). I know what I'm talking about.

Sometimes, Macs just don't play as well as you think they should with given routers, depending on their security configurations. Sometimes routers can be flaky and sensitive, no matter how much you paid for them. In such situations, sometimes a 30/30/30 router reset and reconfiguration is needed. Sometimes a change in wireless security type (like WEP instead of WPA2 or visa versa). Sometimes certain routers just won't play well at all, no matter what you try.

Here is a method of testing that will cost you no net money: Go to Best Buy and pick up a different router (like the WNDR3700 or Airport Extreme). Test it for a week or 2 with your preferred security type engaged. If you still see instability, simply return the router at exactly NO cost to you.

In the cases were Macs and routers weren't cooperating, combinations of the above resolved the situations. Your mileage may vary, as may your willingness to try a solution that goes deeper than, "it's apple's fault; I'll wait on them..." but I tell you what: one thing I've learned about Apple is that they may or may not fix an issue. They don't officially acknowledge problems until there's a fix ready to launch. And if there is never a "fix", you could find yourself waiting forever when you could have just found a solution in one of my above recommendations and been happy.

Do what you want to do. But the path of fastest solution is clear:

  1. Try hard-resetting your router and re-entering your normal security. Test. Make sure you're not using WPA2 (TKIP). Only used AES. If still abnormal, change the security type to something else (like WEP) and test again. If still abnormal...
  2. Go get one of the routers being recommended in the thread from someplace with a liberal return policy (Amazon, Best Buy, WalMart, etc.), set it up with you preferred security stuff and run the same tests.

Now, unless you have a genuine hardware issue with your Mac, one of these 2 solutions will work...and your issue can be resolved *TODAY*. Or you can wait on a "fix" from Apple, which may never come, as they may not even actually acknowledge it as an issue. That might be a long, frustrating wait and I'd recommend you avoid it. If you spent big bucks on your Mac, you might want to consider whether skimping on the quality of router is a wise decision. Worst case scenario is you have to buy a better router...but you can always return it in 30 days if you want to.

That's all that's left to be said in this thread. If I were the OP, I'd be making a list of all the routers people are saying work well, and I'd be ordering something online or riding over to a local store to pick something up. It's much faster and pro-active than sitting around, frustrated with and worried about the stability of your expensive computing device.

I think I've covered everything at this point. Do whatever makes you happy. And remember, you can always return routers to local big-box retailers for NO COST. Try #1...and if it doesn't work, try a different router and see if your situation doesn't improve.

I know dealing with networking issues is not fun. I'd recommend installing Tomato or DD-WRT on your routers if they support them, but considering the resistance to new ideas, I assume most of you aren't comfortable or familiar with flashing 3rd party firmware to your routers. If you want to learn more about those solutions (which could also solve your problems), google them. Otherwise, good luck. This will be my last post on this subject, so take care guys. If you have questions related to any of the content in this post, you can PM me.

my router is dd-wrt flashed, i dont have the ping problem (it doesnt show up on speedtest.net n i am too lazy to ping my router) but my download speed is substantially less than what it should be (comparison with other computers on the same network).

your post lists some good ideas and i acknowledge the fact about router compatibility, but i believe we have ppl using routers spanning from all those brands u listed (hopefully).

at any rate, thanks for your post. but i dont think i will be jumping on board n buying a router because i dont believe that will help us.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.