Odd network related issue - need help!

[Motiv]

Sup Folks - looking for some advice on this issue... any advice/help is appreciated.

We have two bonded T1s here at the office (lol) and last weekend we are completely down for about 48 hours. TWTelecom said there was an issue at the Bellsouth CO with a fried wire on the cross connect equipment or something along those lines. Whatever, we lost like $100k in sales.

Anyways, we are experiencing some odd issues reaching certain websites at certain times.

Examples of a few sites: clearwire.com, wikipedia.org, amazon.com

When the problem happens I can ping the domain names and get an IP address, so our local DNS can't be the issue. When I tracert to the websites it dies in mid route.

I talked to TWTelecom on this issue and they said the router we connect to can trace to all of those websites no problem. What does this tell you?

Tracert results:

C:\Users\xxxx>tracert wikipedia.org

Tracing route to wikipedia.org [208.80.152.2]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 64.132.109.130
2 4 ms 3 ms 4 ms 64.132.109.129
3 10 ms 8 ms 7 ms 64-132-140-113.static.twtelecom.net [64.132.140.
113]
4 16 ms 16 ms 32 ms peer-01-ge-1-0-0-1.asbn.twtelecom.net [64.129.24
9.18]
5 17 ms 17 ms 18 ms te-11-0-0.rar3.washington-dc.us.xo.net [207.88.1
2.10]
6 43 ms 43 ms 44 ms te-3-0-0.rar3.atlanta-ga.us.xo.net [207.88.12.9]

7 42 ms 42 ms 44 ms te-11-4-0.rar3.dallas-tx.us.xo.net [207.88.14.41
]
8 72 ms 72 ms 72 ms 207.88.14.42.ptr.us.xo.net [207.88.14.42]
9 91 ms 80 ms * w006.z207088246.xo.cnc.net [207.88.246.6]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 ^C
C:\Users\xxxx>tracert clearwire.com

Tracing route to clearwire.com [206.196.118.2]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 64.132.109.130
2 3 ms 3 ms 3 ms 64.132.109.129
3 114 ms 7 ms 7 ms 64-132-140-109.static.twtelecom.net [64.132.140.
109]
4 15 ms 15 ms 15 ms peer-01-ge-1-0-0-1.asbn.twtelecom.net [64.129.24
9.18]
5 16 ms * * cr1-tengig0-7-2-0.washington.savvis.net [204.70.
197.242]
6 34 ms 35 ms 34 ms cr1-tengig-0-0-5-0.chicago.savvis.net [204.70.19
5.113]
7 33 ms 33 ms 34 ms acr1-so-0-0-0.chicago.savvis.net [208.172.3.54]

8 42 ms 40 ms 42 ms 208.172.211.170
9 39 ms 39 ms 41 ms static-216.87.63.25.primary.net [216.87.63.25]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * ^C
C:\Users\xxxx>tracert amazon.com

Tracing route to amazon.com [72.21.203.1]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 64.132.109.130
2 3 ms 4 ms 3 ms 64.132.109.129
3 8 ms 7 ms 8 ms 64-132-140-113.static.twtelecom.net [64.132.140.
113]
4 * 16 ms 16 ms 66.192.240.22
5 17 ms * * po-2.r04.asbnva01.us.bb.gin.ntt.net [129.250.2.1
81]
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * ^C
C:\Users\xxxx>






Thanks!

 

[stduc]

I have no idea - but....
As far as I am aware the message * * * Request timed out. simply means that the router in question has been configured to ignore ICMP requests. (If I am wrong I am sure someone will correct me)

But - don't abort the trace - let it complete and increase the default timeout and number of hops if necessary.

Having said that I don't think 'the problem' is yours, or under your control. Just 'one of those things'

My results - for what they are worth.


Tracing route to wikipedia.org [208.80.152.2]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms myrouter
2 32 ms 31 ms 31 ms x.x.x.x
3 32 ms 32 ms 31 ms x.x.x.x
4 33 ms 32 ms 32 ms x.x.x.x
5 33 ms 33 ms 34 ms gig-9-1-rtr001.hex.opaltelecom.net [62.24.254.10]
6 35 ms 33 ms 33 ms xe-11-2-0-scr001.sov.as13285.net [78.144.1.130]
7 33 ms 33 ms 33 ms xe-10-0-0-scr010.sov.as13285.net [78.144.0.228]
8 81 ms 211 ms 219 ms linx-1.wvfiber.net [195.66.224.233]
9 108 ms 108 ms 108 ms ny60-vl14-lon-vl14.wvfiber.net [66.216.48.213]
10 150 ms 205 ms 130 ms ord-ten1-2-nyc-ten1-4.wvfiber.net [66.216.48.205]
11 130 ms 130 ms 130 ms 64.127.129.106
12 176 ms 175 ms 176 ms e1-5.pr0.atlx.hgtn.net [66.113.197.10]
13 188 ms 188 ms 189 ms g5-0.pr0.tpax.hgtn.net [66.113.197.54]
14 168 ms 167 ms 168 ms ge8-1.csw5-pmtpa.wikimedia.org [66.113.197.94]
15 168 ms 169 ms 168 ms rr.pmtpa.wikimedia.org [208.80.152.2]



Tracing route to clearwire.com [206.196.118.2]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms myrouter
2 32 ms 31 ms 31 ms x.x.x.x
3 32 ms 32 ms 31 ms x.x.x.x
4 33 ms 32 ms 32 ms x.x.x.x
5 35 ms 34 ms 34 ms gig-6-1-rtr002.bre.opaltelecom.net [62.24.254.186]
6 33 ms 32 ms 32 ms gig-10-1-rtr001.thn.opaltelecom.net [62.24.254.42]
7 33 ms 34 ms 32 ms host-78-144-1-6.as13285.net [78.144.1.6]
8 33 ms 33 ms 33 ms xe-10-0-0-scr010.thn.as13285.net [78.144.0.224]
9 34 ms 34 ms 33 ms gi9-47.mpd01.lon01.atlas.cogentco.com [130.117.14.197]
10 36 ms 34 ms 34 ms te7-3.mpd02.lon01.atlas.cogentco.com [130.117.2.26]
11 108 ms 107 ms 107 ms te9-3.ccr04.jfk02.atlas.cogentco.com [130.117.2.105]
12 108 ms 108 ms 107 ms gi13-0-0.core02.jfk02.atlas.cogentco.com [154.54.5.233]
13 113 ms 113 ms 113 ms po1-0.core01.bos01.atlas.cogentco.com [154.54.7.77]
14 132 ms 132 ms 133 ms po5-0.core01.alb02.atlas.cogentco.com [66.28.4.110]
15 133 ms 133 ms 132 ms po13-0.core01.ord01.atlas.cogentco.com [154.54.7.18]
16 139 ms 139 ms 139 ms po14-0.core01.stl03.atlas.cogentco.com [154.54.3.66]
17 138 ms 138 ms 138 ms vl3503.na21.b006098-0.stl03.atlas.cogentco.com [38.20.36.238]
18 139 ms 138 ms 138 ms river-city-internet-group.demarc.cogentco.com [38.104.162.10]
19 141 ms 140 ms 141 ms static-216.87.62.241.primary.net [216.87.62.241]
20 140 ms 139 ms 139 ms static-216.87.63.25.primary.net [216.87.63.25]
21 140 ms 139 ms 139 ms swan27.cgrewards.net [206.196.118.2]


Tracing route to amazon.com [72.21.203.1]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms myrouter
2 32 ms 31 ms 31 ms x.x.x.x
3 32 ms 32 ms 31 ms x.x.x.x
4 33 ms 32 ms 32 ms x.x.x.x
5 34 ms 33 ms 33 ms gig-12-1-rtr001.hex.as13285.net [62.24.254.74]
6 34 ms 33 ms 33 ms xe-10-2-0-scr001.sov.as13285.net [78.144.1.128]
7 33 ms 33 ms 34 ms xe-0-2-0-225.lon20.ip.tiscali.net [77.67.64.13]
8 111 ms 111 ms 110 ms so-0-0-0.was11.ip.tiscali.net [213.200.81.89]
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 77.67.108.34 reports: Destination net unreachable.

Trace complete.

Which is interesting as I can reach amazon.com

so I tried tracert -h 100 -w 5000

http://www.amazon.com

- and got much the same result!



[navy]When I married "Miss Right" I didn't realise her first name was 'always'. LOL[/navy]

 

[burtsbees]

The first two are obviously not denying ICMP echoes. This could be an MTU issue, though. Try an extended ping...do you have any Cisco devices? An extended ping with extended commands selected will let you set the df bit to determine the MTU.

Burt

 

[Yaoul]

Hi Motiv,

When your problem occurs, I understand that you can't reach some websites through your internet browser ; am I right ? Do you have tested some more sites at this time, are there some that you can reach in the same time ?
Did you try to do ipconfig /flushdns when this occurs ? You say that the ping command returns you a domain name resolution ; do you get echo replies then ?

About the tests you performed, I suppose that the security level isn't the same in each of those companies. Amazon could (an seems to) filter traffic, denying access to its webservers for traceroute / ping traffic. This doesn't mean that reaching the site's not possible.

By the way, when you are checking your DNS entries, please use nslookup rather than ping : that gives more credible results. Ping could use cache entries for resolving some domain names.

Finally, you tell that your tracert dies in mid route, however from what I can see, you reach the last layer 3 device before the wikipedia.org server, for an example. It recalls me a problem I've already met ; I'm gonna think about it and tell you more as soon as I remember it all.

Regards,

Yaoul

 

[stduc]

I wouldn't fuss about amazon - they seem to have problems.

http://www.theregister.co.uk/2008/06/06/amazon_site_down/

[navy]When I married "Miss Right" I didn't realise her first name was 'always'. LOL[/navy]