ADMT Migrating Computer Accounts "Duplicate Name"

Hi,

Ive currently installed a new AD Domain by the side of an existing NT4 Domain, i have configured the relevant trusts and tested the authentication.  I have managed to migrate Users & Groups without any problems, but i seem to be incapable of migrating Computer Accounts.

When attempting to Migrate the computer accounts, the actual migration is sucessful, however when the machine boots back up, i receive an error "a duplicate name exists on the network".  I was initially convinced this was something to do with WINS or the Master Browse List, i have removed the old computer account from the old NT4 Domain and still had no luck.  Im fairly sure this is something related to WINS or the MBL but im struggling locating the problem.

Any ideas?

Ta

Paul
LVL 2
buddypearlAsked:
Who is Participating?
 
GranModCommented:
PAQed with points refunded (250)

GranMod
Community Support Moderator
0
 
Walter PadrónCommented:
Hi buddypearl,

See this solution "Windows System Error "duplicate name exists on the network"
http://www.experts-exchange.com/Networking/Microsoft_Network/Q_20988902.html

cheers
0
 
Walter PadrónCommented:
Make the NetBIOS and DNS name of the server the same.
For example, if the DNS name is mypc.company.com, then make the NetBIOS name MYPC as well.

cheers
0
 
buddypearlAuthor Commented:
hi thanks,

The netbios name is the same as the DNS name.

This happens for every computer account i migrate, so far i have failed to find a way round this, no actual duplicate computer exists, this only occurs after i migrate the computer from an NT4 domain to a Windows 2003 Domain using the same WINS server.  If i remove the WINS Server the error does not appear.

I have event log errors stating that it was refused registration by the WINS server, presumably because its a duplicate. yet it isnt.

Ta

Paul
0
 
buddypearlAuthor Commented:
Hi can this be closed pls....

Although i have not figured out the problem i have a resolution.

Considering WINS is a glorifed version of NETBIOS, and we are currently on a FLAT network, there actually isnt any need for WINS.  Removing WINS will remove the ability to add Static WINS entries, however they will be duplicated in our DNS config, the other disadvantage is increased Network Traffic due to the NETBIOS Broadcasts, however this is acceptable for us during the migration.

So the plan is, to remvoe WINS from the DHCP Lease, and have the clients use NETBIOS for resolving the old NT4 Domain, and push out DNS Settings for the new AD DNS Server.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.