porting samba to new platform questions.

[David Collier-Brown]

Ron Alexander wrote:
> My dev/test environment consists of 1 NT4 workstation connected to the @home
> network using a security pkg (like VPN) to a Stratus box.

	Cool! A VOS port!

> The Stratus box has several ethernet cards.
> 
> I have limited samba to just the one interface via smb.conf variables
> interfaces, bind interfaces only, and hosts allow.
> 
> What I do NOT know, is what to set up for things like local/master domain
> master etc. Given my dev/test setup, what is the correct combination of
> variables to make things like name resolution and network neighborhood work?

	Ok, for browse mastering I use
		security = user
		domain master = yes
		preferred master = yes
		os level = 34
	This makes the samba server try to be
	the topmost browse master, cause an
	election if not, and win elections handily.

	For wins, I just use
		wins server = yes

	You might also turn on dns proxy, so that
	samba will look in dns if WINS is missing
	the name.  

	

> The symptom is that nmbd is in a loop putting out a continuous stream of log
> msgs that repeat as follows.
> 
> [2000/05/01 19:46:15, 10] nmbd_sendannounce.c:(404)
>   announce_myself_to_domain_master_browser: t (957224775) - last(957224760)
> < 900
> [2000/05/01 19:46:15, 4] nmbd_workgroupdb.c:(163)
>   find_workgroup_on_subnet: workgroup search for VOSAMBA2 on subnet
> UNICAST_SUBNET: found.
> [2000/05/01 19:46:15, 4] nmbd_workgroupdb.c:(163)
>   find_workgroup_on_subnet: workgroup search for VOSAMBA2 on subnet
> UNICAST_SUBNET: found.
> [2000/05/01 19:46:15, 4] nmbd_workgroupdb.c:(163)
>   find_workgroup_on_subnet: workgroup search for VOSAMBA2 on subnet
> 134.111.220.160: found.
> [2000/05/01 19:46:15, 10] nmbd_sendannounce.c:(404)
>   announce_myself_to_domain_master_browser: t (957224775) - last(957224760)

	Ok experts, does this look to you like samba is trying
	to communicate (via udp) and not getting any responses?

	An associated symptom is that nmblookup run from the
	server doesn't find anything. [from an off-line discussion]

	Once nmblookup and smbclient -L localhost
	work, the next likely issue is going to be:

>     interfaces = 111.222.333.444/255.255.255.0
>     bind interfaces only = Yes
>     hosts allow = 111.222.333. 127. 24.88.99.

	If the client is on net 24.88.99, then
	we're going to have browsing problems, as
	the initial steps are all non-routable broadcasts.

	If the client is NT, it can be the local browse
	master, and  we can probably arrange
	for them to talk, either with local browse sync (?)
	or by the local master looking in WINS for the
	domain browse master. 


> [tmp]
>      path = /system/samba/tmp
>      public = yes

	PS: this will be read-only unless you say
	writeable = yes

--dave
-- 
David Collier-Brown,  | Always do right. This will gratify some people
185 Ellerslie Ave.,   | and astonish the rest.        -- Mark Twain
Willowdale, Ontario   | //www.oreilly.com/catalog/samba/author.html
Work: (905) 415-2849 Home: (416) 223-8968 Email: davecb at canada.sun.com