1 |
>>>>>>>>> My laptop can't ping my remote system but it can ping others |
2 |
>>>>>>>>> (google.com, yahoo.com, etc). I've tried disabling my firewall on |
3 |
>>>>>>>>> both ends with '/etc/init.d/shorewall stop && shorewall clear'. Could |
4 |
>>>>>>>>> my AT&T business ADSL connection on the remote system be blocking |
5 |
>>>>>>>>> inbound pings? |
6 |
>>>> |
7 |
>>>> I did 'traceroute -w 30 -I ip-address' several times and the last IP |
8 |
>>>> displayed is always the same. I looked it up and it's an AT&T IP |
9 |
>>>> supposedly located about 1500 miles from my machine which is also on |
10 |
>>>> an AT&T connection. Does this tell me anything? |
11 |
>>> |
12 |
>>> Yes, it tells you that all hops up to that point at least respond to |
13 |
>>> the kinds of icmp packets traceroute uses. The first hop that fails to |
14 |
>>> answer isn't answering. |
15 |
>>> |
16 |
>>> You are looking for possible reasons why icmp might not be working out |
17 |
>>> properly - that router is your first suspect. Admittedly, it might be |
18 |
>>> blocking traceroute pings and still allow the responses you seek, but |
19 |
>>> you have to start somewhere :-) |
20 |
>> |
21 |
>> So the culprit is the first IP that should appear in the list but |
22 |
>> doesn't? If so, how is that helpful since it's not displayed? |
23 |
> |
24 |
> This is where it gets tricky. You identify the last router in the list |
25 |
> for which you have an address or name, and contact the NOC team for that |
26 |
> organization. Ask them for the next hop in routing for the destination |
27 |
> address you are trying to ping and hope that they will be kind enough to |
28 |
> help you out. |
29 |
|
30 |
Oh man that's funny. Really? Let's say they do pass along the info. |
31 |
Then I hunt down contact info for the culprit router based on its IP |
32 |
and tell them their stuff isn't working and hope they fix it? |
33 |
Actually, since the last IP displayed is from AT&T and my server's ISP |
34 |
is AT&T, I suppose it's extremely likely that the culprit is either an |
35 |
AT&T router somewhere or my own server and I could find out by calling |
36 |
AT&T. |
37 |
|
38 |
- Grant |