Lt. Commander
Join Date: Dec 2007
Posts: 120
# 1 The Tracert Thread
01-22-2010, 09:22 AM
I have found it very difficult to scour every page of every post attempting to locate as many tracerts as possible so I'm going to create a thread specifically for them.

What is a tracert? Trace route. It's a way for you to visually track the progress of packets that travel across the Wide Area Network (WAN) to hopefully identify any connectivity issues.

How do I run a tracert? Go to Start -> Run and enter CMD to bring up a command prompt. Once there, enter this command:

tracert patchserver.crypticstudios.com

and hit enter. You will have a result that should end up looking like this:


C:\>tracert patchserver.crypticstudios.com

Tracing route to patchserver.crypticstudios.com [208.95.184.25]
over a maximum of 30 hops:

1 * * * Request timed out.
2 17 ms 15 ms 14 ms gw.mycitycable.com [216.60.101.33]
3 17 ms 18 ms 27 ms 69.155.161.130
4 50 ms 22 ms 24 ms 12.124.129.97
5 32 ms 27 ms 49 ms cr2.sl9mo.ip.att.net [12.122.142.162]
6 27 ms 28 ms 31 ms cr2.sl9mo.ip.att.net [12.123.140.169]
7 54 ms 41 ms 36 ms cr2.cgcil.ip.att.net [12.122.2.21]
8 29 ms 27 ms 27 ms cgcil01jt.ip.att.net [12.122.86.41]
9 48 ms 31 ms 31 ms 192.205.36.150
10 58 ms 71 ms 66 ms vb2001.rar3.nyc-ny.us.xo.net [207.88.13.10]
11 65 ms 105 ms 62 ms ae0d0.mcr1.cambridge-ma.us.xo.net [216.156.0.26]

12 64 ms 70 ms 70 ms 216.55.4.18
13 59 ms 60 ms 70 ms patchserver.crypticstudios.com [208.95.184.25]

Trace complete.

C:\>




Now, once you have this completed you will right click on the small prompt icon in the upper left hand side of the window.. go down to Edit -> Select All -> press Enter.

Then you can come in here and paste the information with CTRL-V, or right-click paste.

If you experience a tracert in which one of the hops times out, please include another that does show the hop so that it can be identified. I am going to be keeping this thread updated with the routers that I have seen in the tracerts already that have shown poor results.



cr2-tengig-0-15-0-0.NewYork.savvis.net [204.70.196.118]

cr2-pos-0-0-3-0.NewYork.savvis.net [204.70.192.106]

cr2-tengig-0-15-4-0.NewYork.savvis.net [204.70.198.17]

cr2-bundle-pos-1.newyork.savvis.net [204.70.197.34]

cryptic-1.border12.bsn.pnap.net [63.251.130.10]

cr1-tengig-0-15-0-0.NewYork.savvis.net [204.70.196.117]

border12.te8-1-bbnet2.bsn.pnap.net [63.251.128.105]
Lt. Commander
Join Date: Dec 2007
Posts: 120
# 2
01-22-2010, 09:35 AM
lol, I tried this approach yesterday but multiple threads keep poppin up I'd post my tracert but it timeout from the start :/
Lt. Commander
Join Date: Dec 2007
Posts: 120
# 3
01-22-2010, 09:48 AM
Unfortunately the connection seems to come right back most of the time so by the time it pings the bad section, its already up and running again.


A good way to do this is to have the dos prompt running in the background with the command all typed out ready to hit enter.

As soon as you get "server not responding" alt tab and hit enter to run the trace. If you dont get a ping out you can hit the right arrow key in the dos prompt to repeat the command, and try again next time you get the message or dc from the server.

Im still trying but it seems to come back too fast to get a good trace most of the time.
Lt. Commander
Join Date: Dec 2007
Posts: 120
# 4
01-22-2010, 10:00 AM
I ran this on my computer and at 28 hops, it's still timing out on every one...Now granted I'm on a college campus, but I'm still able to send around 25 mbps and receive around that, too, cause I'm wired in. What should I be thinking at this point-- I was able to log in 6 days ago, but can't now.
Lt. Commander
Join Date: Dec 2007
Posts: 120
# 5
01-22-2010, 10:10 AM
Sigh...

I'm gonna throw this out there since a lot of you guys are trying to be helpful, but being aimed in the worng direction by questionable networking advice...

1. Most Firewall servers block ICMP (ping/tracert) by default, but MAY be set to forward traffic to backend devices (i.e. STO's worldservers). The request time outs you see most likely are the traffic load balancers blocking the reply on your pings. The subsequent replies are the backends replying to your ping/tracert

2. Why are you guys tracing the patchserver? If you're going to do your test, it may be better to test the actual world server?


FYI, one of the world servers appears to be 208.95.184.147
Lt. Commander
Join Date: Dec 2007
Posts: 120
# 6
01-22-2010, 10:13 AM
What do you recommend then?
Lt. Commander
Join Date: Dec 2007
Posts: 120
# 7
01-22-2010, 10:17 AM
Tracing route to 208.95.184.147 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 10 ms 9 ms 9 ms 68.85.48.89
4 9 ms 9 ms 9 ms te-9-1-ur02.holt.mi.michigan.comcast.net [68.86.140.73]
5 15 ms 13 ms 14 ms te-0-6-0-7-ar01.pontiac.mi.michigan.comcast.net[68.86.140.69]
6 27 ms 28 ms 28 ms pos-2-1-0-0-cr01.chicago.il.ibone.comcast.net [68.86.90.109]
7 29 ms 28 ms 28 ms pos-0-3-0-0-pe01.350ecermak.il.ibone.comcast.net [68.86.86.158]
8 29 ms 28 ms 28 ms ber1-tengig3-3.chicagoequinix.savvis.net [208.173.180.41]
9 30 ms 28 ms 48 ms cr1-tengig-0-5-0-0.chicago.savvis.net [204.70.196.21]
10 43 ms 45 ms 45 ms cr1-pos-0-0-0-0.NewYork.savvis.net [204.70.192.102]
11 43 ms 42 ms 43 ms er1-te-9-0-0.newyorknyd.savvis.net [204.70.198.165]
12 54 ms 53 ms 68 ms cr2-tengig-0-3-0-0.boston.savvis.net [204.70.198.174]
13 62 ms 52 ms 55 ms cr1-tengig0-5-0-0.boston.savvis.net [204.70.197.49]
14 51 ms 50 ms 50 ms acr1-pos-3-0-0.boston.savvis.net [204.70.195.166]
15 85 ms 199 ms 213 ms internap.Boston.savvis.net [208.172.51.230]
16 48 ms 47 ms 47 ms border12.te7-1-bbnet1.bsn.pnap.net [63.251.128.42]
17 54 ms 54 ms 53 ms cryptic-1.border12.bsn.pnap.net [63.251.130.10]
18 50 ms 50 ms 50 ms 208.95.184.147

Trace complete.
Lt. Commander
Join Date: Dec 2007
Posts: 120
# 8
01-22-2010, 10:22 AM
Italy one here ... first direct , 2nd vpn to US , 3rd vpn to holland.

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\ghigo>tracert patchserver.crypticstudios.com

Tracing route to patchserver.crypticstudios.com [208.95.184.25]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 32 ms 32 ms 19 ms r-bg36-vl11.opb.interbusiness.it [217.141.105.20
2]
4 34 ms 19 ms 19 ms 172.17.5.9
5 20 ms 37 ms 20 ms 172.17.6.89
6 21 ms 34 ms 21 ms mil26-ibs-resid-107.mil.seabone.net [195.22.192.
185]
7 119 ms 120 ms 118 ms ash2-new11-racc1.new.seabone.net [195.22.216.225
]
8 121 ms 120 ms 120 ms 206.111.0.161.ptr.us.xo.net [206.111.0.161]
9 117 ms 116 ms 117 ms te-11-4-0.rar3.washington-dc.us.xo.net [207.88.1
2.201]
10 128 ms 126 ms 127 ms te-3-0-0.rar3.nyc-ny.us.xo.net [207.88.12.73]
11 205 ms 125 ms 143 ms ae0d0.mcr1.cambridge-ma.us.xo.net [216.156.0.26]

12 127 ms 126 ms 127 ms 216.55.4.18
13 127 ms 140 ms 127 ms patchserver.crypticstudios.com [208.95.184.25]

Trace complete.

C:\Users\ghigo>tracert patchserver.crypticstudios.com

Tracing route to patchserver.crypticstudios.com [208.95.184.25]
over a maximum of 30 hops:

1 * * * Request timed out.
2 * * * Request timed out.
3 196 ms 195 ms 196 ms las-bb1-link.telia.net [213.248.85.173]
4 196 ms 195 ms 195 ms xo-125743-las-bb1.c.telia.net [213.248.94.78]
5 196 ms 196 ms 195 ms te-4-1-0.rar3.la-ca.us.xo.net [207.88.12.153]
6 * 280 ms 277 ms vb15.rar3.dallas-tx.us.xo.net [207.88.12.45]
7 280 ms 279 ms 280 ms te-3-2-0.rar3.chicago-il.us.xo.net [207.88.12.13
]
8 279 ms 289 ms 279 ms ae0d0.mcr2.cambridge-ma.us.xo.net [216.156.0.30]

9 277 ms 278 ms * ae1d0.mcr1.cambridge-ma.us.xo.net [216.156.1.13]

10 286 ms 287 ms 287 ms 216.55.4.18
11 277 ms 278 ms 277 ms patchserver.crypticstudios.com [208.95.184.25]

Trace complete.

C:\Users\ghigo>tracert patchserver.crypticstudios.com

Tracing route to patchserver.crypticstudios.com [208.95.184.25]
over a maximum of 30 hops:

1 * * * Request timed out.
2 * * * Request timed out.
3 40 ms 132 ms 37 ms vl304.gw2.ams.giganews.com [216.196.108.219]
4 38 ms 38 ms 38 ms vl305.gw1.ams.giganews.com [216.196.108.226]
5 39 ms 37 ms 38 ms xe-0-2-0-0.ams20.ip4.tinet.net [213.200.75.113]

6 127 ms 128 ms 127 ms xe-0-0-0.nyc30.ip4.tinet.net [89.149.187.62]
7 125 ms 125 ms 127 ms as2828.ip4.tinet.net [213.200.84.146]
8 132 ms 130 ms 128 ms vb2000d1.rar3.nyc-ny.us.xo.net [207.88.13.38]
9 222 ms 134 ms 132 ms ae0d0.mcr1.cambridge-ma.us.xo.net [216.156.0.26]

10 140 ms 126 ms 142 ms 216.55.4.18
11 132 ms 131 ms 137 ms patchserver.crypticstudios.com [208.95.184.25]

Trace complete.
Lt. Commander
Join Date: Dec 2007
Posts: 120
# 9
01-22-2010, 10:26 AM
Quote:
Originally Posted by Efaris
Sigh...

I'm gonna throw this out there since a lot of you guys are trying to be helpful, but being aimed in the worng direction by questionable networking advice...

1. Most Firewall servers block ICMP (ping/tracert) by default, but MAY be set to forward traffic to backend devices (i.e. STO's worldservers). The request time outs you see most likely are the traffic load balancers blocking the reply on your pings. The subsequent replies are the backends replying to your ping/tracert

2. Why are you guys tracing the patchserver? If you're going to do your test, it may be better to test the actual world server?


FYI, one of the world servers appears to be 208.95.184.147
Sweet thanks........for nothing???
Lt. Commander
Join Date: Dec 2007
Posts: 120
# 10
01-22-2010, 10:29 AM
Quote:
Originally Posted by 021
Many do, in this case you take good and bad traceroutes for comparison. In this case the hops do respond fine when there is no problem.

Good:

Tracing route to 208.95.185.174 over a maximum of 30 hops

1 1 ms <1 ms <1 ms 192.168.1.1
2 6 ms 7 ms 7 ms 73.194.112.1
3 6 ms 7 ms 6 ms [68.85.161.249]
4 10 ms 9 ms 9 ms te-0-5-0-1-ar01.needham.ma.boston.comcast.net [68.87.145.245]
5 14 ms 10 ms 11 ms pos-0-1-0-0-ar01.woburn.ma.boston.comcast.net [68.85.162.146]
6 41 ms 40 ms 45 ms pos-2-5-0-0-cr01.chicago.il.ibone.comcast.net [68.86.90.1]
7 40 ms 42 ms 42 ms pos-0-1-0-0-pe01.350ecermak.il.ibone.comcast.net [68.86.86.38]
8 44 ms 47 ms 42 ms ber1-tengig3-3.chicagoequinix.savvis.net [208.173.180.41]
9 43 ms 41 ms 46 ms cr1-tengig-0-5-0-0.chicago.savvis.net [204.70.196.21]
10 69 ms 70 ms 69 ms cr2-pos-0-0-3-0.NewYork.savvis.net [204.70.192.106]
11 72 ms 69 ms 70 ms er1-te-1-0-0.newyorknyd.savvis.net [204.70.196.70]
12 93 ms 81 ms 81 ms cr2-tengig-0-3-0-0.boston.savvis.net [204.70.198.174]
13 76 ms 81 ms 78 ms acr2-pos-3-0-0.boston.savvis.net [204.70.195.170]
14 79 ms 79 ms 76 ms acr1-as0-0.Boston.savvis.net [208.172.51.53]
15 76 ms 76 ms 75 ms internap.Boston.savvis.net [208.172.51.230]
16 103 ms 220 ms 203 ms border12.te8-1-bbnet2.bsn.pnap.net [63.251.128.105]
17 82 ms 85 ms 89 ms cryptic-1.border12.bsn.pnap.net [63.251.130.10]
18 80 ms 81 ms 86 ms 208.95.185.174



Bad:

Tracing route to 208.95.185.174 over a maximum of 30 hops

1 1 ms <1 ms <1 ms 192.168.1.1
2 6 ms 7 ms 7 ms 73.194.112.1
3 6 ms 7 ms 6 ms [68.85.161.249]
4 10 ms 9 ms 9 ms te-0-5-0-1-ar01.needham.ma.boston.comcast.net [68.87.145.245]
5 11 ms 10 ms 14 ms pos-0-1-0-0-ar01.woburn.ma.boston.comcast.net [68.85.162.146]
6 40 ms 43 ms 39 ms pos-2-5-0-0-cr01.chicago.il.ibone.comcast.net [68.86.90.1]
7 43 ms 43 ms 41 ms pos-0-1-0-0-pe01.350ecermak.il.ibone.comcast.net [68.86.86.38]
8 43 ms 41 ms 40 ms ber1-tengig3-3.chicagoequinix.savvis.net [208.173.180.41]
9 41 ms 42 ms 41 ms cr1-tengig-0-5-0-0.chicago.savvis.net [204.70.196.21]
10 69 ms 70 ms 69 ms cr2-pos-0-0-3-0.NewYork.savvis.net [204.70.192.106]
11 71 ms 70 ms 70 ms er1-te-1-0-0.newyorknyd.savvis.net [204.70.196.70]
12 89 ms 81 ms 78 ms cr2-tengig-0-3-0-0.boston.savvis.net [204.70.198.174]
13 133 ms 77 ms 76 ms acr2-pos-3-0-0.boston.savvis.net [204.70.195.170]
14 134 ms 77 ms 77 ms acr1-as0-0.Boston.savvis.net [208.172.51.53]
15 76 ms 77 ms 75 ms internap.Boston.savvis.net [208.172.51.230]
16 89 ms 77 ms 77 ms border12.te8-1-bbnet2.bsn.pnap.net [63.251.128.105]
17 * * * Request timed out.
18 * * 191 ms 208.95.185.174
Hey sulda this was posted in the other thread, I dunno if your still checking them all, thoght Id repost it in your thread. It has the good and the bad.
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


All times are GMT -7. The time now is 10:30 PM.