The traceroute tool allows you to inspect the route path of Internet data packets between your computer and the World of Warcraft server, it also helps identify whether or not your connection is experiencing unusual latency issues. When using this program, you may determine exactly where the data packets transferred meet problems. Below you will find instructions on how to create a trace route in Windows and on Mac OSX.
How to create a trace route in Windows
When you are playing the game, press the Alt and Tab keys simultaneously
[ Windows XP ]
1. Click the Start menu and then Run
2. Type in cmd then press Enter

3. Continue to Step 4
[ If using Windows Vista or Windows 7 ]
1. Click Start and type cmd in the Search/Run field
2. The search should find a program called cmd.exe
3. Right-click on the cmd.exe program and left-click on Run as administrator
4. Type the following into the Command Window that appears:
netstat -n -p tcp -b | more

You will see a line like this one (depending on World of Warcraft):
TCP XXX.XX.XX.XX:XXXX YY.YYY.YYY.YY:3724 ESTABLISHED ZZZZ [WoW.exe]
The X is your IP address, please include this in your email with the information above.
The Y is the address of the server you are connecting to. The 4 digit numbers after the : in both cases indicate the port used. This may be 3724.
The Z is the process id for World of Warcraft on your computer.
5. Now we need some information on your connection, in the same command window, type in:
tracert YY.YYY.YYY.YY > C:\tracert.txt

Important: When using the address from the Netstat command above for YY.YYY.YYY.YY, ensure that you use the number values given and remove the :3724 from the end. A file will be created on your local drive (C:) called tracert.txt which will contain the trace route information. Please note that you must have administrator privileges on your C: drive in order to create this file.
How to create a trace route on Mac OSX
When you are playing, switch the game to windowed mode by pressing the Apple/Command and M keys simultaneously
1. Open the Finder, choose Applications and then Utilities

2. Run the Terminal program
3. In the Terminal window, type netstat -np tcp | grep 3724 and press Enter

You will see a line like this one:
tcp4 0 0 XX.X.X.XX.XXXX YY.YYY.YYY.YY.3724 ESTABLISHED
The Y information is the address of the server you are connecting to.
4. We can now create a trace route to your server using the Y address above In the Terminal window, type traceroute YY.YYY.YYY.YY > ~/Desktop/tracert.txt and press Enter

Important: When using the Y address from the netstat, ensure that you enter the number values given. A file will be created on your desktop called tracert.txt which will contain the trace route information. Please allow your computer 2-3 minutes to create the tracert.txt file before opening or moving the file.
I ran Trace Route, now what do I do?
Open the tracert.txt file. You will see 3 kinds of information regarding the route that internet traffic is taking from your computer to the realm you chose:
1) The number on the far left is the hop number. One hop (Hand over Point) is the router your data packets go through in order to reach the destination.
2) The next 3 numbers (with 'ms' after each one) is the length of time, in milliseconds, it takes for your computer to receive a response from the computer you are trying to contact. A high value, for example greater than 200 ms for broadband or 350 ms for dial-up indicates that traffic is slow, and can cause latency or 'laggy' play. Asterisks (*) indicate that your computer did not receive a response from the computer you are trying to contact at all, which can keep you from connecting to our servers all together, or cause you to be disconnected abruptly. However, please note that network administrators may purposely block incoming PING connections due to security related issues.
3) The final piece of information is the DNS (or 'name') and/or the server IP address you are trying to contact on this hop. If you did not receive any responses from this server, you may receive an error message such as Request Timed Out or Destination Net Unreachable.
Important: Since our World of Warcraft servers are protected from unsolicited traffic and attacks, all the hops after you have reached our server may give you an error message such as 'Request Timed Out' or 'Destination Net Unreachable'. Our current server names begin with various mixes of numbers and letters, and end in the following addresses: Telia.net (example: prs-tc-ks51-geth0-1.telia.net) All error messages you may receive after contacting our server can be safely ignored for troubleshooting purposes, and they do NOT indicate a problem with your internet connection.
If you see any error messages or asterisks in your trace route for the hops before you reach our servers, you may need to contact your Internet Service Provider (ISP) and provide them your trace route information for further troubleshooting. Once the information has been submitted, it may take several days for the problem to be identified and resolved.
Remember that Blizzard Entertainment can only ask your ISP to fix an issue; the best results come when you contact your ISP directly.
How do I create a trace route to a World of Warcraft server?
Updated: 06-Jan-2012
Article ID: 496
Trollbane
Silvermoon
Draenor
Does that sound familiar to anyone?
I play on MAC OSX Lion 10.7.3.
Spinebreaker
Eonar
Eonar
Vek'nilash
Aerie Peak
Bloodfeather
over a maximum of 30 hops:
1 <1 ms 1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 12 ms 30 ms 18 ms 195.229.253.225
4 * * * Request timed out.
5 * * * Request timed out.
6 12 ms 12 ms 20 ms 194.170.0.238
7 17 ms 17 ms 23 ms nyc-emix-ca.at4101.emix.ae [195.229.0.249]
8 22 ms 23 ms 23 ms 195.229.3.197
9 144 ms 140 ms 141 ms dxb-emix-ra.so611.emix.ae [195.229.0.242]
10 226 ms 227 ms 225 ms ffm-b12-link.telia.net [213.248.78.89]
11 226 ms 227 ms 226 ms ffm-bb2-link.telia.net [213.155.135.12]
12 247 ms 244 ms 249 ms s-bb2-link.telia.net [213.155.133.117]
13 259 ms 255 ms 257 ms s-b3-link.telia.net [213.155.133.101]
14 265 ms 252 ms 252 ms s-hdn-i3-link.telia.net [80.91.249.69]
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 *
Alonsus
Runetotem
MI servirebbe una mano :((
Crushridge
Io ho craeto il tracert...e adesso con questi numeri chge ci faccio?
Altra domanda sul forum parlano di trace route e altro link per creare il pathping... credo che sia giusto fare il trace route...
Comunque a infostrada cosa gli dico???
Vi ringrazio già ora!
Hakkar
su un massimo di 30 punti di passaggio:
1 1 ms 98 ms 98 ms 192.168.1.1
2 36 ms * * 151.6.163.72
3 7 ms 8 ms 8 ms 151.6.185.98
4 26 ms 26 ms 25 ms 151.6.4.129
5 26 ms 27 ms 26 ms 212.245.229.50
6 45 ms 45 ms 45 ms if-2-0-1.core1.RCT-Rome.as6453.net [195.219.163.61]
7 50 ms 51 ms 50 ms if-7-0-1-0.tcore1.FR0-Frankfurt.as6453.net [195.219.50.117]
8 48 ms 49 ms 49 ms if-7-2.tcore1.FR0-Frankfurt.as6453.net [195.219.50.1]
9 45 ms 45 ms 45 ms 195.219.50.162
10 155 ms 57 ms 56 ms ffm-bb2-link.telia.net [213.155.133.146]
11 53 ms 53 ms 53 ms ffm-b10-link.telia.net [80.91.251.124]
12 * * * Richiesta scaduta.
13 * * * Richiesta scaduta.
14 * * * Richiesta scaduta.
15 * * * Richiesta scaduta.
16 *
Runetotem
Steamwheedle Cartel
Emeriss
Alonsus
Dragonblight