|
Question : Win2k Pro Cannot join a certain domain
|
|
Here is the situation:
Working here at the school district, we have several domains. We will call them lakota, lakotabizlab, whscs. A computer removed from domain lakota and placed in domain whscs will join correctly. However, it will not join domain lakotabizlab if it is a windows 2000 machine. Windows XP will join the domain. I have tried several 2000 machines on different network Jacks.
The error I get is: The following error occurred attempting to join the domain "lakotabizlab"; The network path was not found.
There are machines currently in this domain and File and printer sharing is ENABLED on the server
I found some interesting output in the netsetup.log.. see below. Notice the first section is SUCCESSFULLY joining a domain. Take note of the machine name it finds at 15:43:08
12/11 15:43:05 -----------------------------------------------------------------
12/11 15:43:05 NetpValidateName: checking to see if 'lakota' is valid as type 3 name
12/11 15:43:05 NetpCheckDomainNameIsValid [ Exists ] for 'lakota' returned 0x0
12/11 15:43:05 NetpValidateName: name 'lakota' is valid for type 3
12/11 15:43:08 -----------------------------------------------------------------
12/11 15:43:08 NetpDoDomainJoin
12/11 15:43:08 NetpMachineValidToJoin: 'WH229LAB12'
12/11 15:43:08 NetpGetLsaPrimaryDomain: status: 0x0
12/11 15:43:08 NetpMachineValidToJoin: status: 0x0
12/11 15:43:08 NetpJoinDomain
12/11 15:43:08 Machine: WH229LAB12
12/11 15:43:08 Domain: lakota
12/11 15:43:08 MachineAccountOU: (NULL)
12/11 15:43:08 Account: lakota\xxxxx
12/11 15:43:08 Options: 0x27
12/11 15:43:08 OS Version: 5.0
12/11 15:43:08 Build number: 2195
12/11 15:43:08 ServicePack: Service Pack 3
12/11 15:43:08 NetpValidateName: checking to see if 'lakota' is valid as type 3 name
12/11 15:43:08 NetpCheckDomainNameIsValid [ Exists ] for 'lakota' returned 0x0
12/11 15:43:08 NetpValidateName: name 'lakota' is valid for type 3
12/11 15:43:08 NetpDsGetDcName: trying to find DC in domain 'lakota', flags: 0x1020
12/11 15:43:08 NetpDsGetDcName: found DC '\\LLSDDC01' in the specified domain
12/11 15:43:09 NetpJoinDomain: status of connecting to dc '\\LLSDDC01': 0x0
12/11 15:43:09 NetpGetLsaPrimaryDomain: status: 0x0
12/11 15:43:09 NetpLsaOpenSecret: status: 0xc0000034
12/11 15:43:09 NetpGetLsaPrimaryDomain: status: 0x0
12/11 15:43:09 NetpLsaOpenSecret: status: 0xc0000034
12/11 15:43:09 NetpManageMachineAccountWithSid: NetUserAdd on '\\LLSDDC01' for 'WH229LAB12$' failed: 0x8b0
12/11 15:43:09 NetpManageMachineAccountWithSid: status of attempting to set password on '\\LLSDDC01' for 'WH229LAB12$': 0x0
12/11 15:43:09 NetpJoinDomain: status of creating account: 0x0
12/11 15:43:09 NetpJoinDomain: status of setting netlogon cache: 0x0
12/11 15:43:09 NetpGetLsaPrimaryDomain: status: 0x0
12/11 15:43:10 NetpSetLsaPrimaryDomain: for 'LAKOTA' status: 0x0
12/11 15:43:10 NetpJoinDomain: status of setting LSA pri. domain: 0x0
12/11 15:43:10 NetpJoinDomain: status of managing local groups: 0x0
12/11 15:43:11 NetpJoinDomain: status of setting ComputerNamePhysicalDnsDomain to 'lakota.spi': 0x0
12/11 15:43:12 NetpJoinDomain: status of starting Netlogon: 0x0
12/11 15:43:12 NetpWaitForNetlogonSc: waiting for netlogon secure channel setup...
12/11 15:43:14 NetpWaitForNetlogonSc: status: 0x0, sub-status: 0x0
12/11 15:43:14 NetpJoinDomain: status of disconnecting from '\\LLSDDC01': 0x0
12/11 15:43:14 NetpDoDomainJoin: status: 0x0
--Now look at the failed attempt to join the other domain-
Notice 15:30:52 The domain controller it finds is lls_bizlab.lakotabizlab Though this is the FQDN of the server, it is not the netbios name therefore it cannot connect to the domain controller to create the computer account.
12/11 15:30:32 -----------------------------------------------------------------
12/11 15:30:32 NetpValidateName: checking to see if 'lakotabizlab' is valid as type 3 name
12/11 15:30:32 NetpCheckDomainNameIsValid [ Exists ] for 'lakotabizlab' returned 0x0
12/11 15:30:32 NetpValidateName: name 'lakotabizlab' is valid for type 3
12/11 15:30:37 -----------------------------------------------------------------
12/11 15:30:37 NetpDoDomainJoin
12/11 15:30:37 NetpMachineValidToJoin: 'WH229LAB12'
12/11 15:30:37 NetpGetLsaPrimaryDomain: status: 0x0
12/11 15:30:37 NetpMachineValidToJoin: status: 0x0
12/11 15:30:37 NetpJoinDomain
12/11 15:30:37 Machine: WH229LAB12
12/11 15:30:37 Domain: lakotabizlab
12/11 15:30:37 MachineAccountOU: (NULL)
12/11 15:30:37 Account: lakotabizlab\xxxx
12/11 15:30:37 Options: 0x27
12/11 15:30:37 OS Version: 5.0
12/11 15:30:37 Build number: 2195
12/11 15:30:37 ServicePack: Service Pack 3
12/11 15:30:37 NetpValidateName: checking to see if 'lakotabizlab' is valid as type 3 name
12/11 15:30:37 NetpCheckDomainNameIsValid [ Exists ] for 'lakotabizlab' returned 0x0
12/11 15:30:37 NetpValidateName: name 'lakotabizlab' is valid for type 3
12/11 15:30:37 NetpDsGetDcName: trying to find DC in domain 'lakotabizlab', flags: 0x1020
12/11 15:30:52 NetpDsGetDcName: failed to find a DC having account 'WH229LAB12$': 0x525
12/11 15:30:52 NetpDsGetDcName: found DC '\\LLS_BIZLAB.LakotaBizlab' in the specified domain
12/11 15:30:52 NetUseAdd to \\LLS_BIZLAB.LakotaBizlab\IPC$ returned 53
12/11 15:30:52 NetpJoinDomain: status of connecting to dc '\\LLS_BIZLAB.LakotaBizlab': 0x35
12/11 15:30:52 NetpDoDomainJoin: status: 0x35
Again, there are currently machines in this "trouble" domain and you can add an XP machine to the domain. But no win2kpro
I fear it is a DNS issue?? I have reinstalled DNS on the DC of the domain experiencing the problems to no avail. I have tried manually pointing the DNS server to other servers as well.
This is driving me nuts!! Thanks!
|
Answer : Win2k Pro Cannot join a certain domain
|
|
Reinstalling doesn't fix configuration issues. It appears that you have some type of problem with that domain in DNS. Without seeing it, it's hard to know what that is. Are the servers dynamically registering in DNS? Is there anything different in DNS regarding this domain?
|
|
|
|
|
