3 ms·
Let me first say I am nto an expert in this area but have been in a similar position. These kinds of problems are frustrating. I cant tell by your initial descr
by mbubb 11y ago
Let me first say I am nto an expert in this area but have been in a similar position. These kinds of problems are frustrating. I cant tell by your initial description how many other things you have tried. Maybe the following is obvious for you.
What else have you tried?
To get more information - look at "mtr" - I find it sometimes shows me where in the path things are going wrong.
This is a decent intro to it:
https://www.linode.com/docs/networking/diagnostics/diagnosing-network-issues-with-mtr https://www.linode.com/docs/networking/diagnostics/diagnosin...
Did you notice that the final IP addr is in level3?
It looks
dig -x 209.244.104.134
;; AUTHORITY SECTION:
244.209.in-addr.arpa. 3600 IN SOA ns2.Level3.net. dns.Level3.net. 2015052900 7200 600 2592000 3600
- jackr9 11y agoI did find out that the location of the final IP address is in San Jose. I didn't know you could use that dig command, thanks. The linode link says that ping, traceroute and mtr commands use ICMP packets to test and if I'm not wrong Apple's servers don't respond to that (I can't check for this because the VPN blocks ICMP packets too). I don't know of anything to try. I've just tried ping and traceroute and will try mtr.