Getting Fed Up With D/C

[Raist]

https://us.battle.net/support/en/art...g-a-traceroute

A how-to for running/interpreting a tracert and such to Blizzard's servers. Apply the concepts to this games servers. There is one exception to the guide, and that is in regards to dumping it to a text file. To make it just display the text on the screen, remove everything after the server address in there example, so it would be "tracert xxx.xxx.xxx". The command they give dumps the results to a text file with no output to the screen, and it will overwrite the file each time you run it. Dumping it to a file like that means you have to open the file to read it, and since it is in a protected location you have to use Admin privileges to edit or rename it.

Alternatively, you can put in an extra > in the command to make it append results each time instead, so it would read "tracert xxx.xxx.xxx >>c:\tracert.txt" instead (>> versus >). Also note that you can make that path and file name anything you want. For example, you can create a folder called FFXIVTRACE at the root of your C:drive, and point the command to C:\FFXIVTRACE\tracert.txt to put it in a file within that folder. This will remove the need to run the CMD prompt as admin, since it won't be at the root of the C:\ drive...which also means you could save the command in a .BAT file and run it from the desktop at will.

If you opt to just display it on the screen with the "tracert xxx.xxx.xxx" command, to copy/paste the text into an email or text file to save it, just right-click anywhere within the DOS window. A context menu should pop up to allow you to Mark or Select All. Mark will allow you to click/drag over text to highlight it, while Select All will highlight all text from the session. At that point, hitting just the <ENTER> key will copy all the highlighted text to clipboard. Then you can use your normal pasting method to put it in an email or text document as you see fit.

If you don't know the IP address of your server, you can use the registered DNS names of the lobby servers (they are in the same subnet and all), or get the IP you actually play on by running the NETSTAT command from the same DOS window after you have logged fully into the game. Netstat will display a list of addresses, many may be in and TIME_WAIT state. You want to look at the ones that are ESTABLISHED. The servers in Canada currently all start with 199. We periodically may servers from up to 3 subnets in Japan at the moment, but the main ones for game play start with 124 (you may also see ones starting with 125 or 202 as well, depending on various circumstances).

Here are the DNS names for the current lobby servers, separated by region:

NA/EU (Canada)
neolobby02.ffxiv.com
neolobby04.ffxiv.com
neolobby06.ffxiv.com

Japan
neolobby01.ffxiv.com
neolobby03.ffxiv.com
neolobby05.ffxiv.com


If you find anything noteworthy in this process pertaining to anything before the SE IP addresses (the ones starting with 199 or 124). Check against other established servers/sites as well (Blizzard's servers, Google, Youtube, Twitch, etc.) as well to see if it is better/worse, then get in touch with your ISP's Tier3 support team. Forward your findings to them so they can conduct a proper investigation and <hopefully> pull in the proper people to address the routing issues.

It is very important that you are dealing specifically with Tier3 (sometimes referred to as Engineering). We are repeatedly seeing issues pertaining to our ISP's routing policies that determine how and with whom we are routed to get to SE's ISP. These are decisions made by our ISP's, but those are made and implemented by Tier3 techs or people higher up the administrative staff. As such, the lower tier guys (like the ones that answer the phone or come check your cables and such) cannot address such issues.