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