Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1503
  • Last Modified:

Connecting to DHCP Server

I've inherited a Windows network that has a number of locations with Windows 2003 and Windows 2008 servers.  One of the DCs is running Windows 2008 R2 server is also serving DNS and DHCP.

The DHCP environment was showing several servers that had been decommissioned years ago.  I used the tip in http://blogs.technet.com/b/networking/archive/2009/02/27/old-dhcp-servers-appear-in-the-list-of-authorized-servers-after-a-domain-rename.aspx to remove the obsolete servers.

My issue now is that when I'm connected to this particular Windows 2008 R2 server, I can bring up DHCP, but I can't see the locally defined scope.  I can access this server's scope from other systems, and from that perspective, it appears to be operating normally.  The other unusual thing I've noticed is that when accessed locally, instead of the server's name showing at the top of the list, the name of one of the software apps on this server is displayed.  The icon is a server with a red circle and a horizontal white line, which I find to be defined as "DHCP server connected but current user does not have the administrative credentials to manage the server."
The same username can remotely access that server's DHCP setup without problems.

So the questions are (1) why can't I access DHCP locally and (2) why isn't the server name used?
0
ITHastings
Asked:
ITHastings
  • 5
  • 3
1 Solution
 
eeRootCommented:
Sounds like you may have at least one old or conflicing DHCP server listed under DHCP's authorized server list.  And also, perhaps there are group policies or local policies restricing which accounts can connect to the DHCP server with admin rights.  On the true DHCP server, launch the DHCP console, right click on "DHCP," and check the "Manage Authorized Servers..." list and make sure no old or rouge DHCP servers exist.  Then check your group and local policies for DHCP admin restrictions.
0
 
ITHastingsAuthor Commented:
When I started working in this domain, there were two obsolete DHCP servers listed in the authorized server list.  I used ADSIedit to remove them.  I've not come across any group or local policies that would restrict access to the DHCP server.

The same account that can successfully open the DHCP console on the "bad" server remotely cannot do it locally.  I've granted that account membership in the DHCP Administrators group, but that didn't help.

Any other suggestions would be appreciated.
0
 
eeRootCommented:
Running "GPResult" on both DHCP servers while logged in with the admin account in question may shed some light on what is happening.  If your admin account is being restricted, the report generated by GPResult should show what group policy or local policy is causing it.
0
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

 
ITHastingsAuthor Commented:
The only thing related to DHCP when running GPResult on the two systems is that the id I'm using is a member of the DHCP Administrators group.
0
 
eeRootCommented:
The last thing I can think to check is if the MMC console settings have somehow been changed or corrupted.  If you create a new MMC file (start, run, type MMC) and then add the DHCP snap in, can you specify the DHCP server and access it with admin rights?
0
 
ITHastingsAuthor Commented:
Tried it and get the same result.

I went ahead and reinstalled DHCP on the "obsolete" server and uninstalled DHCP on the new server.  Did a reboot on the new server, went to the \Windows\system32\dhcp folder and removed the files there.  Added the DHCP role back onto the new server.  

Same result.  I can access the new server's DHCP remotely, but not locally.  When I'm local on the new server, I can see DHCP servers in other locations, but I can't see the local scope.
0
 
ITHastingsAuthor Commented:
The problem was caused by the presence of a HOSTS file on the server.  The only definition in the file had a different computer name assigned to the IP address of this server.  When I removed the definition, DHCP began working normally when opened locally.
0
 
ITHastingsAuthor Commented:
No other answer that was submitted worked for this problem.
0
 
Peak-SupportCommented:
Thanks ITHastings. Solved my issue too!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

  • 5
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now