Added 2012 r2 domain controller to 2003 domain DNS/DHCP problems?

I added a 2012 R2 domain controller to our existing 2003 domain. We only had one domain controller. We have two now. I did check the DNS server and Global Catalog during install of the new DC. Everything seem to go ok until I was setting up new laptops. These laptops will not be part of our domain but I usually connect them to our wifi. I can connect them to the wifi but I get limited connectivity. An ipconfig reveals 169.254 address. I never had a problem in the past setting up laptops this way. The only thing that changed was we added new Domian Controller. Did I miss something setting up the new DC? All existing machine operate fine.
ibewlocal98Asked:
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.

Walter CurtisSharePoint AEDCommented:
The IP address range indicates that the laptops are unable to contact your DHCP service. It is  hard to troubleshoot without knowing more about your network topology. You probably did not miss anything setting up the new DC since that is separate from DHCP, however the DHCP service might have stopped for some reason during the install process, if it was running on one of your servers and not on your Wi-Fi router.

Hope that helps...

http://packetlife.net/blog/2008/sep/24/169-254-0-0-addresses-explained/
ibewlocal98Author Commented:
We are a small business so our DHCP services runs on our 2003 Domain Controller and the DHCP service is started.
Walter CurtisSharePoint AEDCommented:
Then it is a connectivity issue. The message limited connectivity is what windows throws up. It sees the 169.254 and thinks it has an ip, but then it realizes it can't connect to the network and says limited connectivity.
Protecting & Securing Your Critical Data

Considering 93 percent of companies file for bankruptcy within 12 months of a disaster that blocked access to their data for 10 days or more, planning for the worst is just smart business. Learn how Acronis Backup integrates security at every stage

ibewlocal98Author Commented:
All of our other laptops/ desktops connect fine and are operational. It is just the new ones that I try to connect this week.
Walter CurtisSharePoint AEDCommented:
That kinda indicates the new ones are hosed up somehow. Start by making sure networking is working on them correctly. Maybe try connecting one via LAN cable before jumping to Wi-Fi. I know that doesn't test Wi-Fi, but will test networking of the OS.

Have fun!

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
Lee W, MVPTechnology and Business Process AdvisorCommented:
It sounds like you ran out of IPs,  Have you checked your scope to ensure you have enough?  Have you checked your event logs on the server and the workstations?  Have you tried setting the IP manually?  While it's theoretically possible 2012 would cause issues with 2003 (especially now - you DO realize 2003 is outdated and no longer supported, right?  new patches issued for 2012 won't be tested for compatibility with 2003 - meaning that now... next month, next year, or sometime in the future things could stop working and Microsoft won't help or fix it (or even acknowledge if it's a problem with interoperability).
D_VanteCommented:
If you connect them directly to the network can they join the network that way?
ibewlocal98Author Commented:
I do realize that 2003 is no longer supported. I installed the new 2012R2 to eventually replace our old 2003 DC. I just want to make sure everything is working correctly before we decommission the old DC. I will also add another 2012R2 DC.  

We have plenty of IP addresses and I can directly connect them to the network. So it looks like a wireless problem that just happened to coincide with the new DC installation. I reset the Wireless AP's and I can now connect and receive an IP address.
Walter CurtisSharePoint AEDCommented:
Thanks, glad that helped.
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.