Sniper's Paradise!
Advanced Server TNT
(Testing and Tweaking)
Testing Your ISP:
Pings Good, Performance Sucks!
Typical complaint, sometimes your issue, sometimes your ISP. First, your provider. You're going to have to see, based on your own experiences online, if your provider is responsible for packet loss, multiple retries for packets, etc. There's just no subtitute for a good provider. In a DOS window, do a tracert xxx.xxx.xxx.xxx (use known IP or internet addresses) to see the routes your provider has to different geographical areas of the country - see how many timeouts you get (some of these will be normal, as many routers do not respond to this command, unfortunately). Be aware of actual computers on the internet in your tracert and any problems with times to respond.
Running a Trace Route
First pick a Unreal Server with only one player in it and got it's IP address.
Now go to Start | Programs | MS-Dos Prompt | to bring up the dos prompt. Type in tracert 222.111.333.444 (of course use the server's IP address you want to test).
It should come up looking like this:
C:\WINDOWS>tracert 222.111.333.444
Tracing route to cm-222-111-333-444.theirprovider.com [222.111.333.444]
over a maximum of 30 hops:
...1..... 17ms ...20ms... 17ms......444.333.222.555
...2 ...186ms....17ms....18ms.......router-21.myprovider.com [222.111.333.21]
...3 ...232ms ...20ms ...18ms ......router-1.myprovider.com [222.111.333.1]
...4 ...122ms ...18ms ...18ms ......router-129.myprovider.com [222.111.333.129]
...5 ....60ms ....18ms ...16ms ......router-109.myprovider.com [222.111.333.109]
...6 ....41ms ....15ms ...20ms ......router-98.myprovider.com [222.111.333.98]
{etc..etc..continuing on to the server's IP address which happened to be in Canada, went thru 15 steps to get there.}
Trace complete.
C:\windows>
Note:
You might want to try tracert with a few options to reduce the time it takes to get the data and the amount of traffic you add to the network. For example, without the -d option, tracert tries to resolve all addresses into hostnames, which causes added network overhead and adds time to the total job at hand. To see other options for tracert, just type "tracert" by itself at a DOS prompt (you can do the same for ping as well).
Even though these tools are helpful in gathering information, you don't want to use them too often especially when you have
bandwidth sensitive things occurring. Both tracert and ping can cause havoc with game servers located on the same network. To see
what I'm talking about, the next time you're at a Lan game with a few people, keep opening up new dos prompts and
typing "ping -t someIPaddressOnYourLan" and see how long it takes for the players to notice a degradation in play,
and how long it takes before they start loosing their connections. They should notice the game play whither rather quickly, and can often be disconnected before they know what's going on.
There are a few options you can add to tracert:
-d...............................do not resolves addresses to hostnames
-j host-list..................loose source route along host-list
-h maximum hops.....maximum number of hops to search for target
-w timeout wait........timeout milliseconds for each replay
All logos and trademarks are properties of their respective owners.
Unreal™ is a registered trademark of Epic Games Inc.
Privacy Policy
Website by
Powered by RUSH