>> >> So the culprit is the first IP that should appear in the list but >> >> doesn't? If so, how is that helpful since it's not displayed? >> > >> > 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. > > It could well be your router and it is easy to confirm this after you set it > up to respond to ping (or set it to forward all packets with ICMP protocol to > your server while you're troubleshooting this).
I called AT&T and they say the Westell 6100 modem/router I have will not respond to pings. They said I could put it into bridged mode and set up PPPoE on the computer connected to it which would cause ICMP packets to pass through to the computer. Would you guys recommend that? For sure I won't attempt this until I'm in the same room as the device. - Grant
