[Samba] Windows 7 Can't Join Samba 3.5.4 PDC

[Michael Wood]

Hi

On 21 July 2011 16:18, Gaiseric Vandal <gaiseric.vandal at gmail.com> wrote:
> On 07/21/2011 09:50 AM, Andrew Niemantsverdriet wrote:
>>
>> Hi all,
>>
>> When trying to join a windows 7 box to a samba 3.5.4 acting as a PDC I
>> am getting an error on the windows 7 box that says
>> DNS_ERROR_NO_DNS_SERVERS (the full error log is included at bottom of
>> mail). WinXP machines are able to join the domain fine, just not
>> windows 7 boxes. My (sanitized) config is located is included at the
>> bottom of the mail.
>>
>> I have tried doing the registry patches to the windows 7 box but am
>> not using those right now. The error persists even with the registry
>> changes applied.
>>
>> Can anybody tell me what I need to do to fix this error?
>>
>>
>>
>> ##############BEGIN CONFIG#######################
>>     [global]
>>     workgroup = RMC2
>>     server string = RMC2
>>     netbios name = TOPAZ
[...]
>
> I don't think you can have the server and domain have the same name.
>  Ideally you would have the following
>    workgroup= DOMAINNAME
>    server string = SERVERNAME
>    netbios name = SERVERNAME

No, "server string" is not the server's name.  It's an arbitrary
string.  Here's the first paragraph of what the manpage says about it:

       server string (G)

           This controls what string will show up in the printer comment box
           in print manager and next to the IPC connection in net view. It can
           be any string that you wish to show to your users.

> And you should have a DNS " A"entry for "servername."
>
> On the samba wiki there are two sets of registry changes.  For Samba 3.5.x
> you should only need one set-  ie. the following
>
> HKLM\System\CCS\Services\LanmanWorkstation\Parameters
>    DWORD  DomainCompatibilityMode = 1
>    DWORD  DNSNameResolutionRequired = 0
>
>
> Is your client configured to use the PDC as its WINS server (this can be
> assigned via DHCP.)  That should help it find the server.  Otherwise it may
> assume that the domain it is looking for is an Active Directory domain-
>  thus the DNS query looking for the non-existent "ldap" active directory
> server.

-- 
Michael Wood <esiotrot at gmail.com>