• On The Insider: Kim Kardashian Goes Au Natural
advertisement
January 11, 2005 3:00 AM PST

Mac OS X 10.3.7: General Network slowness

by CNET staff

Severe, overall network slow-downs for a number of systems upgraded to Mac OS X 10.3.7 can cause an array of other problems including slow startup for network-enabled applications and slow startup for Mac OS X itself.

MacFixIt reader Ulf Cronenberg found that changing the format of his local IP address assignment fixed the issue:

"My router - a Draytek Vigor 2900 - had the IP 192.168.1.1. You only have to change it e.g. into 10.0.1.1 and after that Mail, OmniWeb and iChat opens as quick as before. It seems that Mac OS X 10.3.7 has problems with routers using the IPs 192.168.1.x."

Jon confirms the previously reported workaround of manually entering DNS server addresses:

"Typically I left my Location set to 'Automatic' and things would just work between home and office with my AirPort card. After updating my 1.25GHz Aluminum PowerBook to 10.3.7, I experienced dreadful slowness on DNS lookups. But only in the office. While at work, connecting to a Buffalo wireless router, it would often take 5 seconds to do one DNS lookup. [...]I ended up creating a "Work" location and hard assigned the DNS numbers. This sped things up a bit but once I switched from DHCP to Manual and hard assigned all numbers, things are just a fast as they were before the upgrade."

Reader "Lyman's" experiences are actually the opposite of Joe's in terms of how he was able to improve Internet performance after installing the update:

"I discovered something useful that may work for others frustrated with slow online performance after upgrading to OS 10.3.7. If you also use a router, something seems to have changed regarding the use of manual DNS addresses. Prior to the upgrade, I had DNS Servers entered manually, per advice of my ISP, Earthlink, in both the router and in Network Preferences. (Configured IPv4 using DHCP). Now the reverse is true. As an experiment, I created a new Location in Network Prefs. All original settings were re-copied exactly, except that I did not enter anything in the DNS Servers box. (The DNS addresses were left unchanged in the router, however). Instantly Safari, Mail, and Firefox became plenty snappy. The solution was as simple as that. Now it appears having redundant addresses is a liability. Making a new Location alone may have done the trick, or just deleting DNS Servers may have provided the cure. Doing both certainly worked great."

Charles Elliott found that turning off all of his equipment, waiting a few minutes, then turning it all back on resulted in elimination of the network lag:

"Upgraded through Software Update. First couple of starts were very slow but this has improved. Had the same trouble many are having with slow internet apps- slow to launch, didn't seem to be working. I turned off Airport, shut the computer down, powered off my Airport Base Station (graphite), cable modem, and LinkSys router for a few minutes, restarted the modem, router and Airport, and rebooted the PowerBook. No more internet or network problems."

Resources

  • More from Late-Breakers
  • Recent posts from MacFixIt
    iTunes 10 user interface sees some minor changes
    Apple seeds iOS 4.1 Gold Master to developers
    Possible fix for Harman Kardon iSub problems with PowerPC Macs
    Precautions to take before installing iTunes 10
    A reminder on how to reset your Mac's system password
    Mail messages appearing blank
    Adobe Lightroom update brings direct Facebook publishing; Camera Raw 6.2 released
    Weekly troubleshooting utilities update
    Add a Comment (Log in or register)
    by hans.vallden January 12, 2005 12:22 PM PST
    I think all of the suggested fixes for the poor network performance are
    somewhat beside the point and for the most part not very "scientific". It
    would seem that an actual bug in DNS resolution was indeed introduced in
    10.3.7. Apple needs to fix it quickly, because there are many of us who can't/
    won't play around with settings to go around the bug.

    I can assure with absolute confidence that the issue is real and based on my
    experimentation likely appears only in a routed/NAT environment. It would
    also appear to affect certain protocols more than others, eg. HTTPS and SMTP
    AUTH calls from Safari/Mail seem near impossible to execute. The same goes
    for WebDAV connections from iCal. These couple of simple tests prove there's
    something selectively wrong with DNS resolution.

    I have reported this issue to Marc Majka at Apple per his request at the Apple
    Discussion forums on 12/28/04. He or anyone at Apple has failed to
    respond.

    THIS IS A HTTPS REQUEST FROM SAFARI TO A FULLY FUNCTIONAL WEBSITE

    2:/etc hans$ sudo tcpdump -i en0 port 53
    Password:
    tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
    listening on en0, link-type EN10MB (Ethernet), capture size 96 bytes
    23:12:51.303963 IP localhost.49280 > resolver1.kolumbus.fi.domain:
    61722+ A? domain.ficora.fi. (34)
    23:12:51.321206 IP resolver1.kolumbus.fi.domain > localhost.49280: 61722
    1/0/0 A 194.100.96.120 (50)
    23:12:51.321866 IP localhost.49281 > resolver1.kolumbus.fi.domain:
    54667+ A? domain.ficora.fi. (34)
    23:12:51.337560 IP resolver1.kolumbus.fi.domain > localhost.49281: 54667
    1/0/0 A 194.100.96.120 (50)
    23:12:51.337760 IP localhost.49282 > resolver1.kolumbus.fi.domain:
    63675+ AAAA? domain.ficora.fi. (34)
    23:12:51.356946 IP resolver1.kolumbus.fi.domain > localhost.49282: 63675
    0/0/0 (34)
    23:12:51.357212 IP localhost.49283 > resolver1.kolumbus.fi.domain:
    48864+ AAAA? domain.ficora.fi.0.0.10.in-addr.arpa. (54)
    23:12:52.239970 IP localhost.49284 > resolver1.kolumbus.fi.domain:
    62758+ PTR? 40.0.229.193.in-addr.arpa. (43)
    23:12:52.257102 IP resolver1.kolumbus.fi.domain > localhost.49284: 62758
    1/0/0 (78)
    23:12:52.258904 IP localhost.49285 > resolver1.kolumbus.fi.domain:
    26408+ PTR? 120.96.100.194.in-addr.arpa. (45)
    23:12:52.277734 IP resolver1.kolumbus.fi.domain > localhost.49285: 26408
    NXDomain* 0/0/0 (45)
    23:12:56.357307 IP localhost.49286 > resolver2.kolumbus.fi.domain:
    48864+ AAAA? domain.ficora.fi.0.0.10.in-addr.arpa. (54)
    23:12:57.284308 IP localhost.49287 > resolver1.kolumbus.fi.domain:
    10846+ PTR? 42.0.229.193.in-addr.arpa. (43)
    23:12:57.299700 IP resolver1.kolumbus.fi.domain > localhost.49287: 10846
    1/0/0 (78)
    23:13:01.357388 IP localhost.49283 > resolver1.kolumbus.fi.domain:
    48864+ AAAA? domain.ficora.fi.0.0.10.in-addr.arpa. (54)
    23:13:06.357467 IP localhost.49286 > resolver2.kolumbus.fi.domain:
    48864+ AAAA? domain.ficora.fi.0.0.10.in-addr.arpa. (54)
    23:13:11.357548 IP localhost.49283 > resolver1.kolumbus.fi.domain:
    48864+ AAAA? domain.ficora.fi.0.0.10.in-addr.arpa. (54)
    23:13:16.357632 IP localhost.49286 > resolver2.kolumbus.fi.domain:
    48864+ AAAA? domain.ficora.fi.0.0.10.in-addr.arpa. (54)
    23:13:21.357715 IP localhost.49283 > resolver1.kolumbus.fi.domain:
    48864+ AAAA? domain.ficora.fi.0.0.10.in-addr.arpa. (54)
    23:13:26.357793 IP localhost.49286 > resolver2.kolumbus.fi.domain:
    48864+ AAAA? domain.ficora.fi.0.0.10.in-addr.arpa. (54)
    23:13:27.380910 IP resolver2.kolumbus.fi.domain > localhost.49286: 48864
    ServFail 0/0/0 (54)
    23:13:27.381205 IP localhost.49288 > resolver1.kolumbus.fi.domain:
    15964+ AAAA? domain.ficora.fi.0.10.in-addr.arpa. (52)
    23:13:32.381304 IP localhost.49289 > resolver2.kolumbus.fi.domain:
    15964+ AAAA? domain.ficora.fi.0.10.in-addr.arpa. (52)
    23:13:37.381389 IP localhost.49288 > resolver1.kolumbus.fi.domain:
    15964+ AAAA? domain.ficora.fi.0.10.in-addr.arpa. (52)
    23:13:42.381473 IP localhost.49289 > resolver2.kolumbus.fi.domain:
    15964+ AAAA? domain.ficora.fi.0.10.in-addr.arpa. (52)
    23:13:47.381559 IP localhost.49288 > resolver1.kolumbus.fi.domain:
    15964+ AAAA? domain.ficora.fi.0.10.in-addr.arpa. (52)
    23:13:48.404628 IP resolver1.kolumbus.fi.domain > localhost.49288: 15964
    ServFail 0/0/0 (52)
    23:13:48.404871 IP localhost.49290 > resolver2.kolumbus.fi.domain:
    15964+ AAAA? domain.ficora.fi.0.10.in-addr.arpa. (52)
    23:13:53.404964 IP localhost.49291 > resolver1.kolumbus.fi.domain:
    15964+ AAAA? domain.ficora.fi.0.10.in-addr.arpa. (52)
    23:13:58.405050 IP localhost.49290 > resolver2.kolumbus.fi.domain:
    15964+ AAAA? domain.ficora.fi.0.10.in-addr.arpa. (52)
    23:14:03.405222 IP localhost.49292 > resolver1.kolumbus.fi.domain:
    22973+ AAAA? domain.ficora.fi.10.in-addr.arpa. (50)
    23:14:08.405319 IP localhost.49293 > resolver2.kolumbus.fi.domain:
    22973+ AAAA? domain.ficora.fi.10.in-addr.arpa. (50)
    23:14:13.405402 IP localhost.49292 > resolver1.kolumbus.fi.domain:
    22973+ AAAA? domain.ficora.fi.10.in-addr.arpa. (50)
    23:14:14.429353 IP resolver1.kolumbus.fi.domain > localhost.49292: 22973
    ServFail 0/0/0 (50)
    23:14:14.429595 IP localhost.49294 > resolver2.kolumbus.fi.domain:
    22973+ AAAA? domain.ficora.fi.10.in-addr.arpa. (50)
    23:14:19.428316 IP resolver2.kolumbus.fi.domain > localhost.49293: 22973
    ServFail 0/0/0 (50)
    23:14:19.429693 IP localhost.49295 > resolver1.kolumbus.fi.domain:
    22973+ AAAA? domain.ficora.fi.10.in-addr.arpa. (50)
    23:14:24.429773 IP localhost.49294 > resolver2.kolumbus.fi.domain:
    22973+ AAAA? domain.ficora.fi.10.in-addr.arpa. (50)
    23:14:29.429855 IP localhost.49295 > resolver1.kolumbus.fi.domain:
    22973+ AAAA? domain.ficora.fi.10.in-addr.arpa. (50)
    23:14:34.429943 IP localhost.49294 > resolver2.kolumbus.fi.domain:
    22973+ AAAA? domain.ficora.fi.10.in-addr.arpa. (50)
    23:14:35.453707 IP resolver2.kolumbus.fi.domain > localhost.49294: 22973
    ServFail 0/0/0 (50)
    23:14:45.459006 IP resolver2.kolumbus.fi.domain > localhost.49294: 22973
    ServFail 0/0/0 (50)
    ^C
    42 packets captured
    877 packets received by filter
    0 packets dropped by kernel

    THIS IS A HTTP REQUEST FROM SAFARI TO A FULLY FUNCTIONAL WEBSITE
    (Notice the difference in length :))

    2:/etc hans$ sudo tcpdump -i en0 port 53
    tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
    listening on en0, link-type EN10MB (Ethernet), capture size 96 bytes
    23:15:52.808203 IP localhost.49296 > resolver1.kolumbus.fi.domain:
    27515+ A? www.digitoday.fi. (34)
    23:15:52.825365 IP resolver1.kolumbus.fi.domain > localhost.49296: 27515
    1/0/0 A julkaisu.digitoday.fi (50)
    23:15:52.904643 IP localhost.49297 > resolver1.kolumbus.fi.domain: 590+
    PTR? 149.153.64.193.in-addr.arpa. (45)
    23:15:52.920937 IP resolver1.kolumbus.fi.domain > localhost.49297:
    590 1/0/0 (80)
    23:15:55.517594 IP localhost.49298 > resolver1.kolumbus.fi.domain:
    41713+ A? server-fi.imrworldwide.com. (44)
    23:15:55.545277 IP resolver1.kolumbus.fi.domain > localhost.49298: 41713
    13/0/0[|domain]
    ^C
    6 packets captured
    527 packets received by filter
    0 packets dropped by kernel
    Reply to this comment