Description of problem:
We have SAMBA PDC Domain with domain name "example.com". Clients from windows XP and windows 7 are able to login without problem. If we are trying to join windows 10 PC. It produces error "Domain Could not be found. Check the domain name and try". If I have changed the domain name to "example" in smb.conf file( I removed "." from workgroup name, If I add again "." in workgroup name I was not able to join windows 8 and 10 clients) then I am able to join windows xp, 7, 8 and 10 without problem. What could be the problem. Our entire setup is using "example.com" domain name. If I change this to "example". It will be very panic job to us to migrate entire environment. Is there any way to join windows 10 PC into domain by keeping "example.com" domain name. We have tried with RHEL 6.7 with samba 3.6 also but the problem is same. Please help us in this regard. I have raised the support case to REDHAT Support Team for further analysis. Support Case Number is "01634476". We have posted this problem into SAMBA group also.
Version-Release number of selected component (if applicable):
SAMBA PDC is able to support windows 10 if we change the domain name without ".com" i.e changing from "example.com" to "example".
Steps to Reproduce:
a) After Windows 7 Microsoft doesn't support joining a NT4 DC by default anymore.
It is only possible with several hacks .
b) A workgroup (netbios name) is normally not using any dots, it is possible but
not recommended. As you're using a dot, Windows thinks it is a DNS name for an
AD domain and not an NT4-style workgroup.
c) Also Samba 3.6 is very old (released 2011) and Windows 10 has been released
end of last year. Samba 3.6 doesn't support a lot of things Windows 10
I'm sorry but don't expect support for Windows 10 with Samba 3.6.
Just to be clear, we support running Samba as a PDC. But if Mircosoft decides to drop support for joining workstations to a NT4-style domain controller, it isn't Samba who is at fault.
Also note that Samba 3.6 is several years old. You should use a newer Samba version (4.2 or newer) and try your luck with that version. It might be that it works with newer protocol versions supported by newer Samba versions.