[Samba] Fwd: Not able to join windows 10 clients to samba 3.6.23 NT4 Style PDC
rpenny at samba.org
Sat May 14 08:10:42 UTC 2016
On 14/05/16 05:10, Ram Prasad Bikkina wrote:
> ---------- Forwarded message ----------
> From: Ram Prasad Bikkina <parvathiprasadb at gmail.com>
> Date: Sat, May 14, 2016 at 9:39 AM
> Subject: Re: [Samba] Not able to join windows 10 clients to samba 3.6.23
> NT4 Style PDC
> To: gaiseric.vandal at gmail.com
> Hi Gaiseric Vandal,
> I applied these registry settings in my windows 10 PC but not able to join.
> It is getting below error.
> Note: This information is intended for a network administrator. If
> you are not your network's administrator, notify the administrator
> that you received this information, which has been recorded in the
> file C:\Windows\debug\dcdiag.txt.
> The following error occurred when DNS was queried for the service
> location (SRV) resource record used to locate an Active Directory
> Domain Controller (AD DC) for domain "samba.local":
> The error was: "DNS name does not exist."
> (error code 0x0000232B RCODE_NAME_ERROR)
> The query was for the SRV record for _ldap._tcp.dc._msdcs.samba.local
> Common causes of this error include the following:>
> - The DNS SRV records required to locate a AD DC for the domain are
> not registered in DNS. These records are registered with a DNS server
> automatically when a AD DC is added to a domain. They are updated by
> the AD DC at set intervals. This computer is configured to use DNS
> servers with the following IP addresses:
> - One or more of the following zones do not include delegation to its
> child zone:
> . (the root zone)
> On Fri, May 13, 2016 at 6:28 PM, Gaiseric Vandal <gaiseric.vandal at gmail.com>
>> The registry changes for Windows 7 also apply to Windows 10
>> On 05/13/16 08:17, Ram Prasad Bikkina wrote:
>>> I prepared samba PDC and not able to join windows 10 clients. Please
>>> suggest any windows 10 registry settings.
>> To unsubscribe from this list go to the following URL and read the
>> instructions: https://lists.samba.org/mailman/options/samba
Have you also set 'max protocol = nt1' in the PDC smb.conf ?
If this is a new domain, can I suggest you use an AD domain instead.
Windows isn't supposed to work with an NT4-style domain since Version 7
(this is Microsofts view, not mine) and as such, Microsoft could make
the registry hacks inoperative at any time.
The other concern is that the Samba 3.6 series is now EOL and is only
supported by the distros that still use it.
More information about the samba