Duplicate Name

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Recently when removing/adding computers in our W2K AD we started getting the
error message "You were not connected...Duplicate name exists on the network"
when trying to remotely manage or map drives to computers that have been
removed and added back with the same name. This happens even if it is a
different computer that we renamed to a name that was previously used but was
removed months ago.
E.g...
We remove a computer from the domain locally (Comp23) and then shut it down
or reimage it ...next we remove the computer object (Comp23) from our
Computers OU. Then we setup a new computer...give it the name we just removed
from the network and AD (Comp23). When we try to manage it we get the Dupe
name error....no errors are generated when this new computer with the
recycled name (Comp23) is joined to the domain though.

Whats up?

squib
 
In
Squib said:
Recently when removing/adding computers in our W2K AD we started
getting the error message "You were not connected...Duplicate name
exists on the network" when trying to remotely manage or map drives
to computers that have been removed and added back with the same
name. This happens even if it is a different computer that we renamed
to a name that was previously used but was removed months ago.
E.g...
We remove a computer from the domain locally (Comp23) and then shut
it down or reimage it ...next we remove the computer object (Comp23)
from our Computers OU. Then we setup a new computer...give it the
name we just removed from the network and AD (Comp23). When we try to
manage it we get the Dupe name error....no errors are generated when
this new computer with the recycled name (Comp23) is joined to the
domain though.

Whats up?

squib
Click to expand...

That depends on how you are connecting. If joining by single Netbios name,
and it gives you the error, it's pretty much saying there's a dupe NetBIOS
name out there. If you are using WINS, check the WINS database for the old
reference.

--
Regards,
Ace

Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.

This posting is provided "AS-IS" with no warranties or guarantees
and confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services

Security Is Like An Onion, It Has Layers
HAM AND EGGS: A day's work for a chicken;
A lifetime commitment for a pig.
 
Thanx for the reply...There are no error messages when joining the computer
to the domain using a recycled name...the error "You were not
connected...Duplicate name exists on the network" is generated when trying to
remotely manage or connect to the newly added computer.
We are using WINS so every time a computer is removed from the AD domain we
have to manually remove it from WINS?
Funny that WINS will not release the removed computer even though we would
wait sometimes weeks before reusing a name.

Squib
 
circa Sat, 11 Sep 2004 09:09:01 -0700, in
microsoft.public.win2000.active_directory, =?Utf-8?B?c3F1aWI=?=
([email protected]) said,
We are using WINS so every time a computer is removed from the AD domain we
have to manually remove it from WINS?
Click to expand...

Yes, or make sure that your WINS tombstoning and scavenging is
working properly.
Funny that WINS will not release the removed computer even though we would
wait sometimes weeks before reusing a name.
Click to expand...

This usually indicates misconfiguration of WINS.

Laura
 
Thanx all...will look at WINS....

squib

Laura A. Robinson said:
circa Sat, 11 Sep 2004 09:09:01 -0700, in
microsoft.public.win2000.active_directory, =?Utf-8?B?c3F1aWI=?=
([email protected]) said,

Yes, or make sure that your WINS tombstoning and scavenging is
working properly.


This usually indicates misconfiguration of WINS.

Laura
Click to expand...
 
Laura A. Robinson said:
circa Sat, 11 Sep 2004 09:09:01 -0700, in
microsoft.public.win2000.active_directory, =?Utf-8?B?c3F1aWI=?=
([email protected]) said,

Yes, or make sure that your WINS tombstoning and scavenging is
working properly.


This usually indicates misconfiguration of WINS.

Laura
Click to expand...
 
Back
Top