[Samba] Fwd: Not able to join windows 10 clients to samba 3.6.23 NT4 Style PDC

[Ram Prasad Bikkina]

Hi Gaiseric,

Thank you for quick reply. I configured my PDC as WINS server and
specified "IP of PDC".

I observed some errors in NMBD log,  "become_domain_master_query
failed". I am googling these errors.



On Mon, May 16, 2016 at 6:57 PM, Gaiseric Vandal
<gaiseric.vandal at gmail.com> wrote:
> If this is an NT4-style domain, then DNS is not essential.    Things like
> SRV records aren't relevant since a lot of the NT4 is back from the NetBios
> days.        It looks like your Win 10 machine thinks it is trying to join
> an AD domain.      Windows clients machines typically are using DNS to
> resolve server names to IP addresses.   However DNS does not provide info on
> locating PDC's and BDC's.  That is better handled with the use of a WINS
> server (Windows Internet Naming) which is basically name looking up for
> "netbios" names and services.
>
> I have configured my PDC to be the WINS server.
>
>
> In my smb.conf on member server
>
>    security = domain
>    domain master = no
>    domain logons = no
>     name resolve order =  host wins  bcast
>     workgroup = MYDOMAIN
>     wins server = IP_OF_PDC
>
>
>
> For a classic domain, make sure you have NOT disable NBT (netbios over
> tcp/ip) on the client machines.  By default it is left enabled.
>
>
> On 05/14/16 00: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:
>>
>>   192.168.1.2
>>
>>   - One or more of the following zones do not include delegation to its
>> child zone:
>>
>>   samba.local
>>   local
>>   . (the root zone)
>>
>>
>>
>> On Fri, May 13, 2016 at 6:28 PM, Gaiseric Vandal
>> <gaiseric.vandal at gmail.com>
>> wrote:
>>
>>> The registry changes for Windows 7 also apply to Windows 10
>>>
>>> https://wiki.samba.org/index.php/Required_settings_for_NT4-style_domains
>>>
>>>
>>>
>>>
>>>
>>>
>>> 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
>>>
>
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba