Red Hat Bugzilla – Bug 459304
Cannot join Windows 2003 domain with RHEL 4.7 Samba
Last modified: 2010-10-22 23:48:01 EDT
Description of problem:
Using Samba included with RHEL 4.7, I cannot join any machines to our domain using net rpc join.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Set up RHEL 4.7
2. Set up smb.conf to use DOMAIN authentication (see attached config file)
3. Attempt to join domain with 'net rpc join -U Administrator -w DOMAINNAME'
Failure -- NT_STATUS_UNSUCCESSFUL. -d 4 output shows:
2008/08/15 11:42:37, 3] libsmb/trusts_util.c:just_change_the_password(57)
just_change_the_password: unable to setup creds (NT_STATUS_NO_TRUST_SAM_ACCOUNT)!
[2008/08/15 11:42:37, 1] utils/net_rpc.c:run_rpc_command(170)
rpc command function failed! (NT_STATUS_NO_TRUST_SAM_ACCOUNT)
Connection failed: NT_STATUS_UNSUCCESSFUL
A successful join.
If I downgrade to samba-3.0.25b-1.el4_6.5 (included with RHEL 4.6), everything works perfectly. I will attach a -d 4 dump of the join attempt. In addition, see this thread:
I have verified that there were no other objects in AD that might have conflicting names.
I am currently sticking with the older version of Samba to retain functionality.
workgroup = DOMAIN
netbios name = RHEL47TEST
security = DOMAIN
log file = /var/log/samba/%m.log
max log size = 500
wins server = 10.1.1.1
dns proxy = no
log level = 10
password server = *
#username map = /etc/samba/username.map
#log level = 0
socket options = TCP_NODELAY
I have opened SR #1850772 for this issue as well.
This issue has already been fixed upstream (http://git.samba.org/?p=samba.git;a=commitdiff;h=d29db976dcffef772044b1e5246ec6715d6afbbb), if that is an option for you, you can workaround it if you call:
net rpc join -U Administrator%password -w DOMAINNAME
Thanks. Support provided me with some scratch RPM's including the patch and these work fine. Hopefully will see this in an errata release shortly.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.