[Samba] (no subject)

[Douglas VanLeuven]

Dale Schroeder wrote:
> I have systems using security = ADS and security = domain where
> "password server =" works quite well.  There's something else going on.
> 
> Dale
> 
> Adam Williams wrote:
>> password server = only works when samba is in security = server mode.
>>
>> security = domain is used when the server is a member server of an NT4
>> style domain (meaning, its not a PDC or a BDC, but another server with
>> some file shares on it and it authenticates to the PDC using LDAP).
>>
>> when you have a bunch of samba servers like you sound like you do, you
>> should be using an LDAP backend.
>>
>> Carter, David SIS SB56 ITMOXF POWERGEN wrote:
>>> Installed Samba 3.0.10 via 'pkgadd' on Solaris 2.6 workstation s080
>>> (137.223.31.80) - previously running Samba 2.2.8 which has worked for a
>>> long time.
>>> Samba 3.0.10 smb.conf file - changed to security =DOMAIN  from SERVER at
>>> 2.2.8 version
>>> password server = 137.223.33.45, 137.223.33.72  - these are DCs
>>>  
>>>
>>> # Samba config file created using SWAT
>>> # from 127.0.0.1 (127.0.0.1)
>>> # Date: 2008/02/07 16:05:52
>>>
>>> # Global parameters
>>> [global]
>>>     workgroup = WW007
>>>     server string = Samba Server ww007
>>>     interfaces = 137.223.31.80/255.255.255.0
>>>     bind interfaces only = Yes

You might try adding 127.0.0.1
  interfaces = 137.223.31.80/255.255.255.0, 127.0.0.1/24

There are some issues documented in the manual and it seems to help with
any broadcast related issues.

I've started masking to 24 bits because I've had some servers come up
with 127.0.0.2 on occasion.  Might be dual processors, but I've not
pursued it further.

Regards, Doug