duplicate name exists on network

[Bruce D. Meyer]

We are getting ready to move about a 1,000 users from an NT domain to an
existing and in use AD domain. When we move computers from the NT domain to
the AD domain, they all get the 'A duplicate name exists on network.' error.

Non of these machines have static WINS mappings. I have removed the dynamic
WINS mapping, I have removed them from server manager. I have even powered
the machine down for three days (Easter weekend) and on the first boot
Monday morning, after first configrming the above items, I get this error
message on each and ever computer I boot up.

I have no problem accessing AD shares, and resources, or the Exchange 5.5
mail server on the NT domain.
running nbtstat -n does NOT return a CONFLICT as expected.

I cannot browse anything outside of the AD domain.
net send etc doesn't work, again, I imagine because the netBT isn't
starting.

Any assistance, faqs, tips, hints, are appreciated. Heck, I'll even read the
FINE manual, if someone would be as nice as to point out which one....
Thanks for your consideration.

Bruce D. Meyer


Here are the errors in order from event log:
Event Type: Error
Event Source: NetBT
Event Category: None
Event ID: 4319
Date: 4/5/2005
Time: 11:06:27 AM
User: N/A
Computer: CS3592
Description:
A duplicate name has been detected on the TCP network. The IP address of
the machine that sent the message is in the data. Use nbtstat -n in a
command window to see which name is in the Conflict state.
Data:
0000: 00 00 04 00 01 00 54 00 ......T.
0008: 00 00 00 00 df 10 00 c0 ....ß..À
0010: 01 01 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
0028: 01 00 02 0a ....

Event Type: Warning
Event Source: MRxSmb
Event Category: None
Event ID: 3032
Date: 4/5/2005
Time: 11:06:27 AM
User: N/A
Computer: CS3592
Description:
The redirector was unable to register the domain COLUMBIASC on to transport
NetBT_Tcpip_{3C55F2DF-08D8-4191-B54 for the following reason: . Transport
has been taken offline.
Data:
0000: 00 00 00 00 04 00 4e 00 ......N.
0008: 00 00 00 00 d8 0b 00 80 ....Ø..€
0010: 00 00 00 00 bd 00 00 c0 ....½..À
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........

Event Type: Information
Event Source: Application Popup
Event Category: None
Event ID: 26
Date: 4/5/2005
Time: 11:06:27 AM
User: N/A
Computer: CS3592
Description:
Application popup: Windows - System Error : A duplicate name exists on the
network.

 

[Paul Bergson]

How about the machine name in AD itself?

Open up Active Directory Users and Computers and check for duplicity there.
Do a search from the root of the domain specifying computer and enter a
name.

--

Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Bruce D. Meyer]

Thank-you for your idea.
I found no duplicates in AD Users and Computers. For fun, I went so far as
to remove the computer name and reboot. oddly, before It was even joined
back to the domain (at this point NO computer account exists in the AD
Domain) I still received the error message that a duplicate computer name
exists.

Here are my thoughts:
Next I will remove the computer from (again...) WINS Dynamic mappings on the
NT domain.
The DHCP server is an NT server. So I am thinking every time I get an IP,
WINS picks up the name. We are not running WINS on the AD side.
I will again, make sure it isn't in server mgr on the NT side, and remove it
from AD users and computers.

I will do all this while the machine is powered down. Now, my thought is,
this. I have noticed we have elections occurring on the network. For some
reason I am not completely clear of, workstations are often the default
master browser. I know how to turn this off on the machines, and we have
enough DC's to take over if on dies, or in the NT side, enough BDC's to
handle it if the PDC died, but we haven't disabled the election thing yet.
Getting back on track, I am assuming that the master browser, often a
workstation has cached the workstation information and might be causing
this.

Another thought we will investigate today is, we have an NT server with two
NICS. I am told they both have the same IP address. I don't remember the
term that was used to explain this, but apparently, it is for some type of
increased throughput or something I am not familiar with. (Perhaps like
bonding or something...) I read some articles about machines having dual
nics giving WINS fits, with error messages like what I am seeing. What would
be useful, is a troubleshooting tool, that I could run that will tell me,
WHO is announcing that the computer name is duplicated. Then I could track
the issue down a bit easier.

Thanks for any help.

Bruce D. Meyer

 

[Paul Bergson]

Looking at this again, I didn't notice the event logs. Have you tried
pinging the IP address and the computer name to see if either give you a
response?

--

Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Bruce D. Meyer]

Yes I did. Also, our naming convention gives each computer from the moment
it arrives and receives it's image, until the moment it is scrapped and
thrown into the trash, a unique computer name. We have shiny silver labels
that are affixed to the computer, and that is it's name. That name always
matches the configured computer name. But as you pointed out, it never hurts
to be certain.

If we figure this out, I will post it to the group so all can benefit.

--Bruce Meyer

 

[ptwilliams]

This often happens because of the messenger bit <03>. Are you sure nbtstat
isn't showing anything?

If all is well, this could well be it? The messenger issue occurs when you
logon to multiple machines at once.

 

[Bruce D. Meyer]

Ok, Progress:
Our esteemed network Administrator discovered when joining an XP box to the
domain, that he got TWO messages, with a slightly different context. This
being that it was the DOMAIN NAME that was in conflict, not the computer
name. Slightly different light. We do indeed have the domain name in the NT
domain WINS static mapping. Not a normal thing to do, but we did it to
resolve a name resolution issue between the two domains. So, we are
rethinking that process now. WINS, or not to WINS for the meantime on the AD
domain, and perhaps replication between the two domains of WINS.

Thanks for your great help.

--Bruce D. Meyer