Re: [Samba] Samba4 machine fails to join in samba3 domain
- Date: Wed, 22 May 2019 17:17:50 +0100
- From: Rowland penny via samba <samba@xxxxxxxxxxxxxxx>
- Subject: Re: [Samba] Samba4 machine fails to join in samba3 domain
On 22/05/2019 16:40, Julien TEHERY via samba wrote:
Louis is right, you should upgrade, but, in the meantime, try adding
'ntlm auth = yes' to your smb.conf, see if that helps.
I was trying to find out if the computer had actually joined, but was
mis-reporting that it wasn't, if it had 'net getdomainsid' would have
given you two SID's
Yes they should upgrade, I totally agree. I've allready migrated
samba3 domain to samba4 domain , but in this case the samba4 one is
only a fileserver that was joined in a microsoft/AD domain. People
from the samba3 domain used to access their home on it through
bidirectionnal approbation approval between the microsoft domain and
Now they have to break this approval to upgrade their forest
functionnal level. That's why we try to integrate this samba4
fileserver into the old samba3 domain, so that users can still have
access to their homes.
Also try running the following commands:
I tried with the ntlm_auth option whitout success.
I won't bother your with samba3 problems, but can somebody explain
what root's SID has to deal with the "net rpc join" command?
I precise this SID does exists in the samba3 (target) domain and the
SID is the same as shown in my first email.
I think your problem may just be that Samba 3.5.x is just too old to
allow Samba 4 to join, 3.5 went EOL at the end of 2013 and it was very
different from 3.6 (which is also EOL)
To unsubscribe from this list go to the following URL and read the