Quote:
Originally Posted by
Tusembobel
This Raist guy posts are found everywhere on forums, and all of them are like - do not ask SE to do anything, there's nothing to do with SE, all of your ISP are shits..etc.. We are trying to tell each other our problems, not to hear your lections Mr. Raist. I want to play the game I pay for, not to battle through lags.. Guess who must provide me with such opportunity? I mean they do not even answer my tickets, do not try to find out the reason..
Would you not agree that it benefits the community more when we work towards actual solutions instead of sitting around whining about things and slinging mud at people? Do you actually want someone to provide answers, or are you just coming here to vent frustrations? I hope it is the former and not the latter. The purpose of this forum is for users to assist users in finding solutions. Read the sticky welcoming you to this forum for clarification if you don't understand.
Quote:
Running a Trace Route
Trace routes can help identify where connection problems occur by testing the connection from your computer to a specified target location. A trace route report shows the step-by-step path that a packet of test data takes to reach its destination.
With the information from a trace route, you can work with your Internet Service Provider (ISP) to solve Internet connection issues. Follow the instructions below for your operating system.
Running a Trace Route
Windows
Click Start and type CMD in the search field.
Right-click on CMD.exe and select Run as Administrator.
Type tracert xxx.xxx.xxx.xxx > c:\tracert.txt and press Enter. Replace the x's with the appropriate server address.
Allow several minutes for the trace route to complete.
A file will be created inside your C: drive called tracert.txt that contains your trace route information.
Type exit and press Enter to close the command window.
Mac OS X
Go to the /Applications/Utilities folder and start the Terminal application.
Type traceroute xxx.xxx.xxx.xxx > ~/Desktop/tracert.txt and press Return. Replace the x's with the appropriate server address.
Allow several minutes for the trace route to complete.
A file will be created on your desktop called tracert.txt that contains your trace route information.
Type exit and press Return to close the terminal.
<<<Edited out the IP address lists, because it gets all out of whack when quoting, follow the URL if you want them--they list them for multiple games>>>>
Analyzing a Trace Route
If you notice any of the following problems in your trace route report, it may indicate an issue with your connection:
Time outs
* symbols
If the number value before the ms jumps from a low number to high number
If the numbers stay at high values.
Because of the safeguards that protect our Battle.net servers, you may notice later hops in your trace route failing with an error message such as 'Request Timed Out' or 'Destination Net Unreachable'. You may also see inflated latency numbers. You can ignore any error messages you receive after contacting our servers as they do not indicate a problem with your internet connection. To identify our servers, look for the following suffixes: attens.net, att.net, alter.net, telia.net.
Sometimes we may need additional information diagnose problems. If requested, obtain specific system files or run a pathping on your connection.
Updated: Dec 10, 2014