Received: from relay4.UU.NET by spaatz.nhq.cap.gov
(PostalUnion/SMTP(tm) v2.1.7 for Windows NT(tm))
id AA-1995Sep26.181909.0.4884; Tue, 26 Sep 1995 18:19:09 -0500
Received: from miles.greatcircle.com by relay4.UU.NET with ESMTP
id QQzixp19023; Tue, 26 Sep 1995 19:19:53 -0400
Received: (majordom @
localhost) by miles.greatcircle.com (8.6.9/Miles-950430-1)
id OAA16069 for firewalls-outgoing; Tue, 26 Sep 1995 14:07:43 -0700
Received: from ncelec.com ([18.104.22.168]) by miles.greatcircle.com
(8.6.9/Miles-950430-1) with SMTP id OAA16053 for <firewalls @
Tue, 26 Sep 1995 14:07:38 -0700
Received: from mike_pc by ncelec.com (5.4R3.10/22.214.171.124)
id AA09918; Tue, 26 Sep 1995 14:03:16 -0700
Date: Tue, 26 Sep 1995 14:03:16 -0700
Message-Id: <9509262103 .
X-Sender: mculver @
X-Mailer: Windows Eudora Pro Version 2.1.2
Content-Type: text/plain; charset="us-ascii"
To: firewalls @
From: Mike Culver <mculver @
Subject: Re: Why is Windows NT sending this packet ? (fwd)
Sender: firewalls-owner @
Maybe this is how NT handles browsing in absence of NetBeui?
>>On Sep 26, 2:45pm, Torsten Sturm (CIP 89) wrote:
>>> Subject: Why is Windows NT sending this packet ? (fwd)
>>> Does anyone know why my Windows NT Server v3.5 would be sending packets
>>> Name: MICROSOFT.MCAST.NET
>>> Address: 126.96.36.199
>IP address in the range of 188.8.131.52-184.108.40.206 are multicast address
>with a special attribute. Instead of the destination being a single machine
>it is a group of machines that have made a request to their NIC to receive
>any packets to this address. The most common place you will see this is with
>routers to send updates. Multicasting works the same as broadcasting except
>only the hosts that want to recieve the packets will see them.
>This does not explain why NT is sending request on this address. The only
>thing I can think of would be it is how it handles the concepts of "groups"
>for NetBIOS over TCP/IP.