Windows 7 Pro unable to join my Linux PDC

From my Windows 7 Pro laptop I'm unable to join my Linux Samba (3.3.4) PDC. Here's what happens.

1. After modifying the LanManagerWorkstation keys I rebooted the laptop.
2. I then go to the Computer properties and navigate to the Computer Name tab
3. I click the "Change" button and enter my inux Samba domain name
4. I receivethe prompt for the username and password
5. I enter root, and root Samba password

After about 30-40 second the connection fails and presents me with the message that the domain either doesn't exist or can be contacted.

Thi doesn't make any sense because I can create mapped drives to the Linux server using any of the user credentials I created in my smbpasswd file from Samba. Isn't creating mapped drives the same authentication process in Windows 7 as when joining a domain?

I need help bad. I've bee at this for about a week. Search all over the Internet with no solution.

I am very much out of my depth here, but... have you installed smbfs on the Linux machine? It's separate from samba4 etc... I've never gotten Windows/Linux communication through Samba to work right without installing smbfs.

To my understanding smbfs is just a feature of mounting filesystems. I want to do more than to just mount filesystems between my Windows and Linux platforms.

Here's some output from c:\Windows\debug\NetSetup.log which really doesn't indicate much. But it's all Windows is giving me. Nothing is reported to the event manager.


12/09/2010 22:23:57:399 NetpDoDomainJoin
12/09/2010 22:23:57:399 NetpMachineValidToJoin: 'LANPC1'
12/09/2010 22:23:57:399 OS Version: 6.1
12/09/2010 22:23:57:399 Build number: 7600 (7600.win7_gdr.100618-1621)
12/09/2010 22:23:57:405 SKU: Windows 7 Professional
12/09/2010 22:23:57:405 NetpDomainJoinLicensingCheck: ulLicenseValue=1, Status: 0x0
12/09/2010 22:23:57:406 NetpGetLsaPrimaryDomain: status: 0x0
12/09/2010 22:23:57:406 NetpMachineValidToJoin: status: 0x0
12/09/2010 22:23:57:406 NetpJoinDomain
12/09/2010 22:23:57:406 Machine: LANPC1
12/09/2010 22:23:57:406 Domain: njhome
12/09/2010 22:23:57:406 MachineAccountOU: (NULL)
12/09/2010 22:23:57:406 Account: njhome\root
12/09/2010 22:23:57:406 Options: 0x27
12/09/2010 22:23:57:406 NetpLoadParameters: loading registry parameters...
12/09/2010 22:23:57:406 NetpLoadParameters: DNSNameResolutionRequired not found, defaulting to '1' 0x2
12/09/2010 22:23:57:406 NetpLoadParameters: status: DomainCompatibilityMode set to '1'
12/09/2010 22:23:57:406 NetpLoadParameters: status: 0x0
12/09/2010 22:23:57:406 NetpValidateName: checking to see if 'njhome' is valid as type 3 name
12/09/2010 22:23:57:509 NetpCheckDomainNameIsValid [ Exists ] for 'njhome' returned 0x0
12/09/2010 22:23:57:509 NetpValidateName: name 'njhome' is valid for type 3
12/09/2010 22:23:57:509 NetpDsGetDcName: trying to find DC in domain 'njhome', flags: 0x40001020
12/09/2010 22:23:57:512 NetpDsGetDcName: failed to find a DC in the specified domain: 0x54b, last error is 0x0
12/09/2010 22:23:57:512 NetpJoinDomainOnDs: NetpDsGetDcName returned: 0x54b
12/09/2010 22:23:57:512 NetpJoinDomainOnDs: Function exits with status of: 0x54b
12/09/2010 22:23:57:512 NetpDoDomainJoin: status: 0x54b

Microsoft TechNet says:

The following is an example of this error:
07/20 16:51:10 NetpDsGetDcName: trying to find DC in domain 'verylongdomain1', flags: 0x1020
07/20 16:51:11 NetpDsGetDcName: failed to find a DC having account 'A-USHAS2-80C$': 0x525
07/20 16:51:11 NetpDsGetDcName: failed to find a DC in the specified domain: 0x54b
07/20 16:51:11 NetpDoDomainJoin: status: 0x54b

The join process usually tries to find a domain controller that already has a computer account for the computer that is currently being joined to the domain. If such a domain controller is not found, it tries to find another domain controller. The preceding example shows that the join domain operation failed because a domain controller was not located for the specified domain.
To investigate further, run nltest /dsgetdc:< domain-name > and examine the output. If you still receive errors, either the domain really does not exist or there is a transient net error that is preventing domain controller discovery. By running Netdiag.exe and examining the output, you usually can determine the cause. A "Failure to connect to a domain controller" message usually means that transient net errors or insufficient credentials are the cause. Table 10.7 shows some error codes that come under this category.

So I executed their command and my results are:

C:\Users\>nltest /dsgetdc:njhome
DC: \\LNX01
Address: \\LNX01
Dom Name: NJHOME
The command completed successfully
C:\Users\>

MS then says to execute:

C:\Users\>net use \\dcname\ipc$ /u:< domain\user > < password >

So I did, and it worked.

C:\Users\>net use \\lnx01\ipc$ /u:njhome\kevin <password>
The command completed successfully.

Now when Microsoft suggest I use this Ldp tool I recieve an error. When I attempt to bind with the Samba PDC. Maybe its a bug in openldap. I on an ancient RH Linux version so this is a probably cause.

res = ldap_bind_s(ld, NULL, &NtAuthIdentity, 1158); // v.3
{NtAuthIdentity: User='root'; Pwd= <unavailable>; domain = 'njhome'.}
Error <34>: ldap_bind_s() failed: Invalid DN Syntax.
Server error: invalid DN

Is this thread of any help at all?

No it didn't. This is all so confusing. Why does this have to be so #@$% hard?

Lastly. Its weird that I can see the shares whether I'm in anohter workgroup (on my home LAN) or in the workgroup named afer the domain name (NJHOME). Here is the output given when joining as a workgroup member instead of domain member (which fails)

netsetup.log:
...
12/10/2010 23:02:28:880 NetpDoDomainJoin
12/10/2010 23:02:28:880 NetpMachineValidToJoin: 'LANPC1'
12/10/2010 23:02:28:880 OS Version: 6.1
12/10/2010 23:02:28:881 Build number: 7600 (7600.win7_gdr.100618-1621)
12/10/2010 23:02:28:884 SKU: Windows 7 Professional
12/10/2010 23:02:28:885 NetpGetLsaPrimaryDomain: status: 0x0
12/10/2010 23:02:28:885 NetpMachineValidToJoin: status: 0x0
12/10/2010 23:02:28:885 NetpJoinWorkgroup: joining computer 'LANPC1' to workgroup 'NJHOME'
12/10/2010 23:02:28:885 NetpValidateName: checking to see if 'NJHOME' is valid as type 2 name
12/10/2010 23:02:28:886 NetpCheckNetBiosNameNotInUse for 'NJHOME' [ Workgroup as MACHINE] returned 0x0
12/10/2010 23:02:28:887 NetpValidateName: name 'NJHOME' is valid for type 2
12/10/2010 23:02:29:045 NetpSetLsaPrimaryDomain: for 'NJHOME' status: 0x0
12/10/2010 23:02:29:065 NetpJoinWorkgroup: status: 0x0
12/10/2010 23:02:29:065 NetpDoDomainJoin: status: 0x0