Hello and thank you for reading my post. My problem is about joining Windows machines to a Samba3 domain. Below is what happened: 1) I installed the three servers DHCPD, BIND9 and SAMBA on a machine A running Debian Wheezy. I managed to join all the Windows machines in the LAN to the Samba3 domain properly. I insist on the fact that, at this point, everything was running properly: I could see and access all the shares in the LAN. 2) Then, I tried to join a brand new Windows Server 2012 R2 to the domain and it failed. 3) I decided to install Samba4 on the machine A. I couldn't make it work because I do not have enough time presently to set up a Samba4 server as it's not straightforward. So I decided to revert to the previous configuration with a Samba3 server. After I did this nothing was working anymore. The Windows machines failed to join the domain. 4) So I reinstalled on another machine B running Debian Wheezy the triplet of services DHCPD, BIND9, SAMBA3. Here is the problem: now, every time I try to join a Windows machine to the domain (whether it is an XP, a 7 or a Server 2003 OS) it fails with the message: Can you help me solve that problem? I've been checking my configurations: they look correct. I don't know if there is something to do either on the Samba3 server or on the Windows machines or on both of them to make this work again. Best regards. -- View this message in context: http://samba.2283325.n4.nabble.com/Join-Windows-machines-to-a-Samba3-domain-tp4659356.html Sent from the Samba - General mailing list archive at Nabble.com.
I really need some help. Every time I try to join the Samba3 domain from any Windows machine in my LAN I get the same message (see my previous post: "An Active Directory Domain Controller (AD DC) for the domain "MY_DOMAIN" could not be contacted. [...]"). This didn't use to happen before I introduced a Samba4 domain controller in this very same LAN. Presently, the machine which was running the Samba4 domain controller is shutdown. The only running domain controller is a Samba3 domain controller which is configured the way I usually do, a way which has perfectly worked for years now. I have tried "millions" of things both on the server and on the Windows machines and I can't still make it work. It's driving me mad. Thank you and best regards. -- View this message in context: http://samba.2283325.n4.nabble.com/Join-Windows-machines-to-a-Samba3-domain-tp4659356p4659386.html Sent from the Samba - General mailing list archive at Nabble.com.
Thank you for your answer. Below are some details about the Samba3 configuration which usually works for me. === MAIN CONFIGURATION FILE /etc/smb.conf == === DOMAIN USERS' GROUP == === MACHINES == === USERS == === SHARE == Below are some details about the BIND9 server and DHCPD server configurations which usually works for me. - I have two zone files for name resolution and reverse name resolution. - The BIND9 and DHCPD are set to work together: when an IP is delivered by the DHCPD server to a client machine, the BIND9 zone files are updated automatically. =====I have to say that, at the time, it took me a lot of time to make all this work properly. Also, even if I agree with you (I wasn't cautious enough), I think that it's wrong not to be able to revert to the previous state. Yet I don't know who is to blame for this. You didn't really answered my question: it's not possible to force the Windows clients to work as they used to? I just read in that document: http://wiki.samba.org/index.php/Samba4/samba-tool/domain/classicupgrade/HOWTO the following sentence: I wish I could know what happened which is not reversible. Thank you for helping. -- View this message in context: http://samba.2283325.n4.nabble.com/Join-Windows-machines-to-a-Samba3-domain-tp4659356p4659413.html Sent from the Samba - General mailing list archive at Nabble.com.