Here you go and I hope this helps.
First test results are,
C:\WINDOWS\Desktop>tracert 192.168.1.100
Tracing route to GLEN [192.168.1.100]
over a maximum of 30 hops:
1 <10 ms <10 ms 13 ms GLEN [192.168.1.100]
Trace complete.
Second test results,
Tracing route to
www.mediajukebox.com [198.73.82.148]
over a maximum of 30 hops:
1 69 ms 69 ms 68 ms HSE-Toronto-ppp315938.sympatico.ca [64.231.114.]
2 69 ms 82 ms 69 ms dis9-toronto12-Vlan100.in.bellnexxia.net [64.23.245.65]
3 69 ms 68 ms 83 ms core4-toronto12-Gigabite4-0.in.bellnexxia.net [06.108.107.221]
4 82 ms 82 ms 83 ms core1-chicago23-pos10-0.in.bellnexxia.net [206.08.103.134]
5 82 ms 83 ms 82 ms bx1-chicago23-pos10-0.in.bellnexxia.net [206.10.103.142]
6 82 ms 83 ms 82 ms s213773-1.uschcg1-bsn.savvis.net [216.89.108.57
7 96 ms 96 ms 96 ms 64.241.95.18
8 96 ms 96 ms 96 ms border-1-fa4-1-0.msp.origix.net [64.247.192.133
9 96 ms 110 ms 96 ms www.mediajukebox.net.jriver.com [198.73.82.148]
Trace complete.
And the third test resulted in,
C:\WINDOWS\Desktop>ping -l 1400 192.168.1.100
Pinging 192.168.1.100 with 1400 bytes of data:
Reply from 192.168.1.100: bytes=1400 time=13ms TTL=128
Reply from 192.168.1.100: bytes=1400 time=27ms TTL=128
Reply from 192.168.1.100: bytes=1400 time=14ms TTL=128
Reply from 192.168.1.100: bytes=1400 time=14ms TTL=128
Ping statistics for 192.168.1.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 13ms, Maximum = 27ms, Average = 17ms
Hope that this is what you were expecting, maybe?
Thanks, Glen