"Duplicate Name on the network"

[Guest]

Hi I have a Windows 2003 domain. These few days, I have a "A duplicate name
exists on the network" error when I starts win xp pro. Not only me, but also
all machines on my domain, even servers.
I am sure there is only one machine using this name. I have tested to change
my PC name to another and reboot. After reboot, the same error message
prompts again.
My network is very simple. 2 AD server, one of them is DHCP server. Could
anyone can help.

 

[Guest]

Allen,

Have you set static IP for all your machines in the domain? If so, try
chaning it to dynamic as it is a local network. This should help.

Also, please elaborate on the number of the Computers you use in the network
and the OS installed in them.

Bye!

 

[Guest]

Hi Jason,

I've got some ideas of the problem. (I am new to this company...)

We have a fileserver with the name "COMPANY", and the domain is
"COMPANY.local". I got this in every machines' event log:
"The name "COMPANY :0" could not be registered on the Interface with
IP address 192.168.100.90. The machine with the IP address 192.168.100.238
did not allow the name to be claimed by this machine."

192.168.100.238 is the fileserver that is not on the domain. I guess if I
change the name of fileserver, the problem will fix. But I will need to do
many changes to client machines.

Any simple way to get it fixed?

Thanks.

 

[Guest]

I fixed it. When I disable the WINS service on the fileserver, it stop
prompting the error. I guess it was because the WINS database corupted.
thanks anyway.

 

[Ron Lowe]

Hi Jason,

I've got some ideas of the problem. (I am new to this company...)

We have a fileserver with the name "COMPANY", and the domain is
"COMPANY.local". I got this in every machines' event log:
"The name "COMPANY :0" could not be registered on the Interface with
IP address 192.168.100.90. The machine with the IP address 192.168.100.238
did not allow the name to be claimed by this machine."

192.168.100.238 is the fileserver that is not on the domain. I guess if I
change the name of fileserver, the problem will fix. But I will need to do
many changes to client machines.

Any simple way to get it fixed?

Thanks.

The problem is thet you have a machine name which is the
same as the domain's NetBIOS name.

This is a mis-configuration.

Any client machine trying to register its workgroup name ( the domain's
netbios name, 'COMPANY' ) is being rejected by the wins server as being
taken by the server whose machine name is 'COMPANY'.

The correct fix is to re-name the server to something other than 'COMPANY'.
There is nothing to fix on the clients.

Shutting down the WINS server has only stopped the error messages, not fixed
the problem.

After you fix it, on the clients, you will then see all the names are
correctly registered.
Here's the sample output of 'nbtstat -n' on a client:

C:\Documents and Settings\Ron.HOMENET>nbtstat -n

Local Area Connection:
Node IpAddress: [81.187.191.70] Scope Id: []

NetBIOS Local Name Table

Name Type Status
---------------------------------------------
RONS-PC-2 <00> UNIQUE Registered
HOMENET <00> GROUP Registered <----Check here.
RONS-PC-2 <03> UNIQUE Registered
RONS-PC-2 <20> UNIQUE Registered
HOMENET <1E> GROUP Registered
RON <03> UNIQUE Registered

 

[Guest]

Thank you very much Ron. That's exactly what is happening.
The story is that this Domain and the office is new. The file server is old.
They didn't consider about name conflect before buliding the domain. After
they move in to the new office. Problem's came.
I am new to this office too. At the very first day I worked on the
network...OH! What The He~~
Thanks anyway.

Hi Jason,

I've got some ideas of the problem. (I am new to this company...)

We have a fileserver with the name "COMPANY", and the domain is
"COMPANY.local". I got this in every machines' event log:
"The name "COMPANY :0" could not be registered on the Interface with
IP address 192.168.100.90. The machine with the IP address 192.168.100.238
did not allow the name to be claimed by this machine."

192.168.100.238 is the fileserver that is not on the domain. I guess if I
change the name of fileserver, the problem will fix. But I will need to do
many changes to client machines.

Any simple way to get it fixed?

Thanks.

The problem is thet you have a machine name which is the
same as the domain's NetBIOS name.

This is a mis-configuration.

Any client machine trying to register its workgroup name ( the domain's
netbios name, 'COMPANY' ) is being rejected by the wins server as being
taken by the server whose machine name is 'COMPANY'.

The correct fix is to re-name the server to something other than 'COMPANY'.
There is nothing to fix on the clients.

Shutting down the WINS server has only stopped the error messages, not fixed
the problem.

After you fix it, on the clients, you will then see all the names are
correctly registered.
Here's the sample output of 'nbtstat -n' on a client:

C:\Documents and Settings\Ron.HOMENET>nbtstat -n

Local Area Connection:
Node IpAddress: [81.187.191.70] Scope Id: []

NetBIOS Local Name Table

Name Type Status
---------------------------------------------
RONS-PC-2 <00> UNIQUE Registered
HOMENET <00> GROUP Registered <----Check here.
RONS-PC-2 <03> UNIQUE Registered
RONS-PC-2 <20> UNIQUE Registered
HOMENET <1E> GROUP Registered
RON <03> UNIQUE Registered