Slow internet after Lion OS X Upgrade

olenco wrote:

You can have many DNS server addresses

That's plain humbug.

olenco wrote:

you can manuall add the IP address of your router to the list as well, just in case you come across an obscure OS X Lion function that does not like using a remote DNS server.

Humbug too

olenco wrote:

I keep hoping that Apple is taking a look at these forums and doing something about it.

They don't. This is a plain user to user community.

olenco wrote:

you come across an obscure OS X Lion function that does not like using a remote DNS server.

Networking is not depending on mythical and obscure Lion funktions. Networking is following precise rules and regulations.

About your humbug on the DNS Server entries.

To repeat myself: The rules and regulations allow up to 3 DNS Server entries in the settings.

Sure, you are able to add 15 DNS Server addresses to the list. But ALL systems will follow the rules and only use the first three entries top down.

To repeat myself again: The first entry have to be the main name resolving server in the network and 2 spare entries are allowed. This entries get used one after another top down.

And especially for you: All entries in that list exceed 3 are ignored by default.

While you're right, networking is fairly complex and not always as precise as you say. The problem with finding a solution to this issue is that there are so many variables:

• the type of network you are on
• the amount of broadcast packets flying around the LAN
• Airdrop/bonjour info flying around
• DNS settings (yes only first three, that standard is changing too) locally - on your Mac
• DNS settings in the network
• ISP settings and configuration
• NAT configuration between you and the internet ... list goes on

One can always submit a complaint to apple.

Is there anything in console that looks 'out of the ordinary' - google it - see if there is a fix for that. Lupunus your post doesn't help anyone.

Post what does work for you - that will help others. Good hunting everyone.

Maybe humbug to you but not to those who have success! No need to keep repeating yourself. I'm familiar with how the DNS works. I only have 2 DNS numbers. I'm also problematic free! It sounds like that bothers you!

Someone sent me nasty messages regarding my posts. if that is you, ,you sound like a real wizard, but you never did answer my original post, in which I reported having no problems at all with Lion accessing the Internet, except when using FireFox or Chrome so, humbug to you too! I am just trying to help the poor folks out there who are not at all technical.

While your comments may be correct, your answers do not show-up here and you do not appear to want to help, therefore, if all you want to do is prove how good you are trechnically and how bad other people are, I suggest you submit your resume to Apple or worse, Microsoft, and do something useful to try to help.

I suspect if we discuss this long enough we will come-up with a set of solutions that will work for everyone. I would also be very surprised if no one from Apple is monitoring, however occasionally, this discussion. If you do not want to contribute, what are you doing reading these posts?

Say something really useful and maybe we will all be better off in the end. In addition, the issues reported here do seem to stem from a range of different problems. We all need to try to help each other, and none of use cares who is more technically capable.

My apologies as it was accidentally sent to you. It wasn't meant to be nasty whatsoever if it is me you're referencing. It was meant to be sent to Lupunus, but again, my apologies! Lupunas seems to be feisty in his responses!

barryian wrote:

Maybe humbug to you but not to those who have success! No need to keep repeating yourself. I'm familiar with how the DNS works. I only have 2 DNS numbers. I'm also problematic free! It sounds like that bothers you!

Nope, that bothers me in no way cause it's not my backyard.

Normally it's a clear thing: If it helps, it is good.

Not good is giving false advice to others leading them to do strange things to ease their pain, knowing that this may eventually cause trouble on other systems or even their own systems because rules and protocols are canceled.

It's like using Vicodine instead of pulling the rotten molar. Sure, the pain is gone but the problem as such persits and eventually causes a cardial inflammation later on.

What if you can't pull the tooth just quite yet! They give you Vicodin! Gosh - Try anger management ... i'm gone!!!

False advice? That's a good one! Maybe incomplete advice, but not false.

You really proved my point, which is most unfortunate.

Barryian, please don't worry. Your reply was fine and I liked your replies to Lupunus as well.

lupunus wrote:

Just replay on my own to bring some addtional info in that DNS / Wireless / Lion thing.

We had new suspects at the interrogation room: Airdrop and local

Had a case couple of day's ago with a UK based "My Mac drops network all the time and slow connection" contribution.
Reason and working resolutionon was:
The guy got a new BT DSL/wifi box which have (not changeable) the local domain "home" fixed. Changing on the Mac the domain from "local" to "home" solves the wireless trouble. To proof the solution I scanned some UK-forum's and found similar reports about the fixed "home" domain on that boxes and that changing (mostly Windows machines involved) Windows default set domain "workgroup" to "home" does the trick.

Additional findings along that track:

• The actual wifi chipset firmware (aka driver) enables the "Airdrop" functionality on the chipset although the Airdrop function is not active (available) in Snow Leopard due to different settings in the controlling configuration file(s)
• Aside of Lion, Airdrop requires as well that all Airdrop using systems are member of the domain "local"

leads to ->

• Having two different domains in a network segment causes name resolution (DNS) trouble.
• Name resolution trouble may cause unwanted network traffic and timeout's and therefore disassociation of clients or slow data transfer rates.

This will under certain circumstances also explain the wireless trouble in mixed networks, some public networks or with some Router's which users of 2011 Mac's reports as "WiFi drops / bad connection with my new 2011 MB / MBPro / Air".

Eventually also, the used BC-Chipset gets along the activation of Airdrop ability more sensitive on interferences (this cause bad packets) in the wireless stream due to security reasons when password free computer to computer connection for Airdrop is possible.

But that is at now only speculation.

What means, aside of possible infrastructure, radio interferences and eventually hardware faults, at least we have more possible causes for wireless trouble with Lion or 2011 systems.

Lupunus

lupunus wrote:

...pulling the rotten molar...

I can smell the decay. Great illustration.😎

I have an iMac i7 (mid 2010) that I just upgraded to Lion from Snow Leopard. I was getting close to 20Mbps download before upgrading and about .36Mbps upload (per Speedtest.net). My wife has a 2011 iMac i5 and her computer is in the basement whereas the router is upstairs just down the hall from my computer. My download speeds since the upgrade have dropped to anywhere from 5-10Mbps with uploads increasing to about .98Mbps.

My wife's computer (which came with Lion installed) is running at 20Mbps down and .98Mbps up. I think perhaps Time Warner adjusted something to give that increase in upload speed. But I'm stumped as to how to get my speed back up to that 20Mbps down. If you point the way, I can follow directions, but I'm not a super techie so the jargon can fly over my head a bit.

Any thoughts as to what I might do? I first noticed this when I started watching Netflix videos and noticed that they were not playing in HD suddenly and some photo sites I visit were loading pics slower than normal.

I have a Linksys WRT54GS Wireless-G with Speedbooster router.

Every once in a while, my speed test will jump into the 12-14Mbps range, but it is rare.

Thanks for any help you might offer!

Mar

Spoke with Apple Tech this evening. He had me reset PRAM. After I did that, speeds accelerated to 16-18Mbps and I thought the problem was solved. Tested about 4-5 more times while he was still on phone. All seemed good.

But later, speeds started dropping back to the 6-10Mbps range. Don't know why. Guess another call to Apple.

Mark

Just wanted to put in my 2 cents. I had this issue where my internet was either extremely slow or nonexistent after upgrading to Lion. I went through several forums on this apple support site and others via google. I tried various solutions, but ultimately what worked was changing the channel frequency on my wireless access point from 1 (low frequency) to 9 (medium high). Not so sure why I had it so low previously.

I live in a town house complex and there are very many available WiFi networks within connectivity distance. I used a piece of software on my PC called Xirrus to identify the other networks and corresponding channels nearby and made sure I was on a different channel frequency than those around.

After doing this, all has been good except from time to time when my Mac is inactive, and then I try to access the internet, the connection is completely dead and I have to turn the WiFi off and then back on. Then all is good.

Hope this helps someone resolve their issue.

My 2 cents too...

Had the same problem; extremely slow and unstable wifi-connection, after upgrading to Lion on my late 2008 MBP.

Tried pretty much every reset and a wide range of other suggestions that has been posted here and in other forums.

I am aware that this is probably not an universal fix, but it worked for me (4 days now):

http://rys.pixeltards.com/2011/09/04/osx-lion-wifi.html

Good luck

I finally got mine fixed via a fluke. Whole Internet went down. Called Time Warner - he refreshed the signal to my my modem and I unplugged the modem and the router for about 30 seconds. That suddenly did the trick. My upgraded to Lion i7 suddenly started getting downloads of 15Mbps like it used to before the upgrade. Must have been something in those router settings or something that needed a refresh. Whatever, I'm glad problem is resolved.

Mark