Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: (ASCEND) Ascend Pipeline 50 Q.
Actually, it still can be a MS problem. I searched the archives of
another list where this has been discussed. MS didn't write their
versio of tracert to standards. I have personally seen it on machines
here in the office. The questions to ask are what version win95 are you
both running OSR1 or OSR2? Have you installed the various patches?
What version OS are you running on the Pipeline 50?
I think that OSR2 may not do this, as I have one machine on OSR1 that
does this, and my workstation (Running OSR2) does not. Here's a quoted
post from the portmaster-users list about this:
> From: "John G. Thompson" <jgt10@livingston.com>
> Message-ID: <3.0.32.19970605152422.006dcd0c@server.livingston.com>
> Reply-To: "John G. Thompson" <jgt10@livingston.com>
> Date: Thu, 05 Jun 1997 15:24:23 -0700
> What 95 and NT do that is non-standard is the following...
> If Windowz determines that the IP address to be ping'd is on the local
> network, as defined by address and netmask, the Windowz OS proceeds to > send
> UDP packets on ports 137, 138 or 139. If there isn't a response to > the UDP
> packet the Windowz ping process IMMEDIATELY reports the address as not > there.
> Please note that the above process does not:
> - wait the default 5 seconds to timeout the request and
> - never sends and icmp packet.
This discussion continued through several posts and I'm not going to
spam the list with them, if you wish to read the rest of it, you can go
to:
http://www.netimages.com/ni-cgi-bin/fetch?newsgroup=portmaster-users&search=form
and search the year 1997 for the subject of traceroute.
Hope this sheds some more light on things.
Kevin
++ Ascend Users Mailing List ++
To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd: <http://www.nealis.net/ascend/faq>
References: