[Samba] Re: WINS over subnets

[John H Terpstra]

On Sunday 01 October 2006 18:45, Hoggins! wrote:
> Edmundo Valle Neto a écrit :
> > Hoggins! escreveu:
> >
> > Yes, in that case it should maintain a more complete list. And yes you
> > just must have ONE WINS server.
> > I think you didnt got the point, domain master, local master, domain
> > controllers, wins server, etc are just roles of the same server,
> > enabling some options in smb.conf the same server can be all of them at
> > the same time.
> > BUT, other subnets need local master browsers too, they can be any
> > Windows workstation (normally you should not worry about that), this is
> > one of the reasons that all of them must use the same single WINS server
> > (I am not saying that yours are not), the LMB can be any available
> > workstation (the machines in the subnet should elect one automatically),
> > so any machine ending up beeing a LMB will use the  same WINS server to
> > find the DMB and sync. It works that way without you needing to care
> > about it.
> >
> >
> > Ok, if the wireless clients can see each others probably that segment
> > has an LMB with the browse list of that segment but just isnt passing it
> > to the samba server.
> > About the LMBs I just said that to make it clear, that the other
> > networks dont register themselves directly with samba to be included in
> > the browse.dat file, who does that is the LMB of that segment (as
> > explained before).
>
> Thanks, I understand better now how it works.
> So the LMB (any Win machine, elected) of the 192.168.3.0/24 segment must
> send its browse list to the server, right ? I must check this traffic
> with ethereal and/or with debug level 2. Sorry I didn't yet.

Not quite! 

The LMB does nothing to contact the DMB. The responsibility for browse list 
synchronization belongs to the DMB.

The DMB looks for the LMB registrations in the WINS (wins.dat) database. It 
then contacts each LMB to synchronise the browse list.

Ergo, if the WINS database does not contain all machines that are LMBs - 
browse list synchronization will not happen.

- John T.

>
> > Yes, it is possible and most of the times the recommended way.
> >
> >
> > Theres some tools and comands to see problems with name resolution on
> > the XP clients, like nbtstat or the netbios browsing console.
> >
> > Putting a log level of 2 in smb.conf, is there any interesting
> > information about elections in the nmbd log? Whould help if you include
> > your smb.conf here too.
>
> Yes, I put debug level to 2, and I saw that the server was always
> elected as the master. And also that the machines successfully
> registered to the server.
> My smb.conf (a bit modified since my first post, but the symptoms are
> the same though) :
>
> [global]
> 	display charset = ASCII
> 	workgroup = BOUFFARD
> 	netbios aliases = hgsserver
> 	server string = PARTAGES
> 	interfaces = eth0
> 	security = SHARE
> 	map to guest = Bad User
> 	root directory = /
> 	pam password change = Yes
> 	passwd program = /usr/bin/passwd %u
> 	passwd chat debug = Yes
> 	username map = /etc/samba/smbusers
> 	unix password sync = Yes
> #	log level = 2
> #	syslog = 3
> #	syslog only = Yes
> 	log file = /var/log/samba/%m.log
> 	max log size = 50
> 	debug timestamp = No
> 	time server = Yes
> 	server signing = auto
> 	socket options = TCP_NODELAY SO_SNDBUF=8192 SO_RCVBUF=8192
> 	printcap name = /etc/printcap
> 	os level = 32
> 	lm announce = Yes
> 	preferred master = Yes
> 	domain master = Yes
> 	local master = no
> 	dns proxy = No
> 	wins support = Yes
> 	ldap ssl = no
> 	remote announce = 192.168.3.255/BOUFFARD
> 	remote browse sync = 192.168.3.255 224.0.0.1
> 	usershare path =
> 	winbind enum users = Yes
> 	winbind enum groups = Yes
> 	winbind use default domain = Yes
> 	guest ok = Yes
> 	hosts allow = 192.168.2.0/24, 192.168.3.0/24
> 	cups options = raw
>
> [...] (some shares declarations)
>
> I'll come with more results on benchmarks ASAP. Thanks for your help and
> patience.
>
> Regards,
>
> 	Hoggins!