Re: Why is there a broadcst on Port 137 and 138 on my network??
From: nntp (nntp@somewhere.com)
Date: 11/21/02
- Next message: David: "Re: How safe Am I? tpf,hardware fw,socks,etc"
- Previous message: Jem Berkes: "Re: Web sites for checking ports"
- In reply to: Lars M. Hansen: "Re: Why is there a broadcst on Port 137 and 138 on my network??"
- Next in thread: NeoSadist: "Re: Why is there a broadcst on Port 137 and 138 on my network??"
- Reply: NeoSadist: "Re: Why is there a broadcst on Port 137 and 138 on my network??"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "nntp" <nntp@somewhere.com> Date: Thu, 21 Nov 2002 05:24:20 GMT
Downloaded a sniffer and found that the traffic is indeed Browser
announcements.
BROWSER Host Announcement, Workstation, Server, Domain Controller, Print
Queue Server, NT Workstation, Master Browser MYSERVER'SNAME
BROWSER Domain/Workgroup Announcement MYDOMAINNAME, Domain Controller, NT
Workstation, Domain Enum
Changing node type to 0x2 has no affect, however, on browser announcements.
"Lars M. Hansen" <badnews@hansenonline.net> wrote in message
news:c5ajtuocq63vfqbek3u3j5q226m9dsuhbn@4ax.com...
> On 18 Nov 2002 14:03:36 -0800, J H spoketh
>
> >Cool. thanks for the numerous and informative artciles.
> >
>
> NetBios uses 4 different node types on a network. These are
> point-to-point, broadcast, hybrid and mixed node.
>
> By default, Windows computers are set up with an H-Node (hybrid), which
> means the computer will attempt to locate other computers on a LAN a
> lookup first, then if that fails, it'll do a broadcast. If there is no
> wins server to ask for name lookups (don't confuse with DNS), it'll
> resort to broadcast traffic, which is what you're seeing.
>
> An M-Node is pretty much the same as a H-Node, only the events are
> reversed. First, it'll do a broadcast to find the names, then it'll
> query the wins database.
>
> B-Nodes (broadcasts) ignores wins altogether, and relies solely on
> broadcasts.
>
> P-Nodes relies on WINS for all name resolution. A P-node will never
> resort to broadcasts if it cannot resolve the name via wins. If the wins
> query doesn't return an answer, it assumes the named resource doesn't
> exist. If you have a large LAN, P-nodes are the way to go. You can set
> this up on the DHCP server...
>
> See here for more:
> http://www.windowsitlibrary.com/Content/386/10/5.html
>
>
> Lars M. Hansen
> http://www.hansenonline.net
> (replace 'badnews' with 'lars' in e-mail address)
- Next message: David: "Re: How safe Am I? tpf,hardware fw,socks,etc"
- Previous message: Jem Berkes: "Re: Web sites for checking ports"
- In reply to: Lars M. Hansen: "Re: Why is there a broadcst on Port 137 and 138 on my network??"
- Next in thread: NeoSadist: "Re: Why is there a broadcst on Port 137 and 138 on my network??"
- Reply: NeoSadist: "Re: Why is there a broadcst on Port 137 and 138 on my network??"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|