Koozali.org: home of the SME Server

Legacy Forums => Experienced User Forum => Topic started by: Buddha_Joe on October 21, 2004, 08:32:15 PM

Title: getting XP to join SME hosted domain
Post by: Buddha_Joe on October 21, 2004, 08:32:15 PM

I'm trying to setup my SME 6.01 server as a domain controler.

I Installed the advworkgroup contrib and every thing looks fine. When I try to get my XP Pro machine to join the domain it eventually comes back and say's access denied. At first I thought it was XP. I searched the forums and followed every bit of advice I could find (reg hacks, Local Security policies etc..). I even went so far as to wipe the machine and go with a fresh install and I kept getting the error.

I checked the messages log on the server and found the following:

Code: [Select]



e-smith[9028]: Processing event: machine-account-create xplaptop$
e-smith[9028]: Running event handler: /etc/e-smith/events/machine-account-create/S10create-machine-account
e-smith[9028]: create-machine-account xplaptop$: Creating Unix user and group
e-smith[9028]: useradd: unable to lock password file
e-smith[9028]: Failed to create account xplaptop$.


I was thinking about upgrading samba. anyone have any other ideas?

Title: getting XP to join SME hosted domain
Post by: gzartman on October 22, 2004, 05:50:36 AM

Uninstall the advanced workgroup contrib and try again.  

Greg

Title: getting XP to join SME hosted domain
Post by: Buddha_Joe on October 23, 2004, 03:31:13 AM

I removed the advworkgroup contrib and tried again. Still getting access denied on the xp box.

Server log is still reporting the following:

Code: [Select]


Processing event: machine-account-create xplaptop$
Running event handler: /etc/e-smith/events/machine-account-create/S10create-machine-account
create-machine-account xplaptop$: Creating Unix user and group
useradd: unable to lock password file
Failed to create account xplaptop$


Title: getting XP to join SME hosted domain
Post by: girkers on October 23, 2004, 03:33:15 AM

I found when I was having this sort of trouble it turned out to be a DNS problem.  I use static IPs in my "Domain" with my SME 6.01 box being the DNS server.

I found that when I had the IP address of my DNS server as the SME server it worked.  I did have another problem recently when that was not enough and I found a patch for TinyDNS.

When I applied the patch to have DHCP synchronised to DNS it was fine.  Try this:

http://www.activeservice.co.uk/sme/contribs/

I installed the RPM and all was good. Let me know how you go.

Title: getting XP to join SME hosted domain
Post by: Buddha_Joe on October 23, 2004, 05:51:41 AM

Unfortunetly I already have that one installed. Thanks for the idea. Though I don't see how that would be preventing the system from locking the password file.

Title: getting XP to join SME hosted domain
Post by: Buddha_Joe on October 24, 2004, 02:19:51 AM

I just tried to see if anyhting was holding the passwd file open using "lsof" but did not find anyhting with that file open. I also did some checking on google and the only thing I have found so far refers to permissons (ie you need to be root).

I checked the groups that admin belongs to and it is a member of root. I noticed however that the passwd file only has read access set to memebers of the root group. I added write access and I still have the same problem. I set the permissions back to the way they were and am heading back to google. If anyone else has any other ideas they would be welcomed.. and of course if I find a fix first I'll post it.

Title: getting XP to join SME hosted domain
Post by: Buddha_Joe on October 24, 2004, 03:30:34 AM

What account is being used to run the event scripts? I assume they are be run as root.

Title: getting XP to join SME hosted domain
Post by: arne on October 24, 2004, 11:54:32 AM

http://forums.contribs.org/index.php?topic=24130.0

Title: getting XP to join SME hosted domain
Post by: Buddha_Joe on October 25, 2004, 06:08:20 AM

arne:

Thanks.. been there and tried that already though.

That still doesn't explain the error in the messages log about useradd not being able to lock the password file.