thanx whylately for this vital information & knowledge....all of sudden it is working fine since last two days....but will keep the watch and note down the results when market watch goes freeze....
today morning :
C:\Documents and Settings\harsh>ping traderji.com
Pinging traderji.com [72.52.250.195] with 32 bytes of data:
Reply from 72.52.250.195: bytes=32 time=403ms TTL=53
Reply from 72.52.250.195: bytes=32 time=406ms TTL=53
Reply from 72.52.250.195: bytes=32 time=390ms TTL=53
Reply from 72.52.250.195: bytes=32 time=406ms TTL=53
Ping statistics for 72.52.250.195:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 390ms, Maximum = 406ms, Average = 401ms
C:\Documents and Settings\harsh>tracert traderji.com
Tracing route to traderji.com [72.52.250.195]
over a maximum of 30 hops:
1 87 ms 93 ms * 59.95.232.1
2 108 ms 109 ms 140 ms 218.248.255.18
3 108 ms 93 ms 109 ms 218.248.255.18
4 140 ms 140 ms 140 ms 203.101.65.233
5 140 ms 155 ms 155 ms 125.21.167.70
6 358 ms 374 ms 374 ms sl-gw39-nyc-0-0-1.sprintlink.net [144.228.178.16
5]
7 390 ms 390 ms 390 ms sl-crs2-nyc-0-5-0-0.sprintlink.net [144.232.13.6
3]
8 390 ms 390 ms 390 ms sl-crs1-chi-0-10-3-0.sprintlink.net [144.232.9.1
49]
9 390 ms 390 ms 390 ms sl-st20-chi-13-0-0.sprintlink.net [144.232.20.3]
10 406 ms 452 ms 406 ms 65.170.10.134
11 405 ms 405 ms 406 ms lw-core4-ge7.rtr.liquidweb.com [209.59.157.181]
12 406 ms 405 ms 405 ms lw-dc2-dist3-ge2.rtr.liquidweb.com [209.59.157.1
22]
13 405 ms 405 ms 405 ms traderji.com [72.52.250.195]
Trace complete.
ok....whylately....two question....
1) which is more better : is it the maximum round trip in milliseconds less or more ?
2) how to detect any flaw in hops ...as in above eg..is hops ok...
thank you