Thread: Tracert

Someone recently suggested to use a tracert, but I have no idea what I'm doing when I get to the website. Anyone wanna offer some guidance?

Some ping tests and a tracert will help determine if any of your latency issues are due to the connection and may help determine where the source of the increased delay is at. (may however reveal hopelessness)

Here's the steps.

Opening the command prompt: Start -> Programs -> Accessories -> Command prompt.

Run a 500 count ping test
1) Open the command prompt
2) type ping 173.234.33.162 -l 512 -n 500, and press enter
3) wait for test to complete may take a few minutes
4) Right click the black window and choose Mark.
5) Highlight the statistics only, by click dragging, should make it white. once highlighted press enter (this places it on your clipboard)
6) paste it here.

Should look something like
Ping statistics for 173.234.33.162:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 40ms, Maximum = 49ms, Average = 43ms


Run a tracert
1) Reopen the command prompt
2) type tracert 173.234.33.162
3) wait for test to complete
4) Right click and choose Select all, should make it all white. Once highlighted press enter (this places it on your clipboard)
5) Paste it here. Also paste it to a new post here.

Originally Posted by Savage'

Maybe try a ping test at pingtest.net

This tells you little. You can ping test just about anywhere. You can speed test most anywhere. He is concerned about his gaming. To TPG. This is what matters. If you want to give a general testing result amongst many locations -- this only tells you one of two things. Is my local connection good? And is my ISP good. Both can be achieved with the tests above. I wait for your response dB

Ping statistics for 173.234.33.162:
Packets: Sent = 500, Received = 494, Lost = 6 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 30ms, Maximum = 3503ms, Average = 71ms

I really need a wired connection...

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Daniel>tracert 173.234.33.162

Tracing route to 173.234.33.162.WAYWIRE.NET [173.234.33.162]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 22 ms 11 ms 21 ms 10.86.128.1
3 14 ms * 27 ms dstswr1-vlan4.rh.brfdnj.cv.net [67.83.242.193]
4 * * * Request timed out.
5 19 ms 24 ms 31 ms 64.15.2.117
6 * * * Request timed out.
7 * * * Request timed out.
8 85 ms 86 ms 110 ms ae3-70g.cr1.ewr1.us.nlayer.net [69.31.94.117]
9 148 ms 162 ms 182 ms xe-3-0-0.cr1.ord1.us.nlayer.net [69.22.142.74]
10 162 ms 117 ms 125 ms ae1-30g.ar1.ord1.us.nlayer.net [69.31.111.134]
11 180 ms 184 ms 219 ms er01.chi01.ubiquityservers.com [69.31.111.66]
12 153 ms 165 ms 162 ms 173.234.33.162.WAYWIRE.NET [173.234.33.162]

Trace complete.

C:\Documents and Settings\Daniel>


LMFAO

Originally Posted by SiDRoC

Mind if I hop in here?

Nope. Well traceroute looks pretty normal. Have to say though this is the reason I find them as a limited diagnostic tool unless your problem is consistent on every ICMP test.

Some would think a problem exists here but doesn't: 5 219 ms 203 ms 199 ms s208-180-36-173.snjs.ca.sta.suddenlink.net [208.180.36.173]
Apparent traffic deprioritization, means nothing since packets go through fine to the next hop.
60-80ms seems pretty normal considering your distance from the server. Jitter looks minimal. Are you experiencing latency issues?