NEW CENTRAL SERVER IP

**azalea** · 04-11-13, 08:47 AM

Open a windows command prompt and do

tracert x.x.x.x

where you put in the ip address of the server instead of x.

**iLLusioN** · 04-11-13, 05:34 PM

Originally Posted by StrickeN

Timer Warner and right by Kansas City, MO.

tbh, I dont know how to find those trace routes that Rad put up

Damn =/ I know a couple guys working at Charter near Warrensburg, thought maybe I could cheat a little. As azalea said, just open up command prompt and tracert server.ip.goes.here

It can take awhile..once it's done right click, select all and hit enter to copy it and post up here.

**StrickeN** · 04-11-13, 08:03 PM

Central Server.

Tracing route to host.colocrossing.com [72.249.124.131]
over a maximum of 30 hops:

1 * * 90 ms cpe-65-26-16-1.kc.res.rr.com [65.26.16.1]
2 16 ms 11 ms 13 ms tge7-1.kscfmo11-cer1.kc.rr.com [65.28.16.34]
3 61 ms 85 ms 78 ms tge0-10-0-5.ksczmogn-ccr1.kc.rr.com [98.156.43.62]
4 86 ms 83 ms 60 ms be10.ksczksmp-ccr1.kc.rr.com [98.156.42.5]
5 58 ms 69 ms 61 ms ae30.hstntxl3-cr01.kc.rr.com [98.156.42.2]
6 59 ms 55 ms 72 ms agg1.dllatx10-cr02.texas.rr.com [24.175.49.9]
7 113 ms 60 ms 55 ms agg10.dllatx10-cr01.texas.rr.com [24.175.49.6]
8 72 ms 96 ms 52 ms xe-1-0-0.DLLUTXJR1CW.tx.twcbiz.com [71.40.237.85]
9 65 ms 67 ms 63 ms xe-1-0-0-0.RESERVED.tx.twcbiz.com [71.40.237.84]
10 56 ms 63 ms 55 ms agg10.dllatx10-cr02.texas.rr.com [24.175.49.7]
11 75 ms 59 ms 71 ms agg21.hstntxl3-cr01.texas.rr.com [24.175.49.8]
12 55 ms 56 ms 62 ms ae-4-0.cr0.hou30.tbone.rr.com [66.109.6.54]
13 69 ms 48 ms 65 ms ae-0-0.cr0.dfw10.tbone.rr.com [66.109.6.39]
14 * * 44 ms 107.14.17.232
15 89 ms 83 ms 111 ms xe-2-0-3.ar1.dfw1.us.nlayer.net [69.31.63.1]
16 66 ms 85 ms 63 ms 69.31.54.194
17 * 65 ms 63 ms quadranet-colocrossing.quadranet.com [96.44.148.54]
18 85 ms 80 ms 88 ms 4.1.2002.aggr.dal.colocrossing.com [207.210.254.246]
19 75 ms 79 ms 93 ms host.colocrossing.com [72.249.124.131]

East Server.

Tracing route to 206.217.143.131 over a maximum of 30 hops

1 468 ms 51 ms 36 ms cpe-65-26-16-1.kc.res.rr.com [65.26.16.1]
2 14 ms 10 ms 12 ms tge7-1.kscfmo11-cer1.kc.rr.com [65.28.16.34]
3 18 ms 31 ms 15 ms tge0-10-0-4.ksczmogn-ccr1.kc.rr.com [98.156.43.60]
4 47 ms 23 ms 32 ms ae30.dllatxl3-cr01.kc.rr.com [98.156.42.0]
5 29 ms 23 ms 31 ms ae-8-0.cr0.dfw10.tbone.rr.com [66.109.6.52]
6 * 26 ms 25 ms 107.14.17.234
7 86 ms 62 ms 63 ms xe-2-0-3.ar1.dfw1.us.nlayer.net [69.31.63.1]
8 68 ms 51 ms 76 ms ae0-60g.cr1.dfw1.us.nlayer.net [69.31.63.125]
9 57 ms 55 ms 48 ms xe-1-1-0.cr1.iah1.us.nlayer.net [69.22.142.2]
10 51 ms 61 ms 73 ms xe-4-2-1.cr1.atl1.us.nlayer.net [69.22.142.118]
11 53 ms 57 ms 56 ms as36352.xe-4-0-1-107.cr1.atl1.us.nlayer.net [69.31.135.94]
12 53 ms 54 ms 57 ms 206.217.143.131

i do not know what this means really.. or how to get the ping statistics like Rad got..

i have always pinged much better to dallas than to any atlanta server.. until the new servers i think

**iLLusioN** · 04-11-13, 08:54 PM

looks like your nlayer hop is the problem as well for the dallas server. ATL looks good though.

**StrickeN** · 04-11-13, 09:22 PM

anything i can do about that nlayer hop problem? i read earlier about talking to Time Warner possibly? what would i tell them lol

**iLLusioN** · 04-11-13, 10:01 PM

They should have a support section on their site somewhere that you can either email a ticket in or talk to a rep...do whichever you'd prefer...give them a brief description of your problem(latency reaching remote server) and attach the tracert(highlight or bold the bad hop) and they should go with it from there...if they need any other information they should contact you.

**Rad** · 04-16-13, 08:53 PM

Old route to CENTRAL

1 <1 ms <1 ms <1 ms xxxxx
2 * * * Request timed out.
3 10 ms 9 ms 8 ms xxxxx
4 17 ms 15 ms 15 ms tge0-10-0-4.lsvqkydb-ccr01.mwrtn.rr.com [65.29.25.134]
5 25 ms 22 ms 23 ms network-065-189-140-166.mwrtn.rr.com [65.189.140.166]
6 34 ms 30 ms 31 ms ae10-0.cr0.dca20.tbone.rr.com [107.14.19.14]
7 31 ms 31 ms 32 ms 107.14.19.135
8 34 ms 33 ms 29 ms xe-2-0-5.ar1.iad1.us.nlayer.net [69.31.30.65]
9 30 ms 30 ms 30 ms ae3-30g.cr2.iad1.us.nlayer.net [69.31.31.157]
10 46 ms 66 ms 44 ms xe-3-3-0.cr1.atl1.us.nlayer.net [69.22.142.105]
11 79 ms 80 ms 80 ms xe-0-0-3.cr1.iah1.us.nlayer.net [69.22.142.117]
12 83 ms 100 ms 83 ms xe-3-1-1.cr1.dfw1.us.nlayer.net [69.22.142.3]
13 84 ms 80 ms 74 ms ae1-50g.ar1.dfw1.us.nlayer.net [69.31.63.126]
14 244 ms 207 ms 229 ms 69.31.54.194
15 91 ms 92 ms 90 ms quadranet-colocrossing.quadranet.com [96.44.148.54]
16 92 ms 92 ms 90 ms 4.1.2002.aggr.dal.colocrossing.com [207.210.254.246]
17 94 ms 91 ms 90 ms host.colocrossing.com [72.249.124.131]

New route to CENTRAL

1 <1 ms <1 ms <1 ms xxxxx
2 * * * Request timed out.
3 11 ms 11 ms 9 ms xxxxx
4 16 ms 15 ms 16 ms tge0-10-0-3.lsvmkyzo-ccr01.mwrtn.rr.com [65.29.25.140]
5 25 ms 23 ms 22 ms network-065-189-140-162.mwrtn.rr.com [65.189.140.162]
6 34 ms 30 ms 31 ms ae-9-0.cr0.chi30.tbone.rr.com [107.14.19.16]
7 35 ms 31 ms 31 ms ae-0-0.cr0.chi10.tbone.rr.com [66.109.6.20]
8 30 ms 29 ms 28 ms 107.14.17.194
9 69 ms 70 ms 58 ms xe-4-0-5.ar2.ord1.us.nlayer.net [69.31.110.209]
10 67 ms 67 ms 67 ms ae4-52.cr1.ord1.us.nlayer.net [69.31.111.145]
11 54 ms 55 ms 54 ms xe-3-3-0.cr1.dfw1.us.nlayer.net [69.22.142.5]
12 56 ms 62 ms * ae1-50g.ar1.dfw1.us.nlayer.net [69.31.63.126]
13 59 ms 58 ms 59 ms 69.31.54.194
14 59 ms 59 ms 59 ms quadranet-colocrossing.quadranet.com [96.44.148.54]
15 61 ms 59 ms 60 ms 4.1.2002.aggr.dal.colocrossing.com [207.210.254.246]
16 59 ms 59 ms 59 ms host.colocrossing.com [72.249.124.131]

Old average latency: 90ms
New average latency: 60ms

The route has also improved for Atlanta. Stricken, does their adjustment by chance (with nlayer routing) also fix your issue?

**StrickeN** · 04-16-13, 09:13 PM

I actually talked to Time Warner last Thursday and they messed with my connection. They had it fixed Thursday night and i was average pinging 50 or so on Saturday.

Now logging back onto the new routed server, it is back to being average ping of 85 or so... Its like it undid the fix or something, idk.

New Central Server Routing::

Tracing route to host.colocrossing.com [72.249.124.131]
over a maximum of 30 hops:

1 36 ms 27 ms 39 ms cpe-65-26-16-1.kc.res.rr.com [65.26.16.1]
2 12 ms 11 ms 9 ms tge7-1.kscfmo11-cer2.kc.rr.com [65.28.16.38]
3 55 ms 55 ms 55 ms tge0-10-0-4.ksczksmp-ccr1.kc.rr.com [98.156.43.68]
4 62 ms 63 ms 63 ms ae30.hstntxl3-cr01.kc.rr.com [98.156.42.2]
5 53 ms 55 ms 55 ms agg1.dllatx10-cr02.texas.rr.com [24.175.49.9]
6 55 ms 63 ms 55 ms agg10.dllatx10-cr01.texas.rr.com [24.175.49.6]
7 96 ms 57 ms 54 ms xe-1-0-0.DLLUTXJR1CW.tx.twcbiz.com [71.40.237.85]
8 60 ms 63 ms 72 ms xe-1-0-0-0.RESERVED.tx.twcbiz.com [71.40.237.84]
9 91 ms 56 ms 55 ms agg10.dllatx10-cr02.texas.rr.com [24.175.49.7]
10 54 ms 55 ms 63 ms agg21.hstntxl3-cr01.texas.rr.com [24.175.49.8]
11 58 ms 55 ms 55 ms ae-4-0.cr0.hou30.tbone.rr.com [66.109.6.54]
12 49 ms 63 ms 47 ms ae-0-0.cr0.dfw10.tbone.rr.com [66.109.6.39]
13 45 ms 46 ms 42 ms 107.14.17.232
14 86 ms 84 ms 106 ms xe-2-0-3.ar1.dfw1.us.nlayer.net [69.31.63.1]
15 65 ms 83 ms 66 ms 69.31.54.194
16 67 ms 65 ms 64 ms quadranet-colocrossing.quadranet.com [96.44.148.54]
17 99 ms 85 ms 79 ms 4.1.2002.aggr.dal.colocrossing.com [207.210.254.246]
18 64 ms 67 ms 66 ms host.colocrossing.com [72.249.124.131]

**Kanati** · 04-16-13, 11:48 PM

But the fact that they had it "fixed" implies it's not the server.

**StrickeN** · 04-17-13, 12:26 AM

i don't think i ever said it was the server. i have no idea what it is. just what the problem shows on my end.... ping lag. the guy at time warner said it had something to do with nslayer and that time warner is working with them to solve nslayer's problem. idk