Error Joining XP Pro to windows 2003 R2 Server Domain

Hi
I am new to Active directory, we have requirement to move to windows 2003 server,
So to have a feel of the same downloaded the evaluation version of windows 2003 server R2 and had the same installed and also applied the 32 Patches using the auto update.

Having completed the same installed the DNS , Created a primary forward lookup zone for the same serer ip.but found that option "Store the zone in active directory" in "DNS Change Zone type" windows was not getting highlited. Was told that as the active directory is not installed or as the PC is still in a workgroup and not in a domain the same is disabled.

So next moved to the great instalation of Active Directory. Having moved to screens of DNS name for the new domain, gave the sysvol on NTFS.
Now was thrown an error in registration diagnostics window.
So asked the wizard to configure the DNS and complete the instalation.there ended the installation. I ran a dcdiag and it shows all fine

The Domain Name is : nocl.com
the DC server name: nocl-s1

Now I want a windows XP professional PC named "Engineering" to be part of the domain so I can test the Group policy things.

When I try connecting the same to the domain, I get

"The following error occured attempting to join the domain:nocl.com "
Windows cannot find the network path verify that the network path is correct and the destination computer is not busy or turned off. I am sure the same is not turned off.
I am able to ping the server from the client.
I am able to resolve the server name to the IP address from the client
I even created a computer account in the windows 2003 server of the name engineering.
Still I am not able to join the domain.
Going mad over the same...

The NetSetup.log is also added
07/13 11:27:11 -----------------------------------------------------------------
07/13 11:27:11 NetpDoDomainJoin
07/13 11:27:11 NetpMachineValidToJoin: 'ENGINEERING'
07/13 11:27:11 NetpGetLsaPrimaryDomain: status: 0x0
07/13 11:27:11 NetpMachineValidToJoin: status: 0x0
07/13 11:27:11 NetpJoinDomain
07/13 11:27:11 Machine: ENGINEERING
07/13 11:27:11 Domain: NOCL.COM
07/13 11:27:11 MachineAccountOU: (NULL)
07/13 11:27:11 Account: NOCL.COM\administrator
07/13 11:27:11 Options: 0x27
07/13 11:27:11 OS Version: 5.1
07/13 11:27:11 Build number: 2600
07/13 11:27:11 ServicePack: Service Pack 2
07/13 11:27:11 NetpValidateName: checking to see if 'NOCL.COM' is valid as type 3 name
07/13 11:27:11 NetpCheckDomainNameIsValid [ Exists ] for 'NOCL.COM' returned 0x0
07/13 11:27:11 NetpValidateName: name 'NOCL.COM' is valid for type 3
07/13 11:27:11 NetpDsGetDcName: trying to find DC in domain 'NOCL.COM', flags: 0x1020
07/13 11:27:11 NetpDsGetDcName: found DC '\\nocl-s1.NOCL.COM' in the specified domain
07/13 11:27:11 NetUseAdd to \\nocl-s1.NOCL.COM\IPC$ returned 51
07/13 11:27:11 NetpJoinDomain: status of connecting to dc '\\nocl-s1.NOCL.COM': 0x33
07/13 11:27:11 NetpDoDomainJoin: status: 0x33
********************************************************
Hope I have given enough input to have a clear image of the problem.
Thanks in advance

 

Even after adding DHCP no luck

Today I added a DHCP on the same server which hosts the DNS and the active directory and made the client to be connected to release and get a new lease from the DHCP.
The same happend fine.
But now when I
"ping -a <server ip address> "
I get a differnt name like nag.local
No server of that name excists now, it is a old name I had given during my previous test installation and the server is formatted and the new installation sits on it
but I am able to ping the server.
Even if I give a wrong password during the domain change , what I get is unable to reach the server, what could be problem
The netsetup.log shows that the
"machineaccountOU=NULL "
How do I set the same?
Going mad over the same...

The NetSetup.log is also added
-----------------------------------------------------------------
07/14 14:02:59 NetpDoDomainJoin
07/14 14:02:59 NetpMachineValidToJoin: 'ENGINEERING'
07/14 14:02:59 NetpGetLsaPrimaryDomain: status: 0x0
07/14 14:02:59 NetpMachineValidToJoin: status: 0x0
07/14 14:02:59 NetpJoinDomain
07/14 14:02:59 Machine: ENGINEERING
07/14 14:02:59 Domain: nocl.com
07/14 14:02:59 MachineAccountOU: (NULL)
07/14 14:02:59 Account: nocl.com\administrator
07/14 14:02:59 Options: 0x27
07/14 14:02:59 OS Version: 5.1
07/14 14:02:59 Build number: 2600
07/14 14:02:59 ServicePack: Service Pack 2
07/14 14:02:59 NetpValidateName: checking to see if 'nocl.com' is valid as type 3 name
07/14 14:02:59 NetpCheckDomainNameIsValid [ Exists ] for 'nocl.com' returned 0x0
07/14 14:02:59 NetpValidateName: name 'nocl.com' is valid for type 3
07/14 14:02:59 NetpDsGetDcName: trying to find DC in domain 'nocl.com', flags: 0x1020
07/14 14:02:59 NetpDsGetDcName: found DC '\\nocl-s1.NOCL.COM' in the specified domain
07/14 14:02:59 NetUseAdd to \\nocl-s1.NOCL.COM\IPC$ returned 51
07/14 14:02:59 NetpJoinDomain: status of connecting to dc '\\nocl-s1.NOCL.COM': 0x33
07/14 14:02:59 NetpDoDomainJoin: status: 0x33

********************************************************
Hope I have given enough input to have a clear image of the problem.
Thanks in advance

 

With regard adding the XP PC to the domain ensure the following:
1.) The primary DNS server is specified on the XP machine as the 2003 server.
2.) When adding to the domain specify the domain name by it's netbios name and if that doesn't work try the full DNS name ie domainname and domainname.local
3.) If you are pinging and it's replying with names other than it should be check the following:
Host file on PC c:\windows\system32\drivers\etc\host open up and see if any entries in there for the old name. If there are delete them, you have DNS now.
If not check the DNS server hasn't got any records for the old name. If it has then delete them.

http://www.johnkellett.co.uk - Windows and Citrix Consultant.

 

i had the same problem before..

i changed the preffered DNS server as the Windows 2003 server machine and alternate DNS server as the router's IP...

it worked fine after that

 

never add a external dns to dhcp or tcp-ip properties.

you should only have internal dns, the dns servers will take care of fowarding.