I'm attempting to join a Win7 Pro machine running on lion through Parallels 7 to
Parallels is set to use briged ethernet adapter, DNS has been set to our internal servers, can ping the domain controller by IP and hostname. Gateway & Subnet are correct. I've applied the registry edits win7 needs to connect to samba shares:
HKLM\System\CCS\Services\LanmanWorkstation\Parameters DWORD DomainCompatibilityMode = 1 DWORD DNSNameResolutionRequired = 0
Am I overlooking something?
4/19 I think I may have isolated the issue. Checking the Windows NetSetup log, it appears that the registry tweaks required to join a win7 machine to our Samba Domain Controller are not sticking, despite being correctly set to the values above in the registry editor. The values for DomainCompatabilityMode & DNSNameResolutionRequired are defaulting to incorrect values, which I am thinking is preventing the join.
04/19/2012 11:25:31:685 NetpDoDomainJoin 04/19/2012 11:25:31:685 NetpMachineValidToJoin: 'LOADMACHINE' 04/19/2012 11:25:31:685 OS Version: 6.1 04/19/2012 11:25:31:685 Build number: 7601 (7601.win7sp1_rtm.101119-1850) 04/19/2012 11:25:31:685 ServicePack: Service Pack 1 04/19/2012 11:25:31:685 SKU: Windows 7 Professional 04/19/2012 11:25:31:685 NetpDomainJoinLicensingCheck: ulLicenseValue=1, Status: 0x0 04/19/2012 11:25:31:685 NetpGetLsaPrimaryDomain: status: 0x0 04/19/2012 11:25:31:685 NetpMachineValidToJoin: status: 0x0 04/19/2012 11:25:31:685 NetpJoinDomain 04/19/2012 11:25:31:685 Machine: LOADMACHINE3CB3 04/19/2012 11:25:31:685 Domain: DOMAINNAME 04/19/2012 11:25:31:685 MachineAccountOU: (NULL) 04/19/2012 11:25:31:685 Account: DOMAINNAME\root 04/19/2012 11:25:31:685 Options: 0x27 04/19/2012 11:25:31:685 NetpLoadParameters: loading registry parameters... 04/19/2012 11:25:31:685 NetpLoadParameters: DNSNameResolutionRequired not found, defaulting to '1' 0x2 04/19/2012 11:25:31:685 NetpLoadParameters: DomainCompatibilityMode not found, defaulting to '0' 0x2 04/19/2012 11:25:31:685 NetpLoadParameters: status: 0x2 04/19/2012 11:25:31:685 NetpValidateName: checking to see if 'DOMAINNAME' is valid as type 3 name 04/19/2012 11:25:31:794 NetpCheckDomainNameIsValid [ Exists ] for 'DOMAINNAME' returned 0x0 04/19/2012 11:25:31:794 NetpValidateName: name 'DOMAINNAME' is valid for type 3 04/19/2012 11:25:31:794 NetpDsGetDcName: trying to find DC in domain 'DOMAINNAME', flags: 0x40001010 04/19/2012 11:25:31:794 NetpDsGetDcName: failed to find a DC in the specified domain: 0x54b, last error is 0x0 04/19/2012 11:25:31:794 NetpJoinDomainOnDs: NetpDsGetDcName returned: 0x54b 04/19/2012 11:25:31:794 NetpJoinDomainOnDs: Function exits with status of: 0x54b 04/19/2012 11:25:31:794 NetpDoDomainJoin: status: 0x54b
Viewing these values (DomainCompatibilityMode & DNSNameResolutionRequired) in regedit clearly shows that they are set to the appropriate values of: DomainCompatibilityMode=1 DNSNameResolutionRequired=0
Now I am left wondering why NetpLoadParameters is not 'seeing' these added values, and defaulting to the incorrect ones.