domain master browser

[Simon Hyde]

On Thu, 18 Dec 1997 03:14:19 +1100, you wrote:

>Thanks for using NetForward!
>http://www.netforward.com
>v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v
>
>If my samba server is NOT the domain or local master browser even though
> I am trying to set it up that way, then which machine on the net is?
> How do I find out?
>
>I'd like my Samba server (currently running 1.9.17p4) to be a Domain
> Master Browser for a workgroup (let's call it 'ENGINEER').
>
>I set it up according to BROWSING.txt, but yet Windows NT/95 PCs on other
> subnets are unable to browse and see computers on this subnet
> (even if those PCs are also in the same workgroup).
> Hmmm... why not?  What could cause this?
>
>It appears that the Samba is not acting as the Domain Master Browser
> ... at least as far as I can tell... and this is where I need
> help in verification of my setup.  Maybe it's just that there
> is already a domain or local master browser selected when
> I start Samba.  If I give Samba a high 'os level', should it
> immediately take over as a master browser or does it wait
> until a current master browser gives that up?
>
>192.207.166.161 (aka lorax) is the IP address of my samba server.
>
>Below is the output of nmblookup with debug level of 5.
>Notice the [slightly misspelled] warning:
>Warning: inconsistant interface 192.207.166.161
>After looking at this code in nmblookup.c/interface.c, I am convinced this
> is because of a minor bug in the code where the network mask is passed
> in as 0.0.0.0
>So, I don't think that has anything to do with my problem...
> which again is that PCs in the same workgroup on other subnets
> don't see PCs on this subnet.
>There is no NT domain named the same as the workgroup.  There is an
> NT server acting as a WINS server (199.170.224.6 as specified
> as the 'wins server').
>
>I've tried raising the os level to 33 also... that did not give different
> results.
>
>Anyone have any ideas?  Do I need to have the WINS server be the
> domain master browser instead of Samba (BROWSING.txt seems to
> clearly indicate that Samba can be the Domain Master Browser).
>
>notice that nbtstat on a Win NT machine does not mention my samba machine as
> a master browser...
>
That's because it has an os level lower than that of the NTAS machine and
therefore cannot become local master browser or domain master browser (the
first being required before the second can be done)