samba - May 2007 - sambaDomainName=HOST i.s.o. ...=DOMAIN

Hello,

I'm trying to setup a standalone samba server named "alta" in a 
workgroup named "TDOM". So I put

   workgroup = TDOM

in the 'smb.conf' file. The netbios name of the machine defaults to 
'ALTA' so no netbios name paramater is needed (I assume).

I've put the user and group accounts in an ldapsam backend and I also 
created a sambaDomainName=TDOM,... . The user and groups have sid's in 
that domain (sid = <TDOM-sid>-rid).

Now when I start the samba server it creates an extra entry 
sambaDomainName=ALTA in de ldapsam backend, and no user can login 
because the domain doesn't match. I suspect some idmap parameters could 
be used to allow users to login, but the main problem is:

1. Why is a sambaDomainName=ALTA entry created while I specified a 
workgroup of TDOM?
2. How do I avoid it? (if appropriate)

Some background information: I use samba-3.0.24 on debian/etch with an 
openldap-2.3.32 backend. Eventually I want to setup a domain using a 
samba PDC and BDC's, but with understanding the process in order to 
obtain a robust setup.

kind regards,
Frank Meisschaert

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Frank Meisschaert wrote:
> 1. Why is a sambaDomainName=ALTA entry created while I 
>    specified a workgroup of TDOM?
> 2. How do I avoid it? (if appropriate)
The domain name for a server's SAM depends on the
server configuration (see get_global_sam_name() in the
source code).  So for standalone and member servers,
the machine's SAM domain is the machine name.  FOr a
Samba DC, the SAM name is the domain/workgroup name.




cheers, jerry

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGQ2OVIR7qMdg1EfYRAqEDAKDC//HvYr9T5GMuFCyknb7yoykMNACcCvQ7
al9u0t+APfNNrlquBHJLc0s=Vevh
-----END PGP SIGNATURE-----