Topic: Access denied error to XP client

[Rob Wellesley]

Hi all

I have just installed 8 identical hardware/software PCs all running XP pro SP1 using SME 5.1.2 update3 as the domain controller with roaming profiles

1 pc refuses to joinup. The account creation process goes fine at the linux side but fails at the smbpasswd side.

This is indicated in the attached log and also "visually" i.e. machine name present in /etc/passwd /etc/shadow but not in /etc/smbpasswd

The errors are "access denied" or it will appear to join but only the admin account has access.

All PCs have been regedited

Changing the removing the account and/or changing the computer name and trying to rejoin goes no where.

Any ideas??  Any ideas on using a manual "add user script" In an e-smith environment?

[2002/10/21 16:08:07, 0] lib/util_sock.c:matchname(955)
host name/name mismatch: pc-00077 != pc-00077.grantcameron.co.nz
[2002/10/21 16:08:07, 0] lib/util_sock.c:get_socket_name(1008)
Matchname failed on pc-00077 192.168.1.77
[2002/10/21 16:08:07, 0] rpc_server/srv_netlog_nt.c:get_md4pw(150)
get_md4pw: Workstation alcove1$: no account in domain
[2002/10/21 16:08:07, 0] lib/util_sock.c:matchname(955)
host name/name mismatch: pc-00077 != pc-00077.grantcameron.co.nz
[2002/10/21 16:08:07, 0] lib/util_sock.c:get_socket_name(1008)
Matchname failed on pc-00077 192.168.1.77
[2002/10/21 16:08:08, 0] passdb/pdb_smbpasswd.c:startsmbfilepwent(171)
startsmbfilepwent_internal: unable to open file /etc/smbpasswd. Error was
Permission denied
[2002/10/21 16:08:08, 0] passdb/pdb_smbpasswd.c:pdb_getsampwnam(1368)
unable to open passdb database.
[2002/10/21 16:08:08, 0] passdb/pdb_smbpasswd.c:startsmbfilepwent(171)
startsmbfilepwent_internal: unable to open file /etc/smbpasswd. Error was
Permission denied
[2002/10/21 16:08:08, 0] passdb/pdb_smbpasswd.c:add_smbfilepwd_entry(574)
add_smbfilepwd_entry: unable to open file.
[2002/10/21 16:08:08, 0] rpc_server/srv_samr_nt.c:_api_samr_create_user(1926)
Failed to add entry for user alcove1$.

[Darrell May]

Rob use this HowTo to manually remove all references to the machine you are having issues with:

http://myezserver.com/downloads/mitel/contrib/samba-2.2.5-4/samba-howto.html

Regards,

Darrell

[Rob Wellesley]

Darrell May wrote:
>
> Rob use this HowTo to manually remove all references to the
> machine you are having issues with:

Yep - am using it. In fact your website would be one of our first ports of call. It still won't join - wether we remove and rejoin with the same  or a different name.

Interestingly - it joins our test domain.

rob

[Paul Sahlin]

I'm having the same problem in a PClab with 16 computers. Have installed Ghost Corporate and have cloned the computers. I've successfully cloned them with SID-change (via GhostWalker). The problems that occur:
1) If Ghost enters the cloned PC in the domain, the users can't log in, it says that the domain is not available or busy.
2) If you manually try to enter the cloned PC in the domain, the admin and password fails to enter the machine in the domain.

I tried to use Dan Browns Samba-update How-to, to remove the first cloned PC with the effect that I now can't either enter the cloned PC or any other PC!

Most frustrating. Is the password for UNIX or samba that's corrupt? I tried to make fhe following commands:

passwd
#new password

smbpasswd
#new password

so it fits with the admin password. But not any success. I'm almost losing the faith in rescuing this server.

Regards, Paul

[Paul Sahlin]

I'm sorry Darrel. It's your How-to, not Dan's.

Regards, Paul

[Paul Sahlin]

It's good to explore things by your own. I've learned pretty much about networks and servers by using the SME-solution.
What was the solution?

- I had an account   "admin"  locally as administrator
when I tried to put machines into the domain (with the global admin account) conflict occured, naturally. So I tried to put the machines into the domain by using the account (global) root.
The other way would have been to change the local admin account to administrator or something.

- I had machines in the WORKGROUP with the same name as the DOMAIN.
I changed the workgroupname, and rebooted. Then it worked.

Anyway, this problem gave me good knowledge about smbpasswd and passwd, even if I never needed them.... Who knows in the future?

Cloning with Ghost 7.5E seems to work well.

/Paul