duplicate name error

  • Thread starter Thread starter Burnie
  • Start date Start date
B

Burnie

We have several Windows 2000 Servers that have two nics in
them. One nic is for the primary network. The other nic
is for the "shadow network". We wanted it this way so
when the servers communicate with each other, they would
use this secondary network to do so. The primary network
is 10.1.1.x and the secondary network is 172.16.1.x. We
have a entries for every server that is on the secondary
network in each host file. When we reboot the machine we
get a duplicate name exists on the network error and is
not allowed to join the domain. Does anyone know how to
resolve this issue?
Burnie
 
In
Burnie said:
We have several Windows 2000 Servers that have two nics in
them. One nic is for the primary network. The other nic
is for the "shadow network". We wanted it this way so
when the servers communicate with each other, they would
use this secondary network to do so. The primary network
is 10.1.1.x and the secondary network is 172.16.1.x. We
have a entries for every server that is on the secondary
network in each host file. When we reboot the machine we
get a duplicate name exists on the network error and is
not allowed to join the domain. Does anyone know how to
resolve this issue?
Burnie
Click to expand...

On one of the NICs on each machine, the 'shadow' NIC, disable NetBIOS, MS
Client and F&P Services and the dupe name will go away.

--
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.
 
This is regarding your reply: "On one of the NICs on each
machine, the 'shadow' NIC, disable NetBIOS, MS Client and
F&P Services and the dupe name will go away."

This doesn't work. First of all, I had already tried
these things. Just to make sure they were still set that
way, I checked again. Still getting the duplicate name
message. I have noticed that a lot of people have asked
this same question other places around the net. I have
yet to find anyone that can solve this problem. If anyone
knows, please let us know.
thanks,
Burnie.
 
In
Burnie said:
This is regarding your reply: "On one of the NICs on each
machine, the 'shadow' NIC, disable NetBIOS, MS Client and
F&P Services and the dupe name will go away."

This doesn't work. First of all, I had already tried
these things. Just to make sure they were still set that
way, I checked again. Still getting the duplicate name
message. I have noticed that a lot of people have asked
this same question other places around the net. I have
yet to find anyone that can solve this problem. If anyone
knows, please let us know.
thanks,
Burnie.
Click to expand...

This usually kills the dupe name error. Are you using WINS? Dupe entry in
the WINS database? Is RRAS configured for routing?

--
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.
 
I found several other postings saying what fixed their
problem. Whether it was changing an entry in the
registry, unchecking a box in the network properties, or
changing a setting somewhere. Trust me I tried them all.
Then I saw someone post something about WINS and it got me
thinking. What I did was just take out all static WINS
entries on the machine having the problem and the
duplicate name error is no more. I am still able to
resolve names, so I am happy. I just wanted to let you
know. Thanks. -Burnie
 
In
Burnie said:
I found several other postings saying what fixed their
problem. Whether it was changing an entry in the
registry, unchecking a box in the network properties, or
changing a setting somewhere. Trust me I tried them all.
Then I saw someone post something about WINS and it got me
thinking. What I did was just take out all static WINS
entries on the machine having the problem and the
duplicate name error is no more. I am still able to
resolve names, so I am happy. I just wanted to let you
know. Thanks. -Burnie
Click to expand...

No problem. I don't know if it was my post about WINS or someone elses,
either way, glad it helped resolve the issues!

:-)

--
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.
 
Back
Top