nixCraft

In One on of the embedded network device support
the CLI command <tracerote IP address> like tracert on windows CLI

why traceroute 8.6.19.68 not completed the trace in 20 hops <max limit of device> it was showng only the gateway and remaining all *
What could b the reason, speed was 100Mbs of the device
If we compare with the windows is the following output

C:\Documents and Settings\Administrator>tracert 8.6.19.68
Tracing route to 8.6.19.68 over a maximum of 30 hops
1 1 ms <1 ms <1 ms 192.168.1.1
2 39 ms 30 ms 33 ms 121.246.32.1.dynamic-pune.vsnl.n
2.1]
3 29 ms 30 ms 34 ms 172.31.70.21
4 30 ms 28 ms 30 ms 172.31.8.193
5 29 ms 30 ms 40 ms 172.31.3.13
6 30 ms 30 ms 34 ms 172.31.12.249
7 * * * Request timed out.
8 33 ms 34 ms 34 ms 59.163.59.37.static.vsnl.net.in
9 293 ms 287 ms 277 ms 59.163.55.202.static.vsnl.net.in
10 323 ms 324 ms 325 ms if-2-11.mse1.NW8-NewYork.as6453.
7]
11 329 ms 324 ms 325 ms if-7-0.core1.NTO-NewYork.as6453.
]
12 325 ms 324 ms 325 ms if-14-0-0.core2.NTO-NewYork.as64
.13]
13 347 ms * 344 ms cr2-pos-0-8-0-3.nyr.savvis.net [
14 338 ms 334 ms 348 ms cr2-bundle-pos-1.sanfrancisco.sa
.197.33]
15 343 ms 340 ms 340 ms er1-te-2-0-1.SanJose3Equinix.sav
200.234]
16 336 ms 335 ms 342 ms hr1-te-2-0-0.santaclarasc5.savvi
0.206]
17 335 ms 334 ms 336 ms hr1-te-2-0-0.santaclarasc8.savvi
0.226]
18 353 ms 336 ms 337 ms 204.70.203.142
19 338 ms 339 ms 334 ms csr2-ve243.santaclarasc8.savvis.
1]
20 336 ms 339 ms 334 ms csr1-ve241.santaclarasc8.savvis.
2]
21 339 ms 339 ms 340 ms 66.35.203.158
22 345 ms 352 ms 336 ms 208.82.16.230
23 358 ms 338 ms 334 ms 8.6.19.68
Trace complete.

You better contact their networking department usually problem exists between your ISP or their network. Email them your output. Sometime a firewall is configured to block ping and trace router paths.

__________________
Rocky Jr.
You may have my body & soul, but you will never touch my pride!

If you have knowledge, let others light their candles at it.

Certified to work on HP-UX / Sun Solaris / RedHat