Discussion Locked

Error joining XP Pc to Windows 2003 Domain

0 helpful
18 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I just finished instaling windows 2003 R2 Ent Server.
Followed with installed DNS and when proceeded to install Active directory during the last step it prompted with DNS error for dynamic updates though nonsecure dynamic updates were enabled.So allowed the wizard to correct the same.
Now I am not able to make a XP pc join to the windows 2003 domin.
I am getting the error either the PC is busy or not reachable.
I am able to ping the server from the XP pc,
I have give the same DNS address in XP pc as in server,
Did dcdiag /fix and it gave no error's to
I am stuck any help
Thanks in advance

18 replies

by 3xp3rt

For give you a precise answer I need more info. Is there DHCP installed? What role have your server? How many servers have your organization? ? And an other think. XP machine?s DNS adress most be the server adress, and not the same adress with the server.

by venkatm76

No there is no DHCP installed.
The DNS is installed on the same server which hosts the active directory.
The server has a Static IP address.
I have given the XP machine the DNS Server IP address(which is same as the active directory server)
This is a test environment and has no role.
Hope the same makes sense

by blue screen

What is your ip address on the client pc?

Configure DHCP then authorize DHCP , something like start address (if your server is 192.168.0.1 then start your address at 192.168.0.2 through 192.168.0.100, right click scope options select router on the server name type in your server then click resolve should give you your server ip address, and one more scope option right click select dns then on the server name type your server name click resolve should give your server ip address, then close DHCP now check your client pc ip address if you see something like 169.x.x.x you should renew to get your ip address from your DHCP scope if you get a valid ip address then join the domain and should work.

by venkatm76

The Client XP PC also has a Static IP address.
Still now I am not able to connect the Xp pc to the Domain, When I try, it asks for the username/Password, I give the admin details, still it gives error's ;(

by cg it

when you run the Network Identification wizard and enter a user name and password, what is the error you get? note: default install user name for the administrators account is "administrator" and whatever password you created during the server installation.

Note: If you have to enter a user name and password then your at the least connecting to the server or you would get a network not found error.

by venkatm76

The client is XP Professional with service pack 2.
It is able to detect the domain as when I give the option to join the domain, when i give a wrong domain or user/password the error is domain does not excist or password incorrect respectively.
Here what I get is unable to join the domain.
I am using the server admin user-id and password only for joining to the domain
I am going crazy over the same.

by venkatm76

More Input
**********
When I try to join the XP pc to domain
"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

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

by blackcurrant

Hi again

Have you tried completely removing the XP machine from the domain? Join it to 'Workgroup', reboot, then follow the instructions I gave in the other question on how to join the machine to the new domain using the FQDN of the PC.

Also, if you are still getting references to the old domain in your DNS server, you need to make sure that none of your other workstations contain references (i.e. are still members), of the old domain. If any machines are still members, they will 'pollute' the DNS server. You should also open the DNS snap-in in Active Directory and make sure that there are no records of the old domain name existing (assuming the domain name you quote is no longer used). Remove them if there are.

As I said, this caused us a lot of problems (because I know very little about DNS).

Check your DNS event logs on the server and search for errors. Make sure that the SOA record exists. If it doesn't, then most of what you need to do can be achieved through right-clicking in the DNS consol.

Good luck

by venkatm76

HI
As per your suggestion I went through the link and went about by giving the domain suffic in the pc when it is in workgroup and then tried connecting the same to domin, still the same failed
Next 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 "
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?

more over you had commented that the PC account name should be
eg:-
here :ENGINEERING
have to be
ENGINEERING.NOCL.COM

How do i rename the pc name as "." is not allowed
even I am not able to make a similar account
Do please help

I am adding the netsetup.log for the current date
*************************************************
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

by cg it

ought to take a step back here. You don't need DHCP running to join a comp to a domain. It makes assigning IP addresses easier and providing workstations with resource IPs like DNS and routers but its not necessary.

if you can ping the DC then you've got connectivity to it [and this is with either DHCP enabled and authorized or a static scheme.

So, the problem is joining the domain and credentials to join.

if you open the control panel on the XP machine, and click on the system Icon, that opens up the system properties. click on the computer name tab. on the computer name properties sheet, you can either use the network Identification wizard OR use the change button to manually join the domain. If you use a non FQDN for your LAN, you must use that name to join NOT the FQDN. e.g. if you use a .local extension for your local network. you must provide administrative credentials or an account that has rights to join computers to the domain if that right has been delegated.

If all these attempts fail, you might try to add the compute to the computer OU in Active Directory Users and Computers. Sometimes if there is no computer listed in AD Computers OU for the computer to join, then AD will not allow the computer to join the domain. I've had that happen.

by cg it

I would first check your desktop IP using the ipconfig/all command. if you have an address from DHCP then it should show up and also DNS.

next I would ping the DC. If you can ping then you have connectivity to the DC.

I would run the Network Identification Wizard and try to join the domain that way [making sure that I'm using the correct domain name e.g using the .local extention if it's used on the LAN. If that doesn't work, I would try the change name method of joining the domain. If that doesn't work. Add the computer to the Active Directory USers and Computers computer OU. Then rerun the Network Identificaiton wizard and if that fails , the change name method of joining.

If all that fails, I would try changing the workgroup the XP machine belongs to. EG join a new workgroup reboot, then run the Network Identification Wizard and/or change name method of joining the domain.

If all that fails, then the problem is far more serious. AD is not recognizing the credentials to join the domain or the computer SID is not being processed correctly.

I would look up on Microsoft Help and Support site under W2003 server or XP for help on failed to join domain. There are many KB articles on problems seen in trying to join the domain.

by cg it

you might want to think about starting from scratch again with the W2003 server and use the wizards to configure it as a DC and with Active Directory.

by apaiss

Try to disable the 2003 firewall.
If it helps, enable netbios throgh the firewall.

by venkatm76

No luck so far did all I could
Now I am doing a reinstallation, will come back once it's through or if fails

by venkatm76

Good Morning
I completed the reinstallation of Active Directory,DNS,DHCP........
I even changed the domain to myname "venkat.com"

I changed the workgroup of the XP professional to a new work-group
added a Computer in the active directory users/computers option

I gave DHCp to the XP pc, got itself assigned the IP address
When I give nslookup , it is great and fine, it is showing proper server name
when I give
nslookup 192.168.1.20(which is the server that houses the DNS/Active Directory)

I am able to ping the server
But When I give
ping -a 192.168.1.20
I am getting a different name, don't know why?

NOw When I try connecting the PC I am getting the error as Previously said
Unable to reach the domain controller.
I am going mad, Why is it not reachable.

Any idea's
please help

by edmille3

When moving a machine from the domain to a workgroup or back again the GUID is unknown.
Thus being unable to manage the PC remotely.
How do you retrieve the proper GUID?.

But to join the domain try creating a bounce account. Rename the PC to "bounce" and join the domain. It will find the "Bounce" PC name already exists and then default to the original PC's name.

Make the "bounce" just plain vanillia: domain computer.

This discussion is closed to new replies.