Correction to this post as the second DWORD should have been DNSNameResolutionRequired.
However, I'm interested to know why the error message we receive occurs - it seems to me that setting DNSNameResolutionRequired to 0 should also prevent Windows 7 attempting to set its DNS name after the domain join. Regards, Patrick Patrick Rynhart wrote: > Hi Volker, > > We can confirm that only the first two keys (i.e. > DomainCompatibilityMode & DomainCompatibilityMode) are required in order > for Samba 3.3.4 & Windows 7 RC to domain join and interoperate. > > Immediately after a domain join, we have observed the following message > from the Windows 7 client (which appears to be benign as discussed below): > > "Changing the Primary Domain DNS name of this computer to "" failed. > The name will remain "TESTDOMAIN". The error was: > > The specified domain either does not exist or could not be contacted" > > This doesn't appear to impact the client subsequently participating in > the Samba 3 domain, and I presume it is because Windows 7 requests a DNS > name from the DC (which only makes sense in an Active Directory > environment ?) > > Regards, > > Patrick > -- Dr Patrick Rynhart Linux Systems Administrator / Team Leader IT Support Group School of Engineering and Advanced Technology AgHort A Room 3.61 Turitea Campus Massey University NEW ZEALAND Phone +64 6 356 9099 extn 2444 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
