Re: WINS via firewall
From: eng!neer (fdhgsl@sfg.com)Date: 05/10/02
- Next message: Greg Hennessy: "Re: nokia ip71 config - 2 ip addresses necessary?"
- Previous message: Reg Day: "Kerio - ICS & stealth?"
- In reply to: Bafi: "WINS via firewall"
- Next in thread: Berk S. Daemon: "Re: WINS via firewall"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "eng!neer" <fdhgsl@sfg.com> Date: Thu, 09 May 2002 22:23:17 GMT
I am not a Linux guru so I cannot assist directly however I have some info
related to WINS and browsing that you might like to know. First and
foremost, WINS uses directed traffic via UDP ports 137 and 138. WINS does
not use boroadcasts, Browsing does not necessarily use broadcasts either.
When browsing across routers ,because as you know routers by their
definition separate broadcast domains, there is more involved that straight
up 255.255.255.255 destination addresses to get the browse lists. In fact
WINS does not relate to browsing at all (in fact indirectly it does, and I
will get to that in a moment). When a machine comes online depending upon
how it is configured it try to participate in browse master election.
Accordin to a predetermined set of rules it will become the 'local segment
browse master' (terminology matters alot here) if it over-rules other
machines according to these rules. Once a machine is the 'local subnet
browse master' it will get browser announcements from other machine using
broadcasts and it will accumulate it's local subnet browse list. Now, here
is where WINS comes into play. When a 'local subnet browse master' has a
list for its local subnet it will use WINS to determine who the 'domain
master browser' is. In an NT domain this is the PDC always. There can be
only one 'domain master browser'. This master browser gets the lists from
all the 'subnet master browsers' and accumulates them into one 'master
browser list'. Then the 'domain master browser', again with directed
traffic' updates the 'subnet master browsers' lists with its complete list
that it has accumulated from the 'subnet master browsers' Now, for this to
work as planned, all the 'subnet master browsers' must know the address for
the 'domain master browser', which they can determine from WINS if they are
configured to do so. Likewise, the 'domain master browser' must also point
to the same WINS server (or a replication partner or the WINS server) for
its NETBios registration and lookups.
The idea is that client can in fact not even have a WINS server configured
in the settings, and still they can get a browse list. Because WINS (in
reguards to browsing anyway) is only needed for communication between the
domain and subnet browse masters.
Questions I have for you. Are you running domain or workgroup? Are their
domain controllers on each subnet? Not that there has one on each subnet
but domain controllers automatically take preference in browsing and in some
networks with all 9x or nt workstation there can be problems with browser
elections requiring registry changes to specify a browsemaster manually.
HTH
"Bafi" <lumesitsupport@lumes.lu.se> wrote in message
news:3CDAA7E3.32BEB@lumes.lu.se...
> How to allow broadcast messages generated by WINS clients to pass linux
> box. How to enable broadcast forwarding on Linux.
>
> Bafi
>
>
>
>
- Next message: Greg Hennessy: "Re: nokia ip71 config - 2 ip addresses necessary?"
- Previous message: Reg Day: "Kerio - ICS & stealth?"
- In reply to: Bafi: "WINS via firewall"
- Next in thread: Berk S. Daemon: "Re: WINS via firewall"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
