• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 310
  • Last Modified:

new XP machine wont connect to 2000 server domain

I have supplied 3 new Xp machines that need to connect to an existing 2000 server domain. I have given them the same computer name as the PC's that I have taken off the network, but whenever I try to connect to the domain using the same user name and password, it says access not allowed.

If just set them up as a workgroup, using teh domain name, they work perfectly, you can access the server etc, you even have the old security rights, so the users only have the access they had before.

Am I missing something, do I need to set up new computer names on the server?

This is urgent.
5 Solutions
The problem you have is because you removed old computers from the domain without first detaching them from the domain. Because you used same names for new computers the domain won't allow you to log on with the same computer names .
You can re-connect your old computers and remove them from the domain (put them in workgroup) and then join your new computers to the domain.
You can also remove (delete) your old computer-accounts in
"Active directory Users and Computers" go to your "domain" then "computers" locate those computernames and delete them.
After that you shouldn't have any problems adding your new computers to the domain.

Hope this helps.
Took the words right out of my mouth.  Miki18's solution is correct.

Agreed, If you do not want to go and put the computers back on the domain (old ones). The easiest thig to do is go into active directory and Delete the computers. If you do nothing in 30 days it will work ;). Also I noticed that you said "using the same user name and password" If these accounts do not have Administrative access you might have a problem - use the administrator account when you add them.
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

I agree with those options too, another option is to reset account.  (right click computer name in active directory and click reset account) What this does is breaks that computer's connection to the domain and then requires it to rejoin the domain.
The easiest way that I find to deal with this is to start from scratch. Delete the computer accounts on the Domain Controller from Active Directory Users and Computers and then log onto the clients as the admin of the local system. Go back to the system properties and under the Computer Name tab make sure they don't log onto the new domain. You may need to restart if it was still your current domain name. After the restart go back through the Network ID Wizard. MAKE SURE YOU ADD THE COMPUTER AS A DOMAIN ADMIN. Use MYDOMAINNAME\MYDOMAINADMIN as your template.

matthewtwynhamAuthor Commented:
Thanks everyone, in the end I used Mikec 200I, which worked a treat.

But thanks all for your prompt responses.

Featured Post

Visualize your virtual and backup environments

Create well-organized and polished visualizations of your virtual and backup environments when planning VMware vSphere, Microsoft Hyper-V or Veeam deployments. It helps you to gain better visibility and valuable business insights.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now