11090 » A Windows Server 2003 computer cannot join a domain after you upgrade it to SP1 (Service Pack 1)? (13-Dec-06)

12/11 14:23:06 NetpDoDomainJoin
12/11 14:23:06 NetpMachineValidToJoin: 'NewServer'
12/11 14:23:06 NetpGetLsaPrimaryDomain: status: 0x0
12/11 14:23:06 NetpMachineValidToJoin: status: 0x0
12/11 14:23:06 NetpJoinDomain
12/11 14:23:06 Machine: NewServer
12/11 14:23:06 Domain: JSIINC.com
12/11 14:23:06 MachineAccountOU: (NULL)
12/11 14:23:06 Account: JSIINC\administrator
12/11 14:23:06 Options: 0x25
12/11 14:23:06 OS Version: 5.2
12/11 14:23:06 Build number: 3790
12/11 14:23:06 ServicePack: Service Pack 1, v.2438
12/11 14:23:06 NetpValidateName: checking to see if JSIINC.com is valid as type 3 name
12/11 14:23:06 NetpValidateName: JSIINC.com is not a valid NetBIOS domain name: 0x7b
12/11 14:23:06 NetpCheckDomainNameIsValid [ Exists ] for JSIINC.com returned 0x0
12/11 14:23:06 NetpValidateName: name JSIINC.com is valid for type 3
12/11 14:23:06 NetpDsGetDcName: trying to find DC in domain JSIINC.com, flags: 0x1020
12/11 14:23:06 NetpDsGetDcName: found DC \\PDC.JSIINC.com in the specified domain
11/02 11:07:38 NetUseAdd to \\PDC.JSIINC.com\IPC$ returned 59
11/02 11:07:38 NetpJoinDomain: status of connecting to dc \\PDC.JSIINC.com: 0x3b
11/02 11:07:38 NetpDoDomainJoin: status: 0x3b

This behavior occurs if the Impersonate a client after authentication policy is defined for a GPO (Group Policy Object) that is linked to the domain.

To workaround this problem:

1. Open a CMD.EXE window on the Windows Server 2003 SP1 computer that cannot join the domain.

2. Type CACLS %SystemRoot%\System32\Svchost.exe /E /G "NETWORK SERVICE":F and press Enter.

End of Article