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

Two names associated to one computer

I had to switch two of our user's computers and rename them on the network. Our network uses a domain.
So heres the problem,
Now one of the computers has two names associated to it (lets call them A and B, B is the name for the other computer). I can't get it to unassociate B from that computer so I can use it for the other computer.
I probably haven't explained it quite well as it stands but a round or two of question and answer should clear it up. Thanks!
  • 3
2 Solutions
That is very confusing. If you are renaming computer A to computer B you will first have to rename computer B and then delete the old computer account from Active Directory. After that is done you can rename computer A to the old name of computer B.
strungout132Author Commented:
Ahh ok, thats what i was thinking.
It's weird though, if I ping computer A, i can use both A and B's name for the same computer. Would deleting the computer from AD solve it?
strungout132Author Commented:
Forgot to add, computer B currently has another name as i couldnt name it what it was supposed to be.
Please correct me.

In my understanding the name is refering to NETBIOS NAME right?

You cannot join computer on a domain with the same name.

Try to remove the two computer on the windows domain and then join again.

Can you post computer A and B's Fully Qualified Domain Name?

I hope this helps

strungout132Author Commented:
Alright, i removed computer A from the domain and active directory. Then I rejoined the domain and named computer A accordingly. Then computer B accepted the new name flawlessly.
The pinging issue i was having was solved by "ipconfig /flushdns" and "nbtstat -RR".

Featured Post

 The Evil-ution of Network Security Threats

What are the hacks that forever changed the security industry? To answer that question, we created an exciting new eBook that takes you on a trip through hacking history. It explores the top hacks from the 80s to 2010s, why they mattered, and how the security industry responded.

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