IT Employment

Ask something
Discussion Locked

Joining XP to domain

0 helpful
10 replies

by jneag

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

Having a problem in gettting a particular XP system to join a domain. Let me start off by saying that I've joined several systems this way and it's always worked before, so who knows why this is happening.

I'm going through My Computer properties, Computer Name tab, and selecting the Change button. In the member of section I'm selecting Domain and entering the domain name. I've tried several different Computer names, all of which don't produce a different outcome.

When clicking OK I receive the following error titled "Computer Name Changes".

A domain contorller for the domain **** could not be contacted.

Ensure that the domain name is typed correctly.

If the name is correct, click Deatils for troubleshooting information.

Like I said, no matter what name I give this computer, it refuses to join the domain. The system is currently apart of a workgroup with the same name as the domain. I've tried removing it from the workgroup and then joining the domain, but that doesn't work either. I am assigned an IP, as well as can release/renew the IP and can successfully ping the PDC.

Any ideas?

10 replies

by jneag

Also, whenever booting up and the logon screen appears, the following error appears:

Windows - System error
A duplicate name exists on the netowork.

by tsteinman

Is sound like there is another computer on your network that has the same name as the one you are trying to join. Change the name and try joining the network.

by pgdkansas

I fixed this situation by adding the machine name to the domain manually (through ADS on the Domain Controller) and then attempt it again on the client machine. If this doesn't work, ensure that DNS resolution is enabled on the client machine, and try it all again.
Hope this helps.
--Scott

by jneag

There's no ADS on this domain. Forgot to mention that this is an NT4 domain. Can't find settings for DNS resolution.

Let me describe this a little further. I restored a factory image to this computer. Prior to doing this, this computer connected fine. Could this be SSID related?

by pgdkansas

Have you tried removing, and then adding the computer name mannually through Server Mnager on the PDC? (Actually you can use any server(seeing as it is and NT 4.0 Environment)
Yes, It could be SSID issue, however removing the old computer name from Server Manager(even if it is the same computer name) should remove the SSID information after the PDC refreshes itslef.

I'll keep thinking about it.

--Scott

by mrjay67

You said you restored a (factory) image. If this is a ghost image(or the like) you might try running sysprep(if not already). Ive used sysprep with Win2K and it will help reset SIDs among many other helpful options. I havent used it with XP but will work much the same way. Sysprep and its documentation can be found in \support\tools\deploy.cab on the Windows XP CD.

hope this helps

Jason

by jaflynn

Server Manager Is the way to go, but there is more. First off assign the XP machine a static IP address and DNS server, in teh advanced tab, assign it the WINS server, (if available). Then go to the NT Server and in server manager, remove the computer and readd it, manually refreshing it each time. Then go back to xp machine and add it to the domain. Once you have successfully added it to the domain, then you can revert back to using DHCP. For some reason, XP has issues with using DHCP when trying to join a domain. This is really only happens if it was in a domain, then removed and then back again. Don't ask me why but if you do what I said in the order it should get you back into your domain. By the way this also happens if the domain controller is WIN 2K.

by welby

I used this technique (I didn't have to delete the machine name - but I did remove DHCP) and it worked like a charm. This is after 2024 tries to get this computer to join the domain. I know it's over a year old (the post) but thanks for the help!

Welby

by ed

you need to add

192.x.x.x server #pre #dom: domain

# #PRE
# #DOM:
# Following any entry in the file with the characters "#PRE" will cause
# the entry to be preloaded into the name cache. By default, entries are
# not preloaded, but are parsed only after dynamic name resolution fails.
#
# Following an entry with the "#DOM:" tag will associate the
# entry with the domain specified by . This affects how the
# browser and logon services behave in TCP/IP environments. To preload
# the host name associated with #DOM entry, it is necessary to also add a
# #PRE to the line. The is always preloaded although it will not
# be shown when the name cache is viewed

This discussion is closed to new replies.