Share via

Authorized DHCP Servers not showing up in Authorized list.

Question

Tuesday, November 26, 2013 8:53 PM

I have used ADSI edit to validate that the correct servers are under: CN=NetServices,CN=Services,CN=Configuration,DC=Domain,DC=com

Currently we are in 2003 R2 mode for the Domain but all of our DC's are Windows 2008R2.

I did find a value for showInAdvancedViewOnly is set to TRUE.

Thank you,

Scott

All replies (6)

Monday, December 2, 2013 5:49 AM ✅Answered

If you still have the ticket open with Microsoft Premier Support for the DHCP migration, I would contact the engineer that helped you explaining what you are seeing so they can resolve it. After all, it is part of the ticket.

Please note, that TechNet forum support is not aligned with Microsoft Premier Support. They are two separate entities.

-

In the meantime, you can try the following, but I would still email/contact the engineer assigned to your ticket for verification, since they are familiar with your infrastructure and servers. (This was quoted from: http://support.iyogi.com/networking/internet/when-netsh-dhcp-show-server-command-is-executed-and-you-are-getting-invalid-dhcp-server-references.html ))

  1. Run the ‘Netsh’ command to verify, if the ‘CN=NetServices’ container contains the references to the invalid DHCP servers.
  2. Check the properties of the DHCPROOT key under CN=Configuration, CN=Services, ‘CN=NetServices’, ‘DC=Domain’, and ‘DC=com’ to verify if there is a ‘DHCPServer’ attribute containing the references for the invalid DHCP servers.
  3. Delete invalid references.
  4. Force replication
  5. After replication is successful, verify by executing the ‘netsh dhcp show server’ command.

-

Ace Fekay
MVP, MCT, MCITP/EA, MCTS Windows 2008/R2 & Exchange 2007, Exchange 2010 EA, MCSE & MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services
Technical Blogs & Videos: http://www.delawarecountycomputerconsulting.com/

This post is provided AS-IS with no warranties or guarantees and confers no rights.

Tuesday, November 26, 2013 9:09 PM

are you able to connect to the DCHP servers by clicking browse and locating them, and are they showing as being authorised and running. 

also do you have rights to connect and manage the dhcp servers. 

can you check the servers are listed when running this command from admin command prompt

Netsh dhcp show server

Regards,

Denis Cooper

MCITP EA - MCT

Help keep the forums tidy, if this has helped please mark it as an answer

My Blog

LinkedIn:

Wednesday, November 27, 2013 1:15 PM

I get: The data is invalid. After running....netsh..dhcp..show server -- on the box itself.

I am an Enterprise Administrator within the domain and migrated these two DHCP servers from Windows 2003 R2 to Windows 2008R2, with the help of your Microsoft Premier Support team.

They are both up and running fine as designed.  I just don't have them show up within the MMC. I have to go connect manually.

I just want to make sure that I have everything setup correctly with AD before I switch Domain Levels and move on to upgrading to Windows 2012 R2.

Saturday, November 30, 2013 7:06 AM

Hi Scott,

Please also try to run the command below:

Netsh dhcp show all

If you want to examine the health of Active Dirtectory, I suggest you run DCDiag command on Domain Controllers. You can post out the errors and warnings in the DCdiag results for us to analyze.

Here are some related links below:

Netsh commands for DHCP

http://technet.microsoft.com/en-us/library/bb490941.aspx

Dcdiag

http://technet.microsoft.com/en-us/library/cc731968.aspx

What does DCDIAG actually… do?

http://blogs.technet.com/b/askds/archive/2011/03/22/what-does-dcdiag-actually-do.aspx

Best Regards,

Amy Wang

Thursday, December 5, 2013 2:38 AM

Hi Scott,

Do you have any progresses on this issue by now?

Please let us know the latest situation, so we could help you solve this issue efficiently.

Best Regards,

Amy Wang

Thursday, December 26, 2013 8:07 PM

I have been working on Upgrading the Domain Functionality this last week. I will start to troubleshoot this again next week.