Description of problem: I get the following when doing a "net join" to add a new FC7 machine to a samba domain: [2007/09/13 13:49:29, 0] utils/net_rpc_join.c:net_rpc_join_newstyle(304) error setting trust account password: NT code 0x1c010002 Unable to join domain SOUTHPARK. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
What samba version is running on the "Samba Domain" ?
samba-3.0.23a-1 on the domain controller and samba-3.0.26a-0 on the client
what user are you using to do the join? what does the PDC logs say ?
On client machine named tweak: net join -U <userid here> On PDC: tweak.log: Use of uninitialized value in string at /usr/lib/perl5/vendor_perl/5.8.6/smbldap _tools.pm line 291. Use of uninitialized value in string at /usr/lib/perl5/vendor_perl/5.8.6/smbldap _tools.pm line 291. [2007/09/13 15:30:07, 0] rpc_parse/parse_prs.c:prs_mem_get(559) prs_mem_get: reading data of size 2 would overrun buffer by 1 bytes. [2007/09/13 15:30:07, 0] rpc_server/srv_samr.c:api_samr_set_userinfo(848) api_samr_set_userinfo: Unable to unmarshall SAMR_Q_SET_USERINFO. [2007/09/13 15:30:07, 0] rpc_server/srv_pipe.c:api_rpcTNP(2287) api_rpcTNP: samr: SAMR_SET_USERINFO failed. 10.0.1.6.log: [2007/09/13 15:30:00, 0] rpc_server/srv_netlog_nt.c:get_md4pw(242) get_md4pw: Workstation TWEAK$: no account in domain [2007/09/13 15:30:00, 0] rpc_server/srv_netlog_nt.c:_net_auth_2(461) _net_auth2: failed to get machine password for account TWEAK$: NT_STATUS_ACCES S_DENIED
Looks like there is some problems with smbldap_tools on the PDC, can you successfully join windows servers/clients to the domain ?
No, there is not a problem with smbldap_tools. I am able to join the domain just fine with a Fedora Core 4 client running samba-3.0.23a-1. Please see http://lists-archives.org/samba/31956-winbind-3-0-25c-problem-joining-3-0-24-domain.html Apparently this bug was introduced in samba 3.0.25? I was hoping it was fixed in 3.0.26, but apparently not.
Seem a different problem, but during the 3.0.23 dev series we found a bug in the server side code we fixed in later releases. This is a server bug, but you see the effect on the client as the client has the fix and the server not. I will investigate to see if the client fix has some unwanted side effects, meanwhile a stop gap solution is to upgrade your PDC to a post 3.0.24 release.
Thank you. I rebuilt the 3.0.26 rpm from Fedora 7 and installed it on the PDC and everything works ok now. You might want to warn anyone post 3.0.24 that it doesn't like a <=3.0.24 PDC. Looks like Fedora 7 was the first version to include samba > 3.0.24. You are welcome to close this ticket now.
I guess we can mark this as not a bug (not of this release) as it works using recent releases.