shaitan Posted May 5, 2014 Posted May 5, 2014 Since the 208.115.205.106 pc that hosts KF/Renegade/TS has been dropping so much lately, the host is asking for traceroute's. When it lags you out like it has been doing, do this please and paste the results: Open command prompt, type this in: tracert 208.115.205.106 To easily save it, click the top left, scroll down and find EDIT, then SELECT ALL. Once it's "selected" just hit ENTER. It's copied, then you can paste it at pastebin.com.
OSTKRailiak Posted May 6, 2014 Posted May 6, 2014 http://pastebin.com/qdxXvWJ3 someone shits on the network cluster -.-
shaitan Posted May 6, 2014 Author Posted May 6, 2014 I hope you guys are doing this right after a bunch of people lagout.
shaitan Posted May 6, 2014 Author Posted May 6, 2014 I moved your topic to mine craft, because I want people to read this one rail I(in case you wondered).
DrSithis Posted May 6, 2014 Posted May 6, 2014 To confirm, the ones timing out between lines 12-14 are BlackLotus IPs. They won't respond because they don't allow ICMP requests
OSTKRailiak Posted May 6, 2014 Posted May 6, 2014 I know ^^ But if you look at hop 7 - 11. It looks like the dallas cluster is busy.
DrSithis Posted May 6, 2014 Posted May 6, 2014 That Dallas cluster is always busy for some reason. Raises questions for the Limestone Datacenter's network load and latency there.
Nowherekid Posted May 7, 2014 Posted May 7, 2014 Edit: missed the pastebin part http://pastebin.com/cdiS30pw tracert 208.115.205.116Tracing route to 116-205-115-208.static.reverse.lstn.net [208.115.205.116]over a maximum of 30 hops: 1 1 ms <1 ms <1 ms 192.168.1.1 2 9 ms 16 ms 9 ms 10.253.0.1 3 9 ms 11 ms 8 ms 173-219-249-22-link.sta.suddenlink.net [173.219.249.22] 4 22 ms 21 ms 22 ms 173-219-249-248-link.sta.suddenlink.net [173.219.249.248] 5 25 ms 23 ms 25 ms 173-219-227-45-link.sta.suddenlink.net [173.219.227.45] 6 22 ms 22 ms 21 ms dls-bb1-link.telia.net [213.248.90.101] 7 30 ms 24 ms 30 ms limestone-ic-135964-dls-bb1.c.telia.net [213.248.74.222] 8 22 ms 24 ms 37 ms te5-1.bdr1.core2.dllstx3.dallas-idc.com [208.115.192.54] 9 23 ms 23 ms 23 ms ge0-2.vl285.cr01-103.dllstx3.dallas-idc.com [208.115.249.222] 10 33 ms 26 ms 27 ms 116-205-115-208.static.reverse.lstn.net [208.115.205.116]Trace complete.
shaitan Posted May 7, 2014 Author Posted May 7, 2014 Microsoft Windows [Version 6.1.7601]Copyright (c) 2009 Microsoft Corporation. All rights reserved.C:UsersJoel>tracert 208.115.205.106Tracing route to 106-205-115-208.static.reverse.rencorner.co [208.115.205.106]over a maximum of 30 hops: 1 1 ms 1 ms <1 ms 192.168.1.1 2 * * * Request timed out. 3 13 ms 13 ms 11 ms te-9-2-ur01.centralcity.pa.pitt.comcast.net [68.85.234.201] 4 13 ms 10 ms 11 ms te-8-3-ur01.adams.pa.pitt.comcast.net [68.85.75.70] 5 14 ms 15 ms 13 ms te-0-9-0-7-ar03.mckeesport.pa.pitt.comcast.net [68.87.173.126] 6 20 ms 20 ms 22 ms he-4-4-0-0-cr01.ashburn.va.ibone.comcast.net [68.86.94.161] 7 18 ms 20 ms 18 ms he-0-12-0-0-pe07.ashburn.va.ibone.comcast.net [68.86.83.82] 8 64 ms 76 ms 19 ms dcx2-edge-01.inet.qwest.net [65.120.84.65] 9 * * * Request timed out. 10 59 ms 58 ms 59 ms 216-207-54-74.dia.static.qwest.net [216.207.54.74] 11 62 ms 59 ms 61 ms te5-1.bdr1.core1.dllstx3.dallas-idc.com [208.115.192.50] 12 58 ms 59 ms 58 ms ge1-0.vl384.cr03-122.dllstx3.dallas-idc.com [64.31.3.106] 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 * * * Request timed out. 25 * * * Request timed out. 26 * * * Request timed out. 27 * * * Request timed out. 28 * * * Request timed out. 29 * * * Request timed out. 30 * * * Request timed out.Trace complete.C:UsersJoel>
Lundy004 Posted May 7, 2014 Posted May 7, 2014 From Columbus, Ohio tracert 208.115.205.116 Tracing route to 106-205-115-208.static.reverse.rencorner.co [208.115.205.106] over a maximum of 30 hops: 1 10 ms 14 ms 14 ms cpe-98-28-116-1.columbus.res.rr.com [98.28.116.1 ] 2 16 ms 10 ms 14 ms agg21-1644.clmcohib01r.midwest.rr.com [184.59.24 2.70] 3 42 ms 29 ms 20 ms 65.189.107.12 4 36 ms 13 ms 26 ms tge8-8.wasnohbd-cer01.div.midohio.rr.com [65.189 .107.21] 5 19 ms 27 ms 21 ms aolclient-24-33-160-112.woh.res.rr.com [24.33.16 0.112] 6 31 ms 48 ms 29 ms 65.29.1.34 7 54 ms 31 ms 31 ms ae-4-0.cr0.chi30.tbone.rr.com [66.109.6.68] 8 29 ms 31 ms 27 ms ae-0-0.cr0.chi10.tbone.rr.com [66.109.6.20] 9 * * * Request timed out. 10 30 ms 27 ms * 66.109.11.18 11 26 ms 28 ms 50 ms ae4.cr2.ord2.us.above.net [64.125.20.41] 12 55 ms 51 ms 73 ms xe-0-3-0.cr2.dfw2.us.above.net [64.125.31.78] 13 100 ms 54 ms 52 ms xe-0-2-0.mpr1.dfw1.us.above.net [64.125.27.213] 14 64 ms 51 ms 54 ms 64.125.188.182.t00822-03.above.net [64.125.188.1 82] 15 60 ms 56 ms 51 ms te6-1.bdr2.core1.dllstx3.dallas-idc.com [208.115 .192.58] 16 78 ms 52 ms 53 ms ge1-0.vl384.cr03-122.dllstx3.dallas-idc.com [64. 31.3.106] 17 * * * Request timed out. 18 * * * Request timed out. 19 * * * Request timed out. 20 * * * Request timed out. 21 * * * Request timed out. 22 *
Dragon1932 Posted May 7, 2014 Posted May 7, 2014 Microsoft Windows [Version 6.2.9200] © 2012 Microsoft Corporation. All rights reserved. C:UsersDragon>tracert 208.115.205.106 Tracing route to 106-205-115-208.static.reverse.rencorner.co [208.115.205.106] over a maximum of 30 hops: 1 3 ms 5 ms 1 ms router.belkin [192.168.2.1] 2 21 ms 12 ms 12 ms cpe-72-129-112-1.socal.res.rr.com [72.129.112.1] 3 20 ms 16 ms 14 ms 76.167.31.73 4 31 ms 13 ms 15 ms tge0-10-0-11.chwocadq02r.socal.rr.com [72.129.25 .202] 5 28 ms 25 ms 23 ms agg24.tustcaft01r.socal.rr.com [72.129.25.2] 6 23 ms 30 ms 19 ms 107.14.19.30 7 55 ms 17 ms 48 ms ae3.pr1.lax10.tbone.rr.com [107.14.19.56] 8 18 ms 23 ms 18 ms fxp0.a0.mia95.adelphiacom.net [66.109.7.38] 9 28 ms 16 ms 19 ms xe-2-2-0.cr2.lax112.us.above.net [64.125.31.194] 10 56 ms 60 ms 55 ms ae4.cr2.iah1.us.above.net [64.125.25.54] 11 82 ms 54 ms 56 ms ae1.cr2.dfw2.us.above.net [64.125.21.137] 12 212 ms 52 ms 56 ms xe-0-2-0.mpr1.dfw1.us.above.net [64.125.27.213] 13 55 ms 52 ms 63 ms 64.125.188.182.t00822-03.above.net [64.125.188.1 82] 14 56 ms 54 ms 58 ms te6-1.bdr2.core2.dllstx3.dallas-idc.com [208.115 .192.62] 15 61 ms 55 ms 55 ms ge1-1.vl385.cr03-122.dllstx3.dallas-idc.com [64. 31.3.110] 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 * * * Request timed out. 25 * * * Request timed out. 26 * * * Request timed out. 27 * * * Request timed out. 28 * * * Request timed out. 29 * * * Request timed out. 30 * * * Request timed out. Trace complete. C:UsersDragon>
shaitan Posted May 7, 2014 Author Posted May 7, 2014 Thank you guys for posting these. Handing them in to the limestone.. so they have an excuse to look into it now. >;p
DrSithis Posted May 7, 2014 Posted May 7, 2014 Thank you guys for posting these. Handing them in to the limestone.. so they have an excuse to look into it now. >;p And then again the Dallas IDC Cluster seems to be fine. That looks average for being under 60ms.
Nowherekid Posted July 15, 2014 Posted July 15, 2014 There was some massive server lag today so i ran tracert during the lag and after it cleared up. With a complimentary ping http://pastebin.com/xgeZ4fZr
OSTKRailiak Posted July 15, 2014 Posted July 15, 2014 There was some massive server lag today so i ran tracert during the lag and after it cleared up. With a complimentary ping http://pastebin.com/xgeZ4fZr Yes, i did it also but the ping was good (normal). It was something else. idk. Entropy joined and all was fine again. I asked him, he dont answered but it looked like he did nothing and all went fine automaticly. BUT Entropy was there in seconds!! Thank you Entro
Nowherekid Posted October 24, 2014 Posted October 24, 2014 Microsoft Windows [Version 6.1.7601] Copyright © 2009 Microsoft Corporation. All rights reserved. C:\Users\Alix>tracrt 208.115.205.106 'tracrt' is not recognized as an internal or external command, operable program or batch file. C:\Users\Alix>tracert 208.115.205.106 Tracing route to 106-205-115-208.static.reverse.rencorner.co [208.115.205.106] over a maximum of 30 hops: 1 1 ms <1 ms <1 ms 192.168.1.1 2 7 ms 11 ms 7 ms 10.253.0.1 3 8 ms 10 ms 7 ms 173-219-249-22-link.sta.suddenlink.net [173.219. 249.22] 4 22 ms 20 ms 23 ms 173-219-249-248-link.sta.suddenlink.net [173.219 .249.248] 5 19 ms 22 ms 19 ms 173-219-229-203-link.sta.suddenlink.net [173.219 .229.203] 6 17 ms 20 ms 19 ms dls-bb1-link.telia.net [213.248.90.101] 7 18 ms 23 ms 20 ms dls-bb1-link.telia.net [62.115.140.244] 8 19 ms 19 ms 19 ms limestone-ic-135964-dls-bb1.c.telia.net [213.248 .74.222] 9 21 ms 23 ms 21 ms te5-1.bdr1.core1.dllstx3.dallas-idc.com [208.115 .192.50] 10 20 ms 23 ms 20 ms ge1-0.vl384.cr03-122.dllstx3.dallas-idc.com [64. 31.3.106] 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 * * * Request timed out. 25 * * * Request timed out. 26 * * * Request timed out. 27 * * * Request timed out. 28 * * * Request timed out. 29 * * * Request timed out. 30 * * * Request timed out. Trace complete. C:\Users\Alix>
BillieJoe67 Posted October 25, 2014 Posted October 25, 2014 Please read the date of the last post.. saying nice bump is too mainstream
vlatkozelka Posted October 25, 2014 Posted October 25, 2014 Please read the date of the last post.. saying nice bump is too mainstream whats wrong with mainstream ... man too much going against mainstream gave birth to shit like lady gaga and justin beiber :/
shaitan Posted October 25, 2014 Author Posted October 25, 2014 He was one of two who actually did this when I asked lastnight.
shaitan Posted October 26, 2014 Author Posted October 26, 2014 We were lagging bad, put in a ticket(they said it was the pc, which it wasn't), gave those to Limestone to try and pinpoint it.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now