>In regards to the problem you were having with tracerouting through a
>PortMaster. We've been able to pinpoint the problem in the code that causes
>this to happen. Its a very easy bug to fix and will be fixed in the next
>release.
>-----Original Message-----
>From: Ryan Mooney [SMTP:ryan@pcslink.com]
>Sent: Thursday, November 07, 1996 4:07 PM
>To: slagos@net1plus.com
>Cc: portmaster-users@livingston.com
>Subject: Re: Traceroute Command Line Options
>
>
>Like my last message said, it has NOTHING to do with time outs, or
>no reverse, or anything like that! Its a M$ versus Livingston issue.
>
>Try it sometime...
>
>>
>> Here is the usage for the command line Tracert utility that comes with
>> Windows 95. Hopefully this will help those that were concerned about there
>> routers timing out.
>>
>>
>> Usage: tracert [-d] [-h maximum_hops] [-j host-list] [-w timeout]
>>target_name
>>
>> Options:
>> -d Do not resolve addresses to hostnames.
>> -h maximum_hops Maximum number of hops to search for target.
>> -j host-list Loose source route along host-list.
>> -w timeout Wait timeout milliseconds for each reply.
>>
>>
>>
>
>----------------------------------------------------------------------------
>Ryan Mooney Phone (602)265-9188 PCSLink
>ryan@pcslink.com Fax (602)265-9357 Internet Services
>
>The world needs more bitter, twisted souls. It would be a much better place.
>-----------------------------------------------------------------------------