Security=domain and pdc probs

martin.ejdestig at martin.ejdestig at
Wed Feb 21 07:23:21 GMT 2001


I run a samba server on a tru64 unix system and when I use security=domain I get som problems that I need help with.

First of all, heres the config file I use:


        create mask = 664
        directory mask = 775
        domain logons = yes
        encrypt passwords = yes
        guest account = <guest account>
        hosts allow = <a>.<b>.<c>.
        lock directory = /usr/local/samba/var/locks
        log file = /usr/local/samba/log.%m
        map to guest = Bad User
        password server = <pwd server>
        security = domain
        smb passwd file = /usr/local/samba/private/smbpasswd
        workgroup = <workgroup>

        comment = Home Directory on %L
        browseable = no
        read only = no
        guest ok = no

# And all the shares look somtn like this...

        comment = <some nifty comment>
        path = <path name>
        public = yes
        writable = yes


The pdc in the network is a nt machine. If one boots the nt machine when samba is running on the tru64 unix machine, it seems like the the tru64 unix machine becomes the pdc. When users log on on their nt workstations they get a requester saying:

"A domain controller for your domain could not be contacted. You have been logged on using cached account information. Changes to your profile since you last logged on may not be available."

It seems like everything else works as it should for the users. But when I go to the nt server and start the server manager for example, I get an error requester (can't remember exactly what it was.....but the server manager doesn't work 100% until you stop samba on the tru64 unix machine and then reboot the nt server.....

When you set security = domain does that mean you set the machine samba runs on to a bdc...or whats wrong?....and how do I fix it ;) ?

Thanks in advance....

/Martin Ejdestig

More information about the samba mailing list