How to run a tracert?

Pistdoff - Archosaur

How can i run a tracert as nothing on Sylens post quite explains what i got to type to run one.

Archosaur has been rocking 20k+ ping all day for only a few people and theyre based in different parts of the world. Want to check whats causing mine but idk what command to type.

thanks.

Mayfly - Dreamweaver

First you need to open up a command window, by typing "cmd" or "command" into the Run line of the start menu (windows 7 or prior) or the Search line on the menu that pops up on the right of your screen when you drag the mouse to the upper or lower right corners (windows 8 or later.)

In that window you type "tracert <insert URL or IP of target server here>". Unfortunately I don't have a list of the PWI server URLs, and there isn't one in Sylen's sticky. I know there are posts with the URLs somewhere on the forum, I just don't know where.

NRGLG - Heavens Tear

I posted all of the servers here -> http://pwi-forum.perfectworld.com/showpost.php?p=22397321

---

If you're on a Unix based system, most use "traceroute [insert address or domain here without brackets]". Windows specifically uses "tracert [insert address or domain here without brackets]".

Pistdoff - Archosaur

NRGLG - Heavens Tear wrote: »

I posted all of the servers here -> http://pwi-forum.perfectworld.com/showpost.php?p=22397321

I play on Archo and you havent got that on the list xD

opkossy

Sanctuary (PvE) (pwigc2.perfectworld.com)

64.74.134.24:29000
64.74.134.25:29000
64.74.134.47:29000
64.74.134.48:29000
64.74.134.49:29000
64.74.134.50:29000
64.74.134.51:29000
64.74.134.52:29000


Lost City (PvP) (pwigc3.perfectworld.com)

64.74.134.31:29000
64.74.134.32:29000
64.74.134.53:29000
64.74.134.54:29000
64.74.134.55:29000
64.74.134.56:29000
64.74.134.57:29000
64.74.134.58:29000


Heaven's Tear (PvE) (pwigc4.perfectworld.com)

64.74.134.38:29000
64.74.134.39:29000
64.74.134.59:29000
64.74.134.60:29000
64.74.134.61:29000
64.74.134.62:29000
64.74.134.63:29000
64.74.134.64:29000


Archosaur (PvE) (pwiwest4.perfectworld.com)

64.74.134.26:29000
64.74.134.27:29000
64.74.134.29:29000
64.74.134.30:29000
64.74.134.33:29000
64.74.134.34:29000
64.74.134.36:29000
64.74.134.37:29000


East Coast USA Game Servers:

Harshlands (PvP) (pwieast1.perfectworld.com)

74.201.183.17:29000
74.201.183.18:29000
74.201.183.19:29000
74.201.183.20:29000


Dreamweaver (PvE) (pwieast2.perfectworld.com)

74.201.183.24:29000
74.201.183.25:29000
74.201.183.26:29000
74.201.183.27:29000


Raging Tide (PvE) (pwieast3.perfectworld.com)

74.201.183.66:29000
74.201.183.67:29000
74.201.183.68:29000
74.201.183.69:29000


European Game Servers:

Morai (PvE) (pwieu3.en.perfectworld.eu)

69.174.40.83:29000
69.174.40.84:29000
69.174.40.85:29000
69.174.40.86:29000

Pistdoff - Archosaur

Thanks. This is the result.

C:\Users\Kyle>
C:\Users\Kyle>tracert pwiwest4.perfectworld.com

Tracing route to pwiwest4.perfectworld.com [66.151.133.73]
over a maximum of 30 hops:

1 3 ms 5 ms 3 ms 192.168.0.1
2 18 ms 17 ms 25 ms host-78-145-240-1.as13285.net [78.145.240.1]
3 17 ms 19 ms 18 ms host-78-151-230-145.as13285.net [78.151.230.145]

4 18 ms 19 ms 19 ms host-78-151-230-146.as13285.net [78.151.230.146]

5 39 ms 26 ms 29 ms host-78-144-0-69.as13285.net [78.144.0.69]
6 23 ms 24 ms 34 ms host-78-144-11-34.as13285.net [78.144.11.34]
7 24 ms 27 ms 82 ms xe-10-1-0.lon21.ip4.tinet.net [213.200.78.233]
8 259 ms 233 ms * xe-1-1-6.sjc10.ip4.gtt.net [89.149.186.206]
9 208 ms * * internap-gw.ip4.gtt.net [77.67.70.26]
10 204 ms 207 ms 206 ms border2.t8-1-bbnet2.sje004.pnap.net [66.151.144.
80]
11 209 ms 198 ms 197 ms perfectworld-10.border2.sje004.pnap.net [64.95.1
43.190]
12 207 ms 167 ms 166 ms 66.151.133.73

Trace complete.

C:\Users\Kyle>

NRGLG - Heavens Tear

Pistdoff - Archosaur wrote: »

I play on Archo and you havent got that on the list xD

It was on the list under Lost City. I'm partially dyslexic and that did not help when I put that list together. Sorry about that b:surrender

Pistdoff - Archosaur

So from looking at Sylens post, does this mean there is faults from regional gateway 8 all the way to PWI at every connection thing? Or just one fault at 8 which is causing a knock on effect of high ping?

Pistdoff - Archosaur

Pistdoff - Archosaur wrote: »

So from looking at Sylens post, does this mean there is faults from regional gateway 8 all the way to PWI at every connection thing? Or just one fault at 8 which is causing a knock on effect of high ping?

Ah no problem mate.

NRGLG - Heavens Tear

Pistdoff - Archosaur wrote: »

So from looking at Sylens post, does this mean there is faults from regional gateway 8 all the way to PWI at every connection thing? Or just one fault at 8 which is causing a knock on effect of high ping?

Pretty sure it's just that particular hub. I think it's causing a spike for the rest of them. You could try the program I mentioned in my other post and it will give more detailed information. Optionally, you could start pinging the hub that seems faulty manually. If if fails to respond you will then have proof of packet loss.

"ping 89.149.186.206 -n -1"

Press Ctrl+C to cancel. You could do this for any of the addresses, just replace the "89.149.186.206" with one of the other IPs from the list.

Edit: If you use the program mentioned in my other post, it'd be better to save a sample set, not take a picture. Not really sure why I wrote to take a picture. A sample set would be 100x better.

Pistdoff - Archosaur

NRGLG - Heavens Tear wrote: »

Pretty sure it's just that particular hub. I think it's causing a spike for the rest of them. You could try the program I mentioned in my other post and it will give more detailed information. Optionally, you could start pinging the hub that seems faulty manually. If if fails to respond you will then have proof of packet loss.

"ping 89.149.186.206 -n -1"

Press Ctrl+C to cancel. You could do this for any of the addresses, just replace the "89.149.186.206" with one of the other IPs from the list.

8 259 ms 233 ms * xe-1-1-6.sjc10.ip4.gtt.net [89.149.186.206]

I just got my gf (who lives in Norway) to run a tracert and her tracert came back with this exact same name, just my ms numbers were slightly higher. Id assume were connecting through same gateway which is causing the lagg for some and not all?

Tried the ping you mentioned.

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

C:\Users\Kyle>ping 89.149.186.206 -n -1

Pinging 89.149.186.206 with 32 bytes of data:
Request timed out.
Reply from 89.149.186.206: bytes=32 time=216ms TTL=51
Reply from 89.149.186.206: bytes=32 time=216ms TTL=51
Reply from 89.149.186.206: bytes=32 time=215ms TTL=51
Reply from 89.149.186.206: bytes=32 time=215ms TTL=51
Reply from 89.149.186.206: bytes=32 time=230ms TTL=51
Request timed out.
Reply from 89.149.186.206: bytes=32 time=198ms TTL=51
Reply from 89.149.186.206: bytes=32 time=198ms TTL=51
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 89.149.186.206:
Packets: Sent = 12, Received = 7, Lost = 5 (41% loss),
Approximate round trip times in milli-seconds:
Minimum = 198ms, Maximum = 230ms, Average = 212ms
Control-C
^C
C:\Users\Kyle>

NRGLG - Heavens Tear

Thank you very much, that ping was (more-or-less) proof that the hub is failing. Try pinging the address before that one; which is "213.200.78.233". Just want to see if no packet loss is occurring before it reaches that address.

Pistdoff - Archosaur

NRGLG - Heavens Tear wrote: »

Thank you very much, that ping was (more-or-less) proof that the hub is failing. Try pinging the address before that one; which is "213.200.78.233". Just want to see if no packet loss is occurring before it reaches that address.

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

C:\Users\Kyle>ping 213.200.78.233 -n -1

Pinging 213.200.78.233 with 32 bytes of data:
Reply from 213.200.78.233: bytes=32 time=34ms TTL=55
Reply from 213.200.78.233: bytes=32 time=25ms TTL=55
Reply from 213.200.78.233: bytes=32 time=23ms TTL=55
Reply from 213.200.78.233: bytes=32 time=26ms TTL=55
Reply from 213.200.78.233: bytes=32 time=26ms TTL=55
Reply from 213.200.78.233: bytes=32 time=25ms TTL=55
Reply from 213.200.78.233: bytes=32 time=24ms TTL=55
Reply from 213.200.78.233: bytes=32 time=25ms TTL=55
Reply from 213.200.78.233: bytes=32 time=25ms TTL=55

Ping statistics for 213.200.78.233:
Packets: Sent = 9, Received = 9, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 23ms, Maximum = 34ms, Average = 25ms
Control-C
^C
C:\Users\Kyle>

NRGLG - Heavens Tear

Thank you. Okay, with that I can confirm that the issue is at a random hub over the internet. There is a delay between 213.200.78.233 and 89.149.186.206 that is causing this. I live near the west servers and pinging 89.149.186.206, the results were excellent. On the other hand 213.200.78.233 was very laggy for me. So I'm going to assume both hubs are a fair distance from one another which could mean there are a number of things that could go wrong.

Sadly this is something you and I cannot fix, just stair at from a distance and sigh until it resolves itself.

Pistdoff - Archosaur

NRGLG - Heavens Tear wrote: »

Thank you. Okay, with that I can confirm that the issue is at a random hub over the internet. There is a delay between 213.200.78.233 and 89.149.186.206 that is causing this. I live near the west servers and pinging 89.149.186.206, the results were excellent. On the other hand 213.200.78.233 was very laggy for me. So I'm going to assume both hubs are a fair distance from one another which could mean there are a number of things that could go wrong.

Sadly this is something you and I cannot fix, just stair at from a distance and sigh until it resolves itself.

Yeah thats what i assumed was the problem when i pinged the second time. I play from the UK and her from Norway. The problem is affecting others too (some live in US, some in asia, and they have same problem. Ill just try again in a couple hours before the TW and hopefully itll be resolved by then.

Thanks for your patience and help.

SylenThunder - Twilight Temple

That hub causing the issue is the regional international routing hub in Los Angeles. It's been a real issue lately.

Sadly there is really not anything you, or PWE can do about it.
Sometimes, completely resetting your ISP connection, flushing your DNS cash and TCP stack, will give you a different route if you originate in the US, or your signal is travelling across the US from the East. It's not very often you can get routed through the Washington/Oregon hubs though, but it's pretty nice when you can.

NRGLG - Heavens Tear

I blame constantly connected cellphones for all of the worlds internet problems. That and idiots who run mass DDoSes. Poor lil hubs can't handle it and have to sob for a while. That's where latency comes from. b:laugh