I don't believe this is a Livingston problem.
Although we (Bay Networks) do support MicroSoft's tracert, at least in the
testing that I've done in the field, if Microsoft would quit putting their
little touch on everything the supply we wouldn't be having this
discussion. Microsoft's tracert is not the same as the traceroute command
found on UNIX and most other IP stacks.
The blame should rest with Microsoft for not conforming to the industry,
but instead trying to force the industry to conform to it.
But that's just my two cents worth, and does not reflect the view or
opinions of my employer.
Charlie Clemmer
At 02:50 PM 5/20/97 -0400, Dolnik, Bryan wrote:
>It bugs me that I always see this answer from Livingston. Why do you
>suppose every other router in the world responds correctly. Are they ALL
>doing something wrong?
>
> ----
>From: MegaZone <megazone@livingston.com>
>To: portmaster-users@livingston.com
>Date: Tuesday, May 20, 1997 10:34 AM
>Subject: TRACERT problem - 1st hop times out (fwd)
>
>>Once upon a time Jim Boyce shaped the electrons to say...
>>>fine, and has for some time. However, there is one thing that bothers =
>>>me. Whenever I do a "tracert" (from Win95 OR WinNT) to any destination
>=
>>>outside of our LAN, the first hop always times out. When I take the =
>>
>>Yep. MS traceroute is different from everyone else, and we don't
>currently
>>respond to them. It will always timeout on all Livingston boxes.
>>
>>We just won't talk to MS traceroute at this time.
>>
>>-MZ
>>--
>>Livingston Enterprises - Chair, Department of Interstitial Affairs
>>Phone: 800-458-9966 510-737-2100 FAX: 510-737-2110 megazone@livingston.com
>
>>For support requests: support@livingston.com <http://www.livingston.com/>
>
>>Snail mail: 4464 Willow Road, Pleasanton, CA 94588
>>
>
>
>
>