Ok. I think I understood something wrong. I thought the
logfile was from a member server, not from a BDC. If a BDC
creates its own name as a sambaDomain object in LDAP, then
there's a misconfiguration or a bug. A BDC does not have a
local SAM, only member servers do.
In my case you were
On Fri, Oct 05, 2007 at 02:11:23PM +0200, Christian Brandes wrote:
The samba domain should be mycompany as stated in workgroup and not
USER as stated in netbios name!
Works as designed. Every box has a SAM of its own.
Volker
pgpt4CM52sw11.pgp
Description: PGP signature
--
To unsubscribe
On 05/10/2007, Volker Lendecke [EMAIL PROTECTED] wrote:
On Fri, Oct 05, 2007 at 02:11:23PM +0200, Christian Brandes wrote:
The samba domain should be mycompany as stated in workgroup and not
USER as stated in netbios name!
Works as designed. Every box has a SAM of its own.
I experienced
On Fri, Oct 05, 2007 at 07:15:44PM +0200, Michal Dobroczynski wrote:
I experienced exactly the same behaviour. I expected my BDC stations
to reuse the 'workgroup' attribute, but the effect was exactly like
Christian wrote.
What do you mean by works as designed? Can we just use it that way,
On 05/10/2007, Volker Lendecke [EMAIL PROTECTED] wrote:
On Fri, Oct 05, 2007 at 07:15:44PM +0200, Michal Dobroczynski wrote:
I experienced exactly the same behaviour. I expected my BDC stations
to reuse the 'workgroup' attribute, but the effect was exactly like
Christian wrote.
What do
On Fri, Oct 05, 2007 at 10:15:02PM +0200, Michal Dobroczynski wrote:
Well - what I have discovered is that setting
domain logons = Yes
domain master = No
seems to solve the problem.
... because this *is* the only way to tell Samba to be a
BDC. This must be somewhere in the docs.
Volker
On 05/10/2007, Volker Lendecke [EMAIL PROTECTED] wrote:
On Fri, Oct 05, 2007 at 10:15:02PM +0200, Michal Dobroczynski wrote:
Well - what I have discovered is that setting
domain logons = Yes
domain master = No
seems to solve the problem.
... because this *is* the only way to tell
