moving dhcp server

Hi, planning to move our dhcp server which is an old 2003 server domain controller to a new 2012 server.  I installed the dhcp role on 2012 server but for some reason when i went to configure the server settings for it, the ip address comes up as 169.x.x.x which i assume is the autoconfigured address not the correct internal network ip address which should be 10.10.1.x.  Any ideas?  thanks
dankyle67Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
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.

Don ThomsonCommented:
Couple of questions:

1. Did you isolate the new 2012 server from the mail network and try a single machine to see if it gave you an IP?

2. Is the DHCP Service itself running?
dankyle67Author Commented:
I guess you meant main network correct?  The 2012 server has been running and integrated into the domain as a domain controller for several months now.  I already configured it back then as dns active directory integrated and it has been replicating with the 2003 server without a problem.  I only installed the dhcp role today but have not enabled it yet as i plan on doing this once i temporarily shut down the 2003 server.  There are only 12 pcs in the office so should not be too tricky but what i'm stuck on currently as i mentioned is the fact that the dhcp on the 2012 server is coming up with that 169.x.x.x address instead of the internal 10.x.x.x
Don ThomsonCommented:
You can easily test the DHCP function on the new server by first disabling it on the 2003 server then start it on the new server.  Then release and renew the IP on a test machine that you know can ping the new server.

Disabling the old servers DHCP  will only affect a user that is restarting their machine.

Check ti make sure that you router is also not configured as a DHCP Server.

Also check and make sure that none of the workstations are configured as a static IP.

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
FOXActive Directory/Exchange EngineerCommented:
DK,
If you are planning to make this your dhcp server and drop the 2003 box eventually  it should have a static address anyway.  Give it a static address and retest.  Does the other dhcp server have a static address or is it getting its addresses from the router?
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
Windows Server 2012

From novice to tech pro — start learning today.