This discussion is archived
9667 Views 90 Replies Latest reply: Aug 26, 2009 1:12 AM by James Snook
Currently Being ModeratedMar 31, 2009 7:55 PM (in response to roames)Apple's support is non-responsive and ineffective. I have had a ticket open on this issue now for over a week. Without serious prodding, I get nothing back from a plethora of reps who have been trying to support me on this case.
It's time for Apple to step up and actually provide SUPPORT. I have sent traces to engineering. They have been sitting in the queue since Thursday or Friday. Clearly nobody cares.
VERY frustrating indeed.iMac Core Duo, Mac OS X (10.4.11), iPod Video 30 GB
Currently Being ModeratedMar 31, 2009 9:27 PM (in response to roames)please dont throw rocks at me if i am already saying something that has already been said or tried. the thread is too long and all i did was browse it to see where things were going.
my understanding is that you have this config:
AirportX > router "SL" > Modem ==> ISP
i know you do not feel that it is DNS related but you have said that when clearing the chache on the local machine it seems to have helped; albeit for a minute or so. i will just give some basic troubleshooting and then try to get to the point.
make sure that only one device is handling the DHCP and DNS. it doesnt have to be the same device but if it is not the same device each device needs to know where the other is.
(I know your other computers are running fine, but we need to see if there is a relation to your clearing cache and making things better)
consumer routers do not keep a huge DNS cache they simply learn to where to point to for resolving DNS. some routers / firewalls act as a DNS proxy and that doesnt always play nice with the some ISPs. make sure your router does not have that option, if it does turn it off or make sure you understand what it is doing.
ping 188.8.131.52 or .1 and see if the echo reply is immediate. it should be, that is a root server.
on your leopard computer place those two addresses for your DNS servers in network preferences and DISABLE any statically assigned DNS servers on your devices. (just for now)
see if that makes a difference.
if it is a DNS issue your results should be consistent on any browser and any mac connected via THE SAME medium (ie. wireless or ethernet)
if none of this makes any difference then remove your SL router and use your Airport Extreme to connect to your ISP. Again at first let it use your ISP for DNS and then use OpenDNS (my favorite) or better yet the root server (184.108.40.206 and 220.127.116.11) both are solid and will be far more reliable than anything else.
lastly, (maybe should be firstly) when you open a browser make sure that the process it self is not eating resources and it is functioning properly. use "top" in terminal or "activity monitor"
i have the same set up leopard 5.6 using Airport Extreme and SnapGear Firewall VPN router then to ISP (Charter cable). i have not had any issues at all. my browsers are Firefox 3.0.8 and Safari 4Beta and both are just lightning fast on a 5mb connection.
about me: Network systems Engineer MCP,CCNA i work with Linux and MacOSX clients and servers and as well as Windows systems. I believe that there is always a cause to problems and there is always a way to fix them, just not always pretty.
good luck.MacBook pro, Mac OS X (10.5.6), 2GB RAM
Currently Being ModeratedMar 31, 2009 9:42 PM (in response to keggo)Mine is fixed! Finally! I bought a new router. I had a Netgear G router (WGR614v5) and switched to an Netgear N router(WNR834Bv2). I bought a refurb at newegg for $25 and it saved me from going insane. I can't tell you why or how it works, but my internet connection is flying again on my macbook air. Good luck solving your problem!MacBook Pro 2.2, Mac OS X (10.5.6)
Currently Being ModeratedApr 1, 2009 4:27 AM (in response to keggo)"Keggo"
You are a good person to write such a thoughtful and comprehensive reply. I know it sounds like a DNS issue -- it is. I just believe it's an incompatibility that was introduced with the 10.5.6 update and CERTAIN wireless routers. (That's why my router works for everything else connected). If you see David's post below, you'll see he solved the problem by changing out his router.
If I have time, I'll go through your steps, though I have already done most of them.
But I want you to know that I deeply appreciate your taking the time to think through this and write a cogent and thoughtful suggestion. If only Apple would take the time to do such things!iMac Core Duo, Mac OS X (10.4.11), iPod Video 30 GB
Currently Being ModeratedApr 1, 2009 4:28 AM (in response to David Oei)David,
Thanks. This confirms my suspicion that 10.5.6 introduced something with certain wireless routers. If Apple ever gets around to telling me what they find in my trace, I will post it here. I'm afraid I'm not too hopeful in that regard. They show little desire to help, and no response with any timeliness.Macbook Air, Mac OS X (10.5.6)
Currently Being ModeratedApr 1, 2009 6:25 AM (in response to roames)A new router solved my issue too. Since installing 10.5.6, I had experienced slow internet and connection dropouts, even though system said it was still connected. After experiments, I realized when I bypassed the router straight to my computer, all was well, so I got a new router and everything is fine again.G4 Dual, Mac OS X (10.5.6)
Currently Being ModeratedApr 1, 2009 7:20 AM (in response to roames)I am surprised that those affected took so long to discover that this is a wireless issue particularly as I mentioned the possibility on 4 March (via link) and 15 March.Xserve and two 733 MHz G4s with Leopard !, Mac OS X (10.5.6)
Currently Being ModeratedApr 1, 2009 10:31 AM (in response to opto)Unless there is more than one bug this could point to an OS code issue affecting only some types of Mac. Older Macs (my G4s are OK) and some new ones (my Intel Xserve is OK) appear not to be affected - I rarely use wireless.Xserve and two 733 MHz G4s with Leopard !, Mac OS X (10.5.6)
Currently Being ModeratedApr 16, 2009 5:12 AM (in response to opto)I have a new router, and the problem was fixed. My last post on this topic was removed for revealing too much dirt. I wanted everyone to know that a newer router does solve this problem.Macbook Air, Mac OS X (10.5.6), iPod Video 30 GB
Currently Being ModeratedApr 16, 2009 6:17 AM (in response to roames)Hoping everyone who bought new routers did the obvious before laying out the money.
Reload router firmware and check configuration
I'm running a 9 year old 4 port switch in front of an Airport Extreme unit. Everything ok here at the moment.Pismo 550 G4, Kihei 400 SE, MacBook Pro 15" (2.5 ghz Penryn), Mac OS X (10.4.11), 1024 mb RAM in G3s; 2gb RAM and OS 10.5.6 in Penryn
Currently Being ModeratedApr 16, 2009 9:48 AM (in response to keggo)Keggo, that was insightful. I had not really thought about how the router might be acting as a DNSd so far, and this makes sense. And it does indeed help make some of the earlier posts make sense even if they were not pointing in exactly the same direction.
Oddly, I put a reply in here this morning and it does appear to have been removed, or did not post properly.
All it said was I had also decided to just get a new router. Wireless is my medium but certainly not the issue, the OpenDNS servers after a few weeks testing (I'd been busy, sorry I did not reply earlier) really did seem to solve the problem. Although I tried not to assume anything I clearly did. That was not smart of me.
My router is ok, it is old, but it is not going o see any new firmware. I'm still somewhat annoyed that only Mac OS 10.5.6 specifically decided that my router/isp DNSd was no longer good enough for it. But then, that's not too unusual for Apple I suppose
Thank you all for the input. It took a lot of back and forth with some dead ends but I feel like for some of us the problem is more clear, and I definitely got some new info out of it.
Currently Being ModeratedApr 16, 2009 10:15 AM (in response to James Snook)I got the following via email but can no longer find it here on either page 1 or page 2. You may wish to report this strange behaviour.
James Snook posted "Re: 10.5.6 causing terribly slow Internet access" in "10.5.6 causing terribly slow Internet access" on Apr 15, 2009 7:24:05 PM.
I have come to the same conclusion really. As stated by someone else earlier, not all DNS servers are of the same quality, and clearly my routers old software is not up to spec. Quite why it was OS Ten point five point six specifically that made this a problem if beyond me though.
I'll just have to see if I can pick up a better router some point. Annoying as only this one specific revision of this one specific OS is the problem where everything else is fine with it.
--------------------------------------------------------------Xserve and two 733 MHz G4s with Leopard !, Mac OS X (10.5.6)
Currently Being ModeratedApr 16, 2009 10:58 AM (in response to Neville Hillyer)The thing that really makes me wonder is this:
1: I have several Mac's in my house, all of them are 10.5.6. (MacBook Pro, iMac G4 and Intel iMac)
2: My router is an Apple Airport Extreme
3: only the Intel iMac is having issues with this
So, I'm not horribly interested in replacing the router since I have it set up to deal with Time Machine and nothing else out there really does that. (not only that, it's not an inexpensive piece of hardware that Apple should know a thing or two about!)
Something else is going wrong here with 10.5.6 that causes this issue SOMETIMES on some machines. Apple has been non-responsive on this.
I'm going to re-install Leopard from scratch on the iMac to see if that fixes it. I've got to do some backups of mail, address book, documents, and web bookmarks first. But in the end, a software change should not require people to buy new routers unless there is a warning up front that says something like "This upgrae enables xyz feature which is incompatible with previous dongles, if you want to continue to use your dongle then you should not install this"
shame on you apple!iMac G4, Mac OS X (10.4.7)