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 Volker Lendecke wrote: > On Tue, May 12, 2009 at 03:28:07PM +0900, Yasuma Takeda wrote: >>> That won't work. Your only chance is Samba 3.3.4 with >>> >>> HKLM\System\CCS\Services\LanmanWorkstation\Parameters >>> DWORD DomainCompatibilityMode = 1 >>> DWORD DomainCompatibilityMode = 0 >>> >>> HKLM\System\CCS\Services\Netlogon\Parameters >>> DWORD RequireSignOnSeal = 0 >>> DWORD RequireStrongKey = 0 >>> >>> Haven't tested that yet, but you should get some steps >>> further. >>> >>> Volker >>> >> I succeeded to join Windows 7(RC) to Samba 3.3.4 domain. >> >> 1. I installed Windows 7. >> 2. I changed above 4 parameters by regedit on Windows 7. >> 3. Windows 7 can join to the domain which is provided by Samba 3.3.4. > > Just FYI: I haven't tried myself, but probably the keys in > HKLM\System\CCS\Services\Netlogon\Parameters are not > required, Samba does all the necessary crypto. > > Volker > -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba