Yeah there's still a few dinosaurs roaming the earth who can't figure out
how to configure their network so that ping can't be used as a denial of
service attack. Or they remember something from years ago that it could
be an issue (sort of like those who don't put keys on a PF table because
they heard it was an issue on some early release of S/38).
But some "spreaders" like IBM's Edge server where you goto x.x.x.x and it
may route you to y.y.y.y or z.z.z.z also block pings. (We use Edge).
It is something to consider though.
another command to try from DOS is tracert
Tracing route to sametime.corp.dekko.com [10.17.6.161]
over a maximum of 30 hops:
1 3 ms 19 ms 21 ms gdslan-v8.corp.dekko.com [10.10.8.1]
2 <1 ms <1 ms <1 ms albt-g0-0-903.corp.dekko.com [10.7.0.233]
3 <1 ms <1 ms <1 ms avcm-t307.corp.dekko.com [10.20.0.241]
4 1 ms 1 ms 1 ms grrtwan01-t320.corp.dekko.com
5 7 ms 1 ms 1 ms grrtlan-v9.corp.dekko.com [10.17.0.9]
6 * * * Request timed out.
7 * *
I can see that it hit a router here in Kendallville,
bounced off of our tower in Albion IN,
went through some equipment we have in Avilla,
made it to our Garrett wide area network,
made it to some local equipment in Garrett
and then nothing.
"sametime" routes through our edge server (which is not listed above) so I
suspect if something blocks ping it's going to block tracert also.
This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact