Hi,

When I Traceroute to one of our client's servers through traceroute
command in linux or windows I get following:

C:\Documents and Settings\Administrator>tracert xxx.xxx.xxx.xxx

Tracing route to xxx.xxx.xxx.xxx over a maximum of 30 hops

  1   <10 ms   <10 ms   <10 ms  10.0.9.99
  2   831 ms   981 ms   791 ms  xxy.xyz.yyy.zzz
  3  1021 ms   150 ms    50 ms  zxy.xzy.yyz.zxy
.............. lines removed
20   321 ms   370 ms   551 ms  zzz.zzz.zzz.zzz
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Then I ran Nessus on the client IP and got following in the report
(general/udp):

xxy.xyz.yyy.zzz
zxy.xzy.yyz.zxy
------- lines removed
zzz.zzz.zzz.zzz
yyy.yyy.yyy.yyy
?
xxx.xxx.xxx.xxx

As inidicated above in the Nessus result, there is one extra hop
traveresed (yyy.yyy.yyy.yyy) and it shows to reach xxx.xxx.xxx.xxx
after a question mark.

Can someone please tell what command Nessus uses for this? Meanwhile
I'll try HPING also.

Thanks.
_______________________________________________
Nessus mailing list
[email protected]
http://mail.nessus.org/mailman/listinfo/nessus

Reply via email to