5.1 seemed to fix the DNS issue I was having with the Airport Express, and the G5 desktop, but the MBP continues to have the internet hang consistently while in use. Sometimes quitting and reopening Safari seems to jumpstart it, but not always.
Any ideas why this may be happening and how I can resolve the issue is appreciated.
Now, if I can just find the preference for Auto-Make Cup of Coffee How I Like It,
Mac OS X (10.5)
I USED to have this problem on the G5 desktop. I did the DNS trick advised in other threads (while on OSX 10.5), which resolved the issue. Then removed the DNS trick after the X.5.1 update, and haven't had the problem on the G5 desktop since. Yet it still persists ONLY on the Macbook Pro, so I'm assuming it's an entirely different issue.
The G5 is no longer having internet problems, but the Macbook Pro is having one helluva time with it!!! GEEZ! Every 15 minutes the internet just comes to a standstill. Turning the AIrport On/Off results in wierd popups requesting the password, asking for some permissions or something, anyway WAY MORE problems than one should expect. I AM TIRED OF LEOPARD ISSUES....
If this is happening often, can you open a console window and do a 'ping www.ihatecomputers.net' (or some other host that responds outside your local network)?
When things stop working, reference that window and see if your pings have stopped. Curious of it's something def going on with the wireless layer or if safari is just where you're noticing it and it's getting freaked out someplace.
My safari has been hanging quite a bit lately when a plugin needs to be referenced. I have to reset safari's cache and all for it to go back to normal for a while.
My MBP won't stay connected, either. I have the 10.5.1 update but the problem persists. It's the internet itself and not just Safari. When I try to use Adium or aMSN or something I still lose connection to those programs too very often.
It is sort of discouraging to have to wait to get these problems fixed when they're a real pain. :/
We have the same problem with an Airport Express, a MacBook and MacBook Pro with Leopard. Also the password prompts that never came up under Tiger. I hope Apple fixes these issues soon.
I opened a similar thread on this subject (iChat/MSN etc.. disconnects too often). And i'm using an ethernet modem, so... maybe it's not airport related...
I think I've duplicated this. I started having quite a few 'hangs' so I started a network trace.
Things to note: The DNS request is going out (at least out at the level that tcpdump can see). But no response comes back. I stop the trace and do some pings. They all fail due to DNS lookups. I ping my local router by IP, and things respond fine. I then ping the DNS names, and everything is back again.
In the mean time, Safari did the whole error message thing.
That consistent with what you're seeing?
So here's the deal - i'm getting packets in. You can see the requests coming in from other boxes (UPnP from the router, NTP, etc.) so the only thing this could be is that the DNS server really isn't responding. I'm going to force this not to resolve through the routers proxy and go direct to the DNS server and see if it helps.
-- trace data --
Err:~ eb$ sudo tcpdump -ni en1
Password:
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on en1, link-type EN10MB (Ethernet), capture size 96 bytes
22:11:42.876562 IP 192.168.15.102.2190 > 192.168.15.255.2190: UDP, length 161
22:11:43.345151 IP 192.168.15.110.50839 > 192.168.15.1.53: 6960+ A? dashboard.wordpress.com. (41)
22:11:45.441295 IP 192.168.15.1.1900 > 239.255.255.250.1900: UDP, length 317
22:11:45.454594 IP 192.168.15.1.1900 > 239.255.255.250.1900: UDP, length 321
22:11:45.460640 IP 192.168.15.1.1900 > 239.255.255.250.1900: UDP, length 267
22:11:45.470820 IP 192.168.15.1.1900 > 239.255.255.250.1900: UDP, length 313
22:11:45.476469 IP 192.168.15.1.1900 > 239.255.255.250.1900: UDP, length 245
22:11:45.482810 IP 192.168.15.1.1900 > 239.255.255.250.1900: UDP, length 288
22:11:47.521427 IP 192.168.15.110.50840 > 192.168.15.1.53: 2414+ A? dashboard.wordpress.com. (41)
22:11:50.244392 IP 192.168.15.108.4905 > 255.255.255.255.4905: UDP, length 5
22:11:50.645929 IP 192.168.15.110.123 > 17.254.0.28.123: NTPv4, Client, length 48
22:11:51.319655 IP 192.168.15.108.1026 > 255.255.255.255.1900: UDP, length 148
22:11:57.636591 IP 192.168.15.108.1026 > 255.255.255.255.1900: UDP, length 148
22:11:58.345069 IP 192.168.15.110.50841 > 192.168.15.1.53: 35066+ A? dashboard.wordpress.com. (41)
^C
17 packets captured
17 packets received by filter
0 packets dropped by kernel
Err:~ eb$ nslookup dashboard.wordpress.com
^C
Err:~ eb$ ping dashboard.wordpress.com
^C
Err:~ eb$ ping www.google.com
^C
Err:~ eb$ ping 192.168.15.1
PING 192.168.15.1 (192.168.15.1): 56 data bytes
64 bytes from 192.168.15.1: icmp_seq=0 ttl=127 time=1.155 ms
64 bytes from 192.168.15.1: icmp_seq=1 ttl=127 time=1.289 ms
^C
--- 192.168.15.1 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max/stddev = 1.155/1.222/1.289/0.067 ms
Err:~ eb$ ping www.google.com
PING www.l.google.com (64.233.167.147): 56 data bytes
64 bytes from 64.233.167.147: icmp_seq=0 ttl=243 time=33.948 ms
^C
--- www.l.google.com ping statistics ---
1 packets transmitted, 1 packets received, 0% packet loss
round-trip min/avg/max/stddev = 33.948/33.948/33.948/0.000 ms
Err:~ eb$ ping dashboard.wordpress.com
PING lb.wordpress.com (72.233.2.54): 56 data bytes
64 bytes from 72.233.2.54: icmp_seq=0 ttl=54 time=6.912 ms
64 bytes from 72.233.2.54: icmp_seq=1 ttl=54 time=9.562 ms
^C
--- lb.wordpress.com ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max/stddev = 6.912/8.237/9.562/1.325 ms
Ok - this is REALLY weird. I'm tempted to say this is the local router, but I'll need to do more tests on diff systems at the same time to verify. The really really odd part is that the router seems to be dropping the mac out of its arp table. It therefore won't talk to me until it decides to re-arp for my mac address.
Things to note in this trace:
- An ICMP ping is going to the local router (192.168.15.1) and replies are NOT coming back.
- Packets keep coming in and going out on the local network so the local host networking is working just fine.
- Packets destined off-network are not making it out either. See socket 60125 - it's trying to shutdown a previously opened socket and keeps having to retransmit since it's not getting a FIN-ACK back from its FIN.
* The router sends out an ARP request asking for my mac address. So somehow, it has lost it even though I've been sending data for quite a while.
- My box replies.
- The ICMP pings will suddenly start going through.
- The FIN finally gets a FIN-ACK
- Everything is back to normal.
Err:~ eb$ sudo tcpdump -ni en1
Password:
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on en1, link-type EN10MB (Ethernet), capture size 96 bytes
22:23:17.616886 IP 192.168.15.108.1026 > 255.255.255.255.1900: UDP, length 148
22:23:19.784710 IP 192.168.15.110.60133 > 66.135.48.253.80: S 281377011:281377011(0) win 65535 <mss 1460,sackOK,eol>
22:23:23.153365 IP 192.168.15.104.137 > 192.168.15.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
22:23:24.547784 IP 192.168.15.108.4905 > 255.255.255.255.4905: UDP, length 5
22:23:25.153257 IP 192.168.15.104.137 > 192.168.15.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
22:23:25.572028 IP 192.168.15.110 > 192.168.15.1: ICMP echo request, id 57604, seq 0, length 64
22:23:26.395649 IP 192.168.15.110.59928 > 63.246.25.157.80: . 1040691985:1040693425(1440) ack 672412312 win 65535 <nop,nop,timestamp 306542761 10941830>
22:23:26.572250 IP 192.168.15.110 > 192.168.15.1: ICMP echo request, id 57604, seq 1, length 64
22:23:27.153290 IP 192.168.15.104.137 > 192.168.15.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
22:23:27.572506 IP 192.168.15.110 > 192.168.15.1: ICMP echo request, id 57604, seq 2, length 64
22:23:28.572794 IP 192.168.15.110 > 192.168.15.1: ICMP echo request, id 57604, seq 3, length 64
22:23:29.573086 IP 192.168.15.110 > 192.168.15.1: ICMP echo request, id 57604, seq 4, length 64
22:23:29.720933 IP 192.168.15.108.1026 > 255.255.255.255.1900: UDP, length 148
22:23:30.573288 IP 192.168.15.110 > 192.168.15.1: ICMP echo request, id 57604, seq 5, length 64
22:23:30.814409 IP 192.168.15.110.60125 > 72.246.200.199.80: F 3333245440:3333245440(0) ack 1902839257 win 65535 <nop,nop,timestamp 306542806 1047960670>
22:23:30.814712 IP 192.168.15.110.60065 > 63.246.25.157.80: F 2585024105:2585024105(0) ack 1117153205 win 65535 <nop,nop,timestamp 306542806 11362654>
22:23:30.815129 IP 192.168.15.110.60120 > 209.8.114.14.80: F 1100588448:1100588448(0) ack 2720518985 win 65535 <nop,nop,timestamp 306542806 206144478>
22:23:30.815262 IP 192.168.15.110.60119 > 209.8.114.14.80: F 762700974:762700974(0) ack 2716418281 win 65535 <nop,nop,timestamp 306542806 206144475>
22:23:30.815409 IP 192.168.15.110.60121 > 209.8.114.14.80: F 1764537627:1764537627(0) ack 2715530987 win 65535 <nop,nop,timestamp 306542806 206144478>
22:23:31.573572 IP 192.168.15.110 > 192.168.15.1: ICMP echo request, id 57604, seq 6, length 64
22:23:31.805563 IP 192.168.15.110.60125 > 72.246.200.199.80: F 0:0(0) ack 1 win 65535 <nop,nop,timestamp 306542815 1047960670>
22:23:31.805621 IP 192.168.15.110.60121 > 209.8.114.14.80: F 0:0(0) ack 1 win 65535 <nop,nop,timestamp 306542815 206144478>
22:23:31.805656 IP 192.168.15.110.60120 > 209.8.114.14.80: F 0:0(0) ack 1 win 65535 <nop,nop,timestamp 306542815 206144478>
22:23:31.805682 IP 192.168.15.110.60119 > 209.8.114.14.80: F 0:0(0) ack 1 win 65535 <nop,nop,timestamp 306542815 206144475>
22:23:32.390161 IP 192.168.15.1.1900 > 239.255.255.250.1900: UDP, length 253
22:23:32.393245 IP 192.168.15.1.1900 > 239.255.255.250.1900: UDP, length 271
22:23:32.396701 IP 192.168.15.1.1900 > 239.255.255.250.1900: UDP, length 325
22:23:32.403033 IP 192.168.15.1.1900 > 239.255.255.250.1900: UDP, length 247
22:23:32.409240 IP 192.168.15.1.1900 > 239.255.255.250.1900: UDP, length 289
22:23:32.412613 IP 192.168.15.1.1900 > 239.255.255.250.1900: UDP, length 321
22:23:32.422982 IP 192.168.15.1.1900 > 239.255.255.250.1900: UDP, length 313
22:23:32.432941 IP 192.168.15.1.1900 > 239.255.255.250.1900: UDP, length 318
22:23:32.573843 IP 192.168.15.110 > 192.168.15.1: ICMP echo request, id 57604, seq 7, length 64
22:23:33.574092 IP 192.168.15.110 > 192.168.15.1: ICMP echo request, id 57604, seq 8, length 64
22:23:33.578009 arp who-has 192.168.15.110 (c0:a8:c0:a8:c0:a8) tell 192.168.15.1
22:23:33.578094 arp reply 192.168.15.110 is-at 00:1c:b3:7c:a3:18
22:23:33.579890 IP 192.168.15.1 > 192.168.15.110: ICMP echo reply, id 57604, seq 8, length 64
22:23:33.809450 IP 192.168.15.110.60125 > 72.246.200.199.80: F 0:0(0) ack 1 win 65535 <nop,nop,timestamp 306542835 1047960670>
22:23:33.809515 IP 192.168.15.110.60121 > 209.8.114.14.80: F 0:0(0) ack 1 win 65535 <nop,nop,timestamp 306542835 206144478>
22:23:33.809543 IP 192.168.15.110.60120 > 209.8.114.14.80: F 0:0(0) ack 1 win 65535 <nop,nop,timestamp 306542835 206144478>
22:23:33.809568 IP 192.168.15.110.60119 > 209.8.114.14.80: F 0:0(0) ack 1 win 65535 <nop,nop,timestamp 306542835 206144475>
22:23:33.817953 IP 209.8.114.14.80 > 192.168.15.110.60121: R 2715530987:2715530987(0) win 0
22:23:33.817963 IP 209.8.114.14.80 > 192.168.15.110.60120: R 2720518985:2720518985(0) win 0
22:23:33.818455 IP 209.8.114.14.80 > 192.168.15.110.60119: R 2716418281:2716418281(0) win 0
22:23:33.818629 IP 72.246.200.199.80 > 192.168.15.110.60125: . ack 1 win 6795 <nop,nop,timestamp 1048021650 306542835,nop,nop,sack 1 {0:1}>
22:23:34.574380 IP 192.168.15.110 > 192.168.15.1: ICMP echo request, id 57604, seq 9, length 64
22:23:34.580694 IP 192.168.15.1 > 192.168.15.110: ICMP echo reply, id 57604, seq 9, length 64
22:23:34.797482 IP 72.246.200.199.80 > 192.168.15.110.60125: F 1:1(0) ack 1 win 6795 <nop,nop,timestamp 1048022630 306542835>
22:23:34.797591 IP 192.168.15.110.60125 > 72.246.200.199.80: . ack 2 win 65535 <nop,nop,timestamp 306542845 1048022630>
22:23:35.574637 IP 192.168.15.110 > 192.168.15.1: ICMP echo request, id 57604, seq 10, length 64
22:23:35.578570 IP 192.168.15.1 > 192.168.15.110: ICMP echo reply, id 57604, seq 10, length 64
