<PREFACE> By the bugs I found in Samba3 I really wonder if anybody is using Samba3 on Production Servers, otherwise I could not imagine why this bug slipped thru until now (3.0.1). </PREFACE> OK, the Documentation states that the Parameter "domain logons = yes" is **only** needed when you want to support Win 9x style logins. However this is not true, without this Paramter Samba does not act as PDC at all. This is shown by testparm as well as when testing things out from WindowsXP/2000 clients. Without the parameter "domain logons = yes" testparm reports ROLE_STANDALONE. Beside of that I'm unable to locate and join the Domain with WindowsXP/2000 clients, when this parameter is not set. So I would suggest: 1. Either change the Documentation to reflect this 2. or program the behavior of the parameter according to the Documentation. For option 1. I volunteer to update the Documentation for that. For option 2. Sorry only programming in Perl, so I'm not able to fix that. #### Config ##### [global] display charset = UTF-8 workgroup = TEST.INT netbios name = Server smb passwd file = /etc/samba/private/passdb.tdb passdb backend = tdbsam min protocol = NT1 time server = Yes os level = 64 preferred master = Yes domain master = Yes wins support = Yes ldap ssl = no [ALL] path = /Daten read only = No guest ok = Yes
What documentation are you referring to ? the smb.conf(5) man page? I've just updated that 'domain logons = yes" entry in CVS.
exactly, in more detail the smb.conf(5) which is shipped with samba 3.0.1 and you see when invoking from swat for example. Also I wondered because there is still Samba 2.2 referenced.
the man page has been updated.
sorry for the same, cleaning up the database to prevent unecessary reopens of bugs.
database cleanup