My point in responding is that the blame shouldn't fall on Livingston for
not responding, but on Microsoft for providing poor utilities.
Does anyone know how Ascend, DEC, 3Com, etc react to this utility? I've
also seen certain firewall that don't respond either, although I don't work
with those products enough to say anything definitive.
Charlie Clemmer
Bay Networks
At 06:31 PM 5/20/97 -0400, Stephen Zedalis wrote:
>On Tue, 20 May 1997, Dolnik, Bryan wrote:
>
>>I understand that Microsoft deviated from the standard and this is not a
>>good thing, but my beef still remains that I can use 'tracert' effectively
>>on every other router on the Internet EXCEPT for Livingston's.
>
>This is not true, there are several routers out there besides
>Livingston that will generate "* * *" when queried with a MS TRACERT
>but work just fine with a UNIX traceroute. Livingston is just the most
>visible. Hey, whats your script for tracert to "every other router on
>the Internet"? I bet thats a collossal waste of bandwidth. :)
>
>>I get tired of trying to explain to customers that everyone else in the
>>world is wrong and we (Livingston router users) are right :(
>
>Not everyone else in the world, just everyone running MS products :)
>
>
>