Windows 2003 Server and Netbios Name Conflict

Hello,
I have an existing windows 2000 domain with two servers. The domain name is company.com. 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 company.com. 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 company.com on the same lan segment as the existing win2k servers that are in the company.com domain?
LVL 1
tadduciAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jay_Jay70Commented:
name your server differently mate. you cant have two machines with the same name. Rename it when your done
0
tadduciAuthor Commented:
Hello,
Not that easy buddy... I do have the servers all named differently. The question is that I have an existing Microsoft domain created called company.com 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 company.com and it wants me to make it company0.com.

Computer names are all different.
0
Jay_Jay70Commented:
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
http://www.damaged-existence.com/internet/ActiveDirectoryProcedures/ReplaceDomainController/tabid/54/Default.aspx

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

James
0
tadduciAuthor Commented:
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.

0
Jay_Jay70Commented:
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
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Internet Protocols

From novice to tech pro — start learning today.