| 1 |
>>>>> This is where it gets tricky. You identify the last router in the list |
| 2 |
>>>>> for which you have an address or name, and contact the NOC team for that |
| 3 |
>>>>> organization. Ask them for the next hop in routing for the destination |
| 4 |
>>>>> address you are trying to ping and hope that they will be kind enough to |
| 5 |
>>>>> help you out. |
| 6 |
>>>> |
| 7 |
>>>> Oh man that's funny. Really? Let's say they do pass along the info. |
| 8 |
>>>> Then I hunt down contact info for the culprit router based on its IP |
| 9 |
>>>> and tell them their stuff isn't working and hope they fix it? |
| 10 |
>>>> Actually, since the last IP displayed is from AT&T and my server's ISP |
| 11 |
>>>> is AT&T, I suppose it's extremely likely that the culprit is either an |
| 12 |
>>>> AT&T router somewhere or my own server and I could find out by calling |
| 13 |
>>>> AT&T. |
| 14 |
>>> |
| 15 |
>>> Well, I did try to convey a sense of what it sometimes takes to deal |
| 16 |
>>> with such things. Usually your ISP deals with it for you and you'd be |
| 17 |
>>> amazed how often they pick up the phone to do exactly what I described. |
| 18 |
>> |
| 19 |
>> You did, and I suppose it has to come down to that at some point. |
| 20 |
>> Thank you for your help Alan. |
| 21 |
> |
| 22 |
> You're welcome, and I hope you get the issue satisfactorily solved (I |
| 23 |
> don't envy you at all) |
| 24 |
|
| 25 |
Well at this point I think the problem is that the server's Westell |
| 26 |
6100 modem/router doesn't respond to pings unless it's in bridged mode |
| 27 |
(according AT&T). I'll put it into bridged mode the next time I'm |
| 28 |
there. |
| 29 |
|
| 30 |
- Grant |
Archives