Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17


Windows 2003 Server and Netbios Name Conflict

Posted on 2007-04-10
Medium Priority
Last Modified: 2013-11-25
I have an existing windows 2000 domain with two servers. The domain name is I need to replace the servers and due to the fact I have so little data on them I want to stage my new servers on the same lan and also setup AD via dcpromo and call the domain The new servers will not join the win2k domain as I don't feel like going thru the upgrade process. I just want to start over on the new servers and move the data over manually and recreate the users etc... I need to work on these servers remotely and they share the same subnet for remote access purposes.

Is this possible? When I dcpromo the new win2003 server I get a netbios naming error due to the fact that the existing and in production win2k enviroment has the same netbios name?

How can I setup the new servers in a new forest with on the same lan segment as the existing win2k servers that are in the domain?
Question by:tadduci
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
LVL 48

Expert Comment

ID: 18887759
name your server differently mate. you cant have two machines with the same name. Rename it when your done

Author Comment

ID: 18889115
Not that easy buddy... I do have the servers all named differently. The question is that I have an existing Microsoft domain created called running win2k... Now I want to migrate to a windows 2003 domain but not go thru the upgrade process so I have new hardware and I am looking to setup the 2nd domain along side the 1st domain but when I go to dcpromo the first server of the new ones it tells me there is a netbios name conflict with the name and it wants me to make it

Computer names are all different.
LVL 48

Expert Comment

ID: 18895806
Ahh i see i see, can i suggest a different approach?

you may be able to save yourself some heartache with a migration rather than an upgrade

Thats my guide, let me know if that is an option for you


Author Comment

ID: 18900289
I need to do a new fresh setup for reasons beyond the scope of this article. I need to know the simplest way to maintain internet connectivity to the new servers (win 2003) and have them sit on the same subnet as the old servers (win2k). I realize I cannot permit netbios names to conflict so I am interesting in ideas around this.

Can I make it company0 for the new netbios name and just change it later? Or because it is in a domain it will prevent me from renaming the DC later on.

I thought about a VLAN or putting these machines on a seperate switch but then they would not have internet connectivity and thus no remote access for me.

LVL 48

Accepted Solution

Jay_Jay70 earned 2000 total points
ID: 18902737
hmm the only thing i could think of would be the VLAN situation and just share a gateway, your porblem is the broadcast domain...i simply cant see a way around it - if you want another opinion i can get some more help

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Recently, I had the need to build a standalone system to run a point-of-sale system. I’m running this on a low-voltage Atom processor, so I wanted a light-weight operating system, but still needed Windows. I chose to use Microsoft Windows Server 200…
Preface There are many applications where some computing systems need have their system clocks running synchronized within a small margin and eventually need to be in sync with the global time. There are different solutions for this, i.e. the W3…
Monitoring a network: how to monitor network services and why? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the philosophy behind service monitoring and why a handshake validation is critical in network monitoring. Software utilized …
In this video, Percona Solution Engineer Dimitri Vanoverbeke discusses why you want to use at least three nodes in a database cluster. To discuss how Percona Consulting can help with your design and architecture needs for your database and infras…

670 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question