Jump to content
RenCorner Network

Tracert to new server


shaitan
 Share

Recommended Posts

Can u guys run traceroutes to the new pc? I got the info in the .rar here: http://208.115.205.106/progs/WinMTR.rar   
You just gotta run the ArkBox.bat one and paste/pastebin.com me the results -or- just do a CMD prompt and copy that:

tracert 144.217.10.189

tracert 208.115.205.106

I would like to have as many as possible.

 

  • Like 1
Link to comment
Share on other sites

Idaho Trace

Tracing route to ns539583.ip-144-217-10.net [144.217.10.189]
over a maximum of 30 hops:

  1    <1 ms     1 ms    <1 ms  TheNetwork [192.168.1.1]
  2    19 ms    17 ms    18 ms  boid-dsl-gw18.boid.qwest.net [184.99.64.18]
  3    15 ms    18 ms    16 ms  184-99-65-137.boid.qwest.net [184.99.65.137]
  4    27 ms    37 ms    39 ms  sea-brdr-03.inet.qwest.net [67.14.41.154]
  5    29 ms    37 ms    38 ms  4.68.75.121
  6     *        *        *     Request timed out.
  7   104 ms    97 ms    97 ms  sjo-sv5-bb1-a9.ca.us [142.44.208.133]
  8   108 ms    97 ms    98 ms  be100-1368.pao-sv8-bb1-a9.ca.us [178.32.135.158]
  9   106 ms    97 ms    97 ms  chi-5-a9.il.us [198.27.73.227]
 10   110 ms   116 ms    97 ms  be100-1324.bhs-g2-nc5.qc.ca [192.99.146.140]
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14   102 ms    97 ms    97 ms  ns539583.ip-144-217-10.net [144.217.10.189]

Trace complete.

 

Texas

Tracing route to 144.217.10.189 [144.217.10.189]...

hop rtt rtt rtt   ip address fully qualified domain name
1 0 0 0   208.101.16.73 outbound.hexillion.com
2 0 0 0   66.228.118.153 ae11.dar01.sr01.dal01.networklayer.com
3 * * *      
4 0 0 0   50.97.17.57 ae34.bbr01.eq01.dal03.networklayer.com
5 * * *      
6 22 22 22   178.32.135.152 be100-1241.chi-5-a9.il.us
7 39 39 39   192.99.146.140 be100-1324.bhs-g2-nc5.qc.ca
8 * * *      
9 * * *      
10 * * *      
11 38 38 38   144.217.10.189 ns539583.ip-144-217-10.net

Trace complete

 

Always reaching the destination but Lots of hops not responding to pings but those routers could not respond to pings. See ping time outs here and there avg 100ms for me.

Ping statistics for 144.217.10.189:
    Packets: Sent = 542, Received = 539, Lost = 3 (0% loss),

Minimum = 80ms, Maximum = 163ms, Average = 102ms

 

Link to comment
Share on other sites

Tracing route to ns539583.ip-144-217-10.net [144.217.10.189]
over a maximum of 30 hops:

  1     1 ms    <1 ms     1 ms  192.168.1.1
  2    25 ms    20 ms     7 ms  10.175.16.1
  3    12 ms     *       12 ms  172.18.8.30
  4    15 ms    13 ms    13 ms  172.17.0.6
  5     *        *        *     Request timed out.
  6     *       14 ms     *     BB-H2-B31.231-HFA-HOT-100G.hotnet.net.il [213.57.3.112]
  7     *        *        *     Request timed out.
  8    76 ms    65 ms    64 ms  ldn-b5-link.telia.net [62.115.161.58]
  9    74 ms    71 ms    72 ms  be100-159.ldn-5-a9.uk.eu [37.187.231.112]
 10   150 ms   135 ms   135 ms  be100-1298.nwk-5-a9.nj.us [192.99.146.133]
 11   142 ms   142 ms   141 ms  be100-1323.bhs-g2-nc5.qc.ca [192.99.146.138]
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15   143 ms   138 ms   138 ms  ns539583.ip-144-217-10.net [144.217.10.189]

Trace complete.

Link to comment
Share on other sites

Routenverfolgung zu ns539583.ip-144-217-10.net [144.217.10.189] über maximal 30 Abschnitte:

  1    <1 ms    <1 ms    <1 ms  speedport.ip [192.168.2.1]
  2     5 ms     5 ms     5 ms  62.155.240.100
  3    13 ms    15 ms    15 ms  217.239.48.194
  4    14 ms    14 ms    14 ms  be100-162.fra-5-a9.de.eu [37.187.232.98]
  5    24 ms    23 ms    23 ms  be103.rbx-g2-nc5.fr.eu [94.23.122.240]
  6     *        *        *     Zeitüberschreitung der Anforderung.
  7   124 ms   122 ms   115 ms  vl1305.bhs-d2-a75.qc.ca [213.251.128.1]
  8     *        *        *     Zeitüberschreitung der Anforderung.
  9     *        *        *     Zeitüberschreitung der Anforderung.
 10   122 ms   123 ms   123 ms  ns539583.ip-144-217-10.net [144.217.10.189]

Ablaufverfolgung beendet.

Link to comment
Share on other sites

Tracing route to ns539583.ip-144-217-10.net [144.217.10.189]
over a maximum of 30 hops:

  1     2 ms     4 ms    26 ms  192.168.0.1
  2    13 ms    36 ms    28 ms  10.40.112.1
  3    20 ms    26 ms    14 ms  brad-core-2a-xe-101-0.network.virginmedia.net [62.252.15.165]
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7    28 ms    37 ms    40 ms  tcl5-ic-6-ae0-0.network.virginmedia.net [62.254.85.66]
  8     *        *        *     Request timed out.
  9   124 ms   171 ms   164 ms  be100-1298.nwk-5-a9.nj.us [192.99.146.133]
 10   211 ms   244 ms   139 ms  be100-1323.bhs-g2-nc5.qc.ca [192.99.146.138]
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14   142 ms   122 ms   120 ms  ns539583.ip-144-217-10.net [144.217.10.189]

Trace complete.

 

Link to comment
Share on other sites

C:\WINDOWS\system32>tracert 144.217.10.189

Détermination de l’itinéraire vers ns539583.ip-144-217-10.net [144.217.10.189]
avec un maximum de 30 sauts :

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    11 ms    11 ms    11 ms  107-190-35-33.cpe.teksavvy.com [107.190.35.33]
  3    11 ms    13 ms    11 ms  10.170.192.58
  4    13 ms    10 ms    11 ms  xe-2-2-0-0-bdr01-mtl.teksavvy.com [192.171.61.9]
  5    13 ms    13 ms    13 ms  206-248-189-97.dsl.teksavvy.com [206.248.189.97]
  6     *        *        *     Délai d’attente de la demande dépassé.
  7    16 ms    22 ms    13 ms  bhs-g2-nc5.qc.ca [142.44.208.175]
  8     *        *        *     Délai d’attente de la demande dépassé.
  9     *        *        *     Délai d’attente de la demande dépassé.
 10     *        *        *     Délai d’attente de la demande dépassé.
 11    15 ms    12 ms    13 ms  ns539583.ip-144-217-10.net [144.217.10.189]

Itinéraire déterminé.

Link to comment
Share on other sites

Those who have Killing Floor 2, Teamspeak 3, and Ark, please try and join the new IP's for testing(you can substitute the 144.217.10.189 for TS3 with ArkTerraria.rencorner.com):
KF2
I didn't have luck adding these to my favorites via the steam console, but they did show up easily enough in the regular server lists in the game.
Just uncheck 'limit results 1000', make sure the other things like 'hide passworded' is blank too. The difficulty will be 'Suicidal'. Look for 'Rencorner', should show 4 of them(title ending in "NewPC" are these ones).
Rencorner.com KF2 #1-NewPC: 144.217.10.189:9100
Rencorner.com KF2 #2-NewPC: 144.217.10.189:9120
https://www.gametracker.com/server_info/144.217.10.189:9100
https://www.gametracker.com/server_info/144.217.10.189:9120

Ark
These ones I was able to favorite by the steam console way:

Island:   144.217.10.189:8020
-or- 27031 -or- 28338
Ragnarok: 144.217.10.189:8030
-or- 27041 -or- 28358 

Teamspeak
144.217.10.189:9987

Link to comment
Share on other sites

6 hours ago, shaitan said:

Try that again sometime Joe, I think it had crashed.

nope!  I tried


144.217.10.189

144.217.10.189:9987

144.217.10.189:9100

 

Link to comment
Share on other sites

The Ark ones are not showing up. I had to change the port to make it show. Using the SERVER port 8020 didn't work so I had to use the QUERY port 27031 and add that to my favorites list for it to show. I've just tested the Island map and I can join. It will need the newest server profiles adding to it. The Island map which is highlighted is the one on the new box.

20190506152018_1.jpg

 

Screen Capture #717.pngScreen Capture #718.png

Link to comment
Share on other sites

19 minutes ago, Joetorp said:

nope!  I tried


144.217.10.189

144.217.10.189:9987

144.217.10.189:9100

 

I am trying that using ts3, I ain't going thru steam as I don't have an account, if that makes a difference

Link to comment
Share on other sites

Showing this error on the TS too.

[23:26] <&ice187dna> !ts users
[23:26] <&RCBOT> 7[TS3] Permission error! (error id=1024 msg=invalid serverID)
[23:26] <&RCBOT> 7[TS3] Please check if the bot has the required permissions to take the action that's needed.
[23:26] <&RCBOT> 7[TS3] If you don't know what could be causing this error message, please contact the author of the script. (!TS Version)
[23:26] <&RCBOT> 7[TS3] Permission error! (error id=1024 msg=invalid serverID)
[23:26] <&RCBOT> 7[TS3] Please check if the bot has the required permissions to take the action that's needed.
[23:26] <&RCBOT> 7[TS3] If you don't know what could be causing this error message, please contact the author of the script. (!TS Version)

Link to comment
Share on other sites

That's weird about the backup ts, it's an exact copy(but keeps crashing). Oh well, I put up the same backup from a month ago just now.

 

*edit* Ah, it looks like exact copies are the problem. It's sending both UID's to the Teamspeak people's database and kicking one offline. Edited that UID.

Try joining the new ip again sometime @Joetorp

Link to comment
Share on other sites

13 hours ago, Joetorp said:

144.217.10.189

144.217.10.189:9987

Ok, these work now... Port 9100 does not.

I also noticed I do not see "unread content" now... I get the notifications

Link to comment
Share on other sites

  • 1 month later...

*bump* can you guys get some of the WinMTR's for me? Use the Mara.bat one preferably. Pm me the results in pastebin.com if you want(here or discord).

Link to comment
Share on other sites

Tracing route to ns539583.ip-144-217-10.net [144.217.10.189]
over a maximum of 30 hops:

  1   415 ms    70 ms     2 ms  mynetwork [192.168.2.1]
  2    70 ms    20 ms    52 ms  loop0.57w.ba09.stjh.nf.aliant.net [142.163.63.12]
  3    68 ms    18 ms    25 ms  be14-181.dr01.stjh.nf.aliant.net [142.176.208.57]
  4   261 ms   462 ms   290 ms  be1.dr01.crbk.nf.aliant.net [142.166.149.126]
  5   201 ms   105 ms    79 ms  ae3-50.dr02.crbk.nf.aliant.net [142.166.181.54]
  6    38 ms    97 ms   119 ms  et-0-3-0.cr02.hlfx.ns.aliant.net [142.166.181.113]
  7   505 ms   107 ms    86 ms  hg-0-2-0-0-50.cr01.hlfx.ns.aliant.net [142.166.149.93]
  8    59 ms    64 ms   186 ms  be19.bx01.nycm.ny.aliant.net [207.231.227.110]
  9     *       54 ms    52 ms  lag-197.ear3.NewYork1.Level3.net [4.71.230.101]
 10   129 ms    53 ms    68 ms  be100-104.nwk-1-a9.nj.us [192.99.146.253]
 11   143 ms     *      257 ms  be100-1319.bhs-g1-nc5.qc.ca [198.27.73.204]
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15   495 ms   847 ms    59 ms  ns539583.ip-144-217-10.net [144.217.10.189]

Trace complete.

 

Hope it helps!

Link to comment
Share on other sites

See if the weird lag we've been getting is any better now. Limestone changed a few things in the firewall.

Link to comment
Share on other sites

2 hours ago, shaitan said:

See if the weird lag we've been getting is any better now. Limestone changed a few things in the firewall.

image.png

 

Link to comment
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...