Friday, April 23, 2010

Windows Server 2008 DHCP Problem "The parameter is incorrect"

I setup a brand new windows server 2008 standard server. Installed all the latest windows updates. Promoted the server to be a domain controller then added the DHCP console. Upon DHCP setup server 2008 automatically authorized the DHCP server in active directory to provide DHCP..

I did not want the server to be authorized until i'm ready to kick it over from my old DHCP server.

When I went to unauthorize the server however I received the error:

The parameter is incorrect.





I checked using netsh to confirm if the server is authorized in Active Directory. "DC1" is the server name, which it is!



I attempted to remove it using netsh but that also failed with the following error:



Believe it or not the fix for this was:
- Stopping DHCP service
- Deleting the DHCP server object from the DHCP console
- Re-add the DHCP server to the DHCP console
- Start the DHCP service
- Try again to unauthorize the DHCP server

This worked - weird problem!
Posted by at
Labels:

14 comments:

  1. AndrewMay 1, 2010 at 3:32 PM

    Clint,

    Many thanks for this post. I was having no end of trouble adding the DHCP role to my new Windows 2008 DC after attemting a DHCP migration from Windows 2003 to Windows 2008. I am not sure why the Server Manager -> Roles option doesn't work but the MMC snapin does. I did use netsh to delete the old scope (from the failed install, had tried dcdiag /fix, ADSI Edit, etc to resolve this) Now my DHCP server is doing it's job.

    ReplyDelete
  2. AnonymousJuly 31, 2010 at 8:47 AM

    thanks for such nice post
    regards
    Anuj

    http://www.winservers.co.in/

    ReplyDelete
  3. AnonymousSeptember 8, 2010 at 1:31 AM

    It really worked amazing..........

    ReplyDelete
  4. AnonymousOctober 29, 2010 at 5:45 AM

    Odd problem! Thanks this really worked on our DC after having to do a System State restore.

    Many Thanks!

    ReplyDelete
  5. AnonymousNovember 2, 2010 at 9:35 AM

    Same problem here, but your fix didn't work for me. Crazy frustrating! Looks like I'll be better off just rebuilding the server from scratch.

    ReplyDelete
  6. AnonymousNovember 10, 2011 at 4:15 PM

    Thanks
    I had the same problem, and this worked perfectly

    ReplyDelete
  7. AnonymousJuly 31, 2012 at 6:16 AM

    Same here, Win2003 wouldnt de-auth until I did the above routine. Weird indeed.

    ReplyDelete
  8. Clint BoessenJuly 31, 2012 at 6:21 AM

    Thanks guys, glad this post was helpful.

    ReplyDelete
  9. AnonymousSeptember 17, 2012 at 2:50 PM

    Thank you sir. Appreciate it.

    ReplyDelete
  10. AnonymousOctober 24, 2012 at 5:26 AM

    Well Done. Thanks for posting.

    ReplyDelete
  11. AnonymousNovember 3, 2012 at 12:31 PM

    Clint,

    Nice post ... I also had the same issue.
    I was able to resolve it by doing it through "manage authorized servers" (right-click dhcp server) and unauthorize the server in question.

    Regards,
    Raymond Schuiling

    ReplyDelete
  12. AnonymousNovember 6, 2012 at 4:01 PM

    that's what i had to do too

    ReplyDelete
  13. AnonymousJanuary 4, 2013 at 1:25 PM

    I had this same issue - battling to resolve it still after trying the above steps - If I go through the Server Manager - right click Servers and select DHCP Manager it shows IPv4 as functional - use the MMC plugin for DHCP and check managed DHCP Servers - shows that server as functional and authorized - now while the Server Manager -> DHCP Manager is open I also open DHCP Manager pinned from the taskbar - it shows red circle and none functional - If I check from there, it shows that DHCP server as authorized even though its circled out

    Be interested to know if anyone has had this experience tied with the above

    ReplyDelete
  14. AnonymousNovember 14, 2013 at 1:59 PM

    Nice fix.. worked for me!

    ReplyDelete

Subscribe to: Post Comments (Atom)