Solved

DHCP Server MMC Console showing wrong DomainName (2K8 R2)

Posted on 2011-09-16
3
1,276 Views
Last Modified: 2012-08-14
Experts,

I've stumbled upon another strange error.  After promoting a server to a DC (2K8 R2), everything went as smooth as could be expected, until it came time to install the DHCP role onto the unit.

In my environment, I have a SBS domain that has an alternate UPN suffix.

On the server that I just stood up as a DC in this network, AD replication and everything checks fine.  The DHCP console on the other hand, has the alternate UPN suffix listed, instead of the regular domain name.

When I attempt to "add server" to be able to manage it from that same console, I'm given a list of both my authorized DHCP servers (the one with the bad console too), but when I select the server name and add it to the console, nothing actually happens.  The console still just has the alternate UPN name listed.

Clicking on the alternate UPN name just gives a red-background circle with a white line through the middle icon (like a "do not enter" sign)

I can however, manage the DHCP server completely by connecting to it from a remote console with absolutely no problems.

Would anybody happen to know what that's all about?
0
Comment
Question by:usslindstrom
[X]
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
  • 2
3 Comments
 
LVL 11

Accepted Solution

by:
g000se earned 500 total points
ID: 36551556
Hi,

Make sure when you add the DHCP to mmc make sure you do it under a Domain Admin account.
0
 
LVL 11

Assisted Solution

by:g000se
g000se earned 500 total points
ID: 36551561
Also, try running a ipconfig /flushdns
0
 
LVL 5

Author Closing Comment

by:usslindstrom
ID: 36570931
Thanks for the ideas.  Unfortunately, these didn't change the outcome.

- But now, even with the wrong domain (Alternate Principal Name) the MMC at least is functional now.  I'm guessing it was able to replicate something in the background about authorized DHCP servers - so I no longer get an error.

It shows the wrong domain name, but it's managable.  I guess we take what we can get.  :)
0

Featured Post

Industry Leaders: 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

Background Information Recently I have fixed file server permission issues for one of my client. The client has 1800 users and one Windows Server 2008 R2 domain joined file server with 12 TB of data, 250+ shared folders and the folder structure i…
This article shows how to deploy dynamic backgrounds to computers depending on the aspect ratio of display
This tutorial will give a short introduction and overview of Backup Exec 2012 and how to navigate and perform basic functions. Click on the Backup Exec button in the upper left corner. From here, are global settings for the application such as conne…
Are you ready to implement Active Directory best practices without reading 300+ pages? You're in luck. In this webinar hosted by Skyport Systems, you gain insight into Microsoft's latest comprehensive guide, with tips on the best and easiest way…

756 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