domain master browser

[John E Hein]

Simon Hyde wrote at 22:36 GMT on Nov 25:
 > Are all the PC's pointing to this server too?
 > This is always a good thing to setup

Thanks for the response, Simon...

Yes.  all the PCs point to the same NTAS WINS server that the samba server
 does.

 > You'll want to crank this up a bit, if you don't ever want another machine
 > to overrule yours as browser then set this to 255, somewhere around 70
 > should do, putting it well above the NT machine it's talking to (which is
 > somewhere in the 30's if I recall correctly)

According to the samba docs, no regular NT or win95 machine will
 beat anything with an os level of 2.  The only Windows app that would
 be higher would be the NTAS.
Nevertheless, if a Windows machine beat
 the samba server as Domain Master Browser, I wouldn't really care.  Cross-
 subnet browsing should still work since the Windows
 machine would then have the browse lists.

More info...
If I don't have a samba server it still doesn't work.
If I then start a samba server and crank the os level up to 33, it still
 doesn't work.

When I say "doesn't work", I mean I can't see machines in my workgroup
 that are on other subnets, nor can workgroup machines on THAT subnet see 
 workgroup machines on THIS subnet.  This is the crux of my problem, and
 I don't understand why it won't work.  Is the NTAS WINS server perhaps
 interfering?  And no, there is no NT domain named the same as the workgroup
 that my PCs and Samba server are in.

Is there a way to find out who is the Domain Master Browser and
 what it thinks the browse list is... and what Local Master Browsers
 (aka Segment Master Browsers) are out there?

------- start of included message for reference -------
From: shyde at poboxes.com (Simon Hyde)
To: samba at samba.anu.edu.au
Cc: jhein at fallschurch.esys.com
Subject: Re: domain master browser
Date: Tue, 25 Nov 1997 22:36:52 GMT

On Tue, 25 Nov 1997 10:40:01 +1100, you wrote:

>I'd like my Samba server 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).
>
>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.
>
>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').

Are all the PC's pointing to this server too?
This is always a good thing to setup

>
>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).
>
>% nmblookup -d 5 -B lorax __SAMBA__
>Initialising global parameters
>Processing configuration file "/usr/local/samba/lib/smb.conf"
>Processing section "[global]"
>doing parameter browseable = yes
>doing parameter domain logons = yes
>doing parameter guest account = nobody
>doing parameter load printers = yes
>doing parameter logon script = hi.bat "S: %S" "P: %P" "u: %u" "g: %g" "U: %U" "G: %G" "H: %H" "v: %v" "h: %h" "m: %m" "L: %L" "M: %M" "d: %d" "a: %a" "I: %I" "T: %T"
>doing parameter lpq command = /usr/ucb/lpq -P%p
>doing parameter print command = /usr/ucb/lpr -P%p %s;/bin/rm -f %s
>doing parameter printcap name = /usr/local/smb/printcap
>doing parameter printing = sysv
>doing parameter security = user
>doing parameter smbrun = /usr/local/samba/bin/smbrun
>doing parameter username map = /usr/local/smb/user.map
>doing parameter workgroup = ENGINEER
>doing parameter wins support = no
>doing parameter wins server = 199.170.224.6
>doing parameter domain master = yes
>doing parameter local master = yes
>doing parameter preferred master = yes
>doing parameter os level = 2

You'll want to crank this up a bit, if you don't ever want another machine
to overrule yours as browser then set this to 255, somewhere around 70
should do, putting it well above the NT machine it's talking to (which is
somewhere in the 30's if I recall correctly)

>doing parameter log file = /var/adm/log/log.mMuUhLv.%m,%M,%u,%U,%h,%L,%v,
>doing parameter lock directory = /var/spool/samba/locks
>doing parameter share modes = yes
>pm_process() returned Yes
>adding IPC service
>Warning: inconsistant interface 192.207.166.161
>Added interface ip=192.207.166.161 bcast=192.207.166.161 nmask=0.0.0.0
>bind succeeded on port 0
>Socket opened.
>Sending queries to 192.207.166.161
>11/24/97 18:30:01 sending a packet of len 50 to (192.207.166.161) on port 137
>11/24/97 18:30:01 received a packet of len 62 from (192.207.166.161) port 137
>nmb packet from 192.207.166.161(137) header: id=30452 opcode=Query(0) response=Yes
>    header: flags: bcast=No rec_avail=No rec_des=Yes trunc=No auth=Yes
>    header: rcode=0 qdcount=0 ancount=1 nscount=0 arcount=0
>    answers: nmb_name=__SAMBA__(0) rr_type=32 rr_class=1 ttl=14400
>    answers   0 char D.....   hex 4400C0CFA6A1
>Got a positive name query response from 192.207.166.161 (192.207.166.161)
>192.207.166.161 __SAMBA__

------- end -------