Windows 2008 DHCP service fails - “…failed to see a directory server for authorization.”What should the...

Are objects structures and/or vice versa?

What do the Banks children have against barley water?

New order #4: World

aging parents with no investments

Is this food a bread or a loaf?

Does bootstrapped regression allow for inference?

Prime joint compound before latex paint?

How to deal with fear of taking dependencies

Where to refill my bottle in India?

Does a dangling wire really electrocute me if I'm standing in water?

Shall I use personal or official e-mail account when registering to external websites for work purpose?

Why did the Germans forbid the possession of pet pigeons in Rostov-on-Don in 1941?

Why was the "bread communication" in the arena of Catching Fire left out in the movie?

LWC and complex parameters

A poker game description that does not feel gimmicky

Is domain driven design an anti-SQL pattern?

Does it makes sense to buy a new cycle to learn riding?

Can a planet have a different gravitational pull depending on its location in orbit around its sun?

Is there a way to make member function NOT callable from constructor?

What does it exactly mean if a random variable follows a distribution

I’m planning on buying a laser printer but concerned about the life cycle of toner in the machine

Where else does the Shulchan Aruch quote an authority by name?

Does the average primeness of natural numbers tend to zero?

Denied boarding due to overcrowding, Sparpreis ticket. What are my rights?



Windows 2008 DHCP service fails - “…failed to see a directory server for authorization.”


What should the order of DNS servers be for an AD Domain Controller and Why?Windows Cannot View Domain Location“ipv6 equivalent” of 192.168.x.x (configuring a static ipv6 address)How do I connect a 2008 server to a 2003 server active directory?Can I authorize W2K8 DHCP server for private network, even when prohibited in enterprise network?Domain controller offline over 2 months, now can't syncCannot find the DHCP ServerConfiguring VPN on Windows Server 2008 with no DHCPNotification of low DHCP pool in split scope setupMail Server Fails to Replicate Active Directory UsersWindows Server 2012 R2 - Help finding failed logon attempts source






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







14















I have a small environment running Windows 2008 R2 where the DHCP service on the domain controller fails every two weeks.



enter image description here



The most-visible error is Event ID 1059 and the Event Viewer message is:



"The DHCP service failed to see a directory server for authorization."



enter image description here



The setup features two domain controller and the usual services and roles (file, print, Exchange). Restarting the service fails for a variety of reasons. I've had the following messages at different times:




  • "Not enough storage is available to complete this operation".

  • "Unable to determine the DHCP Server version for the Server 192.168.x.x"

  • "The DHCP service has detected that it is running on a DC and has no credentials configured for use with Dynamic DNS registrations initiated by the DHCP service."


A reboot of the domain controller resolves the issue for ~2 weeks. The systems are virtualized and there are no network connectivity issues.



Any ideas as to what's happening here?



Edit - The solution seems to be to fix a misbehaving domain controller.










share|improve this question

























  • I understand that it might sound a little silly, but have you tried this: technet.microsoft.com/en-us/library/cc774849%28v=ws.10%29.aspx

    – George
    May 21 '12 at 14:50











  • No network connectivity issues. These are VMs.

    – ewwhite
    May 21 '12 at 15:16






  • 1





    Wait, shouldn't at least one of the DCs be a physical server?

    – George
    May 21 '12 at 15:23






  • 5





    Since both DC's are VMs - are you getting time skew perhaps? VMs are prone to this and could cause some of the issues you're seeing. Are you syncing the time with the hypervisor?

    – colealtdelete
    May 21 '12 at 20:29






  • 2





    @Bigbio2002 that's wrong, see this. Though that probably doesn't have any bearing on this specific problem it's a common mistake to list the loopback address first on a DC.

    – MDMarra
    Jun 2 '12 at 21:27


















14















I have a small environment running Windows 2008 R2 where the DHCP service on the domain controller fails every two weeks.



enter image description here



The most-visible error is Event ID 1059 and the Event Viewer message is:



"The DHCP service failed to see a directory server for authorization."



enter image description here



The setup features two domain controller and the usual services and roles (file, print, Exchange). Restarting the service fails for a variety of reasons. I've had the following messages at different times:




  • "Not enough storage is available to complete this operation".

  • "Unable to determine the DHCP Server version for the Server 192.168.x.x"

  • "The DHCP service has detected that it is running on a DC and has no credentials configured for use with Dynamic DNS registrations initiated by the DHCP service."


A reboot of the domain controller resolves the issue for ~2 weeks. The systems are virtualized and there are no network connectivity issues.



Any ideas as to what's happening here?



Edit - The solution seems to be to fix a misbehaving domain controller.










share|improve this question

























  • I understand that it might sound a little silly, but have you tried this: technet.microsoft.com/en-us/library/cc774849%28v=ws.10%29.aspx

    – George
    May 21 '12 at 14:50











  • No network connectivity issues. These are VMs.

    – ewwhite
    May 21 '12 at 15:16






  • 1





    Wait, shouldn't at least one of the DCs be a physical server?

    – George
    May 21 '12 at 15:23






  • 5





    Since both DC's are VMs - are you getting time skew perhaps? VMs are prone to this and could cause some of the issues you're seeing. Are you syncing the time with the hypervisor?

    – colealtdelete
    May 21 '12 at 20:29






  • 2





    @Bigbio2002 that's wrong, see this. Though that probably doesn't have any bearing on this specific problem it's a common mistake to list the loopback address first on a DC.

    – MDMarra
    Jun 2 '12 at 21:27














14












14








14


3






I have a small environment running Windows 2008 R2 where the DHCP service on the domain controller fails every two weeks.



enter image description here



The most-visible error is Event ID 1059 and the Event Viewer message is:



"The DHCP service failed to see a directory server for authorization."



enter image description here



The setup features two domain controller and the usual services and roles (file, print, Exchange). Restarting the service fails for a variety of reasons. I've had the following messages at different times:




  • "Not enough storage is available to complete this operation".

  • "Unable to determine the DHCP Server version for the Server 192.168.x.x"

  • "The DHCP service has detected that it is running on a DC and has no credentials configured for use with Dynamic DNS registrations initiated by the DHCP service."


A reboot of the domain controller resolves the issue for ~2 weeks. The systems are virtualized and there are no network connectivity issues.



Any ideas as to what's happening here?



Edit - The solution seems to be to fix a misbehaving domain controller.










share|improve this question
















I have a small environment running Windows 2008 R2 where the DHCP service on the domain controller fails every two weeks.



enter image description here



The most-visible error is Event ID 1059 and the Event Viewer message is:



"The DHCP service failed to see a directory server for authorization."



enter image description here



The setup features two domain controller and the usual services and roles (file, print, Exchange). Restarting the service fails for a variety of reasons. I've had the following messages at different times:




  • "Not enough storage is available to complete this operation".

  • "Unable to determine the DHCP Server version for the Server 192.168.x.x"

  • "The DHCP service has detected that it is running on a DC and has no credentials configured for use with Dynamic DNS registrations initiated by the DHCP service."


A reboot of the domain controller resolves the issue for ~2 weeks. The systems are virtualized and there are no network connectivity issues.



Any ideas as to what's happening here?



Edit - The solution seems to be to fix a misbehaving domain controller.







windows-server-2008 active-directory dhcp-server






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jul 15 '13 at 22:40







ewwhite

















asked May 21 '12 at 13:43









ewwhiteewwhite

174k78370725




174k78370725













  • I understand that it might sound a little silly, but have you tried this: technet.microsoft.com/en-us/library/cc774849%28v=ws.10%29.aspx

    – George
    May 21 '12 at 14:50











  • No network connectivity issues. These are VMs.

    – ewwhite
    May 21 '12 at 15:16






  • 1





    Wait, shouldn't at least one of the DCs be a physical server?

    – George
    May 21 '12 at 15:23






  • 5





    Since both DC's are VMs - are you getting time skew perhaps? VMs are prone to this and could cause some of the issues you're seeing. Are you syncing the time with the hypervisor?

    – colealtdelete
    May 21 '12 at 20:29






  • 2





    @Bigbio2002 that's wrong, see this. Though that probably doesn't have any bearing on this specific problem it's a common mistake to list the loopback address first on a DC.

    – MDMarra
    Jun 2 '12 at 21:27



















  • I understand that it might sound a little silly, but have you tried this: technet.microsoft.com/en-us/library/cc774849%28v=ws.10%29.aspx

    – George
    May 21 '12 at 14:50











  • No network connectivity issues. These are VMs.

    – ewwhite
    May 21 '12 at 15:16






  • 1





    Wait, shouldn't at least one of the DCs be a physical server?

    – George
    May 21 '12 at 15:23






  • 5





    Since both DC's are VMs - are you getting time skew perhaps? VMs are prone to this and could cause some of the issues you're seeing. Are you syncing the time with the hypervisor?

    – colealtdelete
    May 21 '12 at 20:29






  • 2





    @Bigbio2002 that's wrong, see this. Though that probably doesn't have any bearing on this specific problem it's a common mistake to list the loopback address first on a DC.

    – MDMarra
    Jun 2 '12 at 21:27

















I understand that it might sound a little silly, but have you tried this: technet.microsoft.com/en-us/library/cc774849%28v=ws.10%29.aspx

– George
May 21 '12 at 14:50





I understand that it might sound a little silly, but have you tried this: technet.microsoft.com/en-us/library/cc774849%28v=ws.10%29.aspx

– George
May 21 '12 at 14:50













No network connectivity issues. These are VMs.

– ewwhite
May 21 '12 at 15:16





No network connectivity issues. These are VMs.

– ewwhite
May 21 '12 at 15:16




1




1





Wait, shouldn't at least one of the DCs be a physical server?

– George
May 21 '12 at 15:23





Wait, shouldn't at least one of the DCs be a physical server?

– George
May 21 '12 at 15:23




5




5





Since both DC's are VMs - are you getting time skew perhaps? VMs are prone to this and could cause some of the issues you're seeing. Are you syncing the time with the hypervisor?

– colealtdelete
May 21 '12 at 20:29





Since both DC's are VMs - are you getting time skew perhaps? VMs are prone to this and could cause some of the issues you're seeing. Are you syncing the time with the hypervisor?

– colealtdelete
May 21 '12 at 20:29




2




2





@Bigbio2002 that's wrong, see this. Though that probably doesn't have any bearing on this specific problem it's a common mistake to list the loopback address first on a DC.

– MDMarra
Jun 2 '12 at 21:27





@Bigbio2002 that's wrong, see this. Though that probably doesn't have any bearing on this specific problem it's a common mistake to list the loopback address first on a DC.

– MDMarra
Jun 2 '12 at 21:27










10 Answers
10






active

oldest

votes


















3














Since I've had the privilege of actually working in this specific environment, I can say with certainty that the DC that is hosting DHCP fails replication and goes unresponsive to requests for various Directory Services functions (like authorizing DHCP servers) every few weeks. This DHCP issue is a symptom of the larger replication problem.



Since the server that DHCP is on is a DC, it only ever looks to itself for authorization. When Directory Services stops functioning on it, so does DHCP.






share|improve this answer





















  • 1





    Okay. Now fix it!!!

    – ewwhite
    Jul 15 '13 at 22:38



















3














This part really jumps out at me:




  • "Not enough storage is available to complete this operation".


I'm assuming that you actually do have disk space available on the server. This points to the possibility of data or disk corruption. Have you run a chkdsk? Do the credentials the DHCP service runs under have permissions to the log directory and to the directory where the DHCP db is stored?



Ruling out those possibilities, next step is to check that there are no invalid entries in DNS for your domain, especially if there was a DC that was removed from the domain at some point. First do a nslookup on the FQDN of your domain, check to make sure there are no invalid IP addresses returned (I've seen sometimes a 2nd unused NIC on a DC with 169.254.x.x address register itself in DNS as a valid NS/DC). Next on the DNS server check SRV entries for LDAP and KRB, make sure they are all valid.






share|improve this answer



















  • 1





    Not a bad answer, but the out of space error is much more likely about memory or item number/database limits. By the time you have so little disk space, your DHCP service is failing, you'll have noticed other, bigger problems.

    – HopelessN00b
    Oct 7 '12 at 18:48











  • Microsoft is notoriously bad about throwing this kind of error as an "if all else fails" error. Also, "storage space" refers to a specific "flavor" of memory to be allocated rather than disk space very frequently with this error.

    – Evan Anderson
    Jul 15 '13 at 16:16



















0














The issues seems that you are not an enterprise administrator of your the tree in your forest. Do you have any other DHCP's in your domain? Because if you do, try to de-authorize it and see if you can, if you can't then you don't have access which proves the point of not being an enterprise administrator. Please also take a look at this article:



http://technet.microsoft.com/en-us/library/cc775255(v=ws.10).aspx






share|improve this answer
























  • We have the same issues and being an Enterprise Administrator doesn't solve it. We tried looking but couldn't find a document that describes what exactly associates the DHCP and AD services.

    – nearora
    May 31 '12 at 3:40











  • @nearora how often does this occur in your environment?

    – ewwhite
    Jun 5 '12 at 14:23











  • @ewwhite, it is permanent. Even a reboot hasn't fixed it for us from what I recall. We've only tried it with a R&D setup with stock standard MS Windows Server 2008 R2. If you need any information for debugging, I could get it, but might take a while as I need to hassle a colleague to let me use their setup.

    – nearora
    Jun 5 '12 at 22:09



















0














Maybe there is a rogue dhcp server (Check with nmap)? Also, check http://support.microsoft.com/kb/938456 describing conflicting records in AD.






share|improve this answer
























  • Not seeing any rogue dhcp servers on the network.

    – ewwhite
    Jun 5 '12 at 14:22



















0














maybe you run into a bug.
http://support.microsoft.com/kb/2632816/en-gb






share|improve this answer































    0














    Just a few articles to look at...some may not seem to apply, but look carefully and consider the causes in each article:



    http://support.microsoft.com/kb/935744



    http://blogs.technet.com/b/abizerh/archive/2009/07/12/troubleshooting-the-error-not-enough-storage-is-available-to-complete-this-operation.aspx



    http://forums.whirlpool.net.au/archive/1533833






    share|improve this answer































      0














      I would check for AD replication issues.



      http://www.microsoft.com/en-us/download/details.aspx?id=30005






      share|improve this answer































        0














        Couple of questions for you...
        Can you try running a DCDiag on both DCs and posting any errors? Are there any other errors in the event logs? If there's no errors now try running it again on both dcs when the service has failed before rebooting the server.



        Have you tried simply reinstalling DHCP on the trouble server?






        share|improve this answer
























        • DCDiag fails on the affected server when this happens. Again, it's once every few weeks, so I need to catch it in progress again before I can troubleshoot more.

          – ewwhite
          Aug 15 '12 at 20:22











        • No problem, those issues are always the hardest to track down.

          – Jason
          Aug 15 '12 at 20:30



















        0














        So, two virtual Domain Controllers... are both DHCP servers? It sounds like only one is. In which case I'd be tempted to run for a few weeks with the DHCP server only using the other domain controller as DNS. And then for a few weeks with the other domain controller shut down.



        You can always revert the change if it impacts on users but it might help narrow down which box (if it is only one) is causing the issue.



        I'd also be tempted to add a third DC and then decommission the second one to rule out it being some weird installation corruption of the type Windows loves to flump into.



        Have you tried restarting services on the DC rather than rebooting it?



        Do the DCs host other services (file, exchange, etc)? Since you've got a virtualised environment do you have headroom to move those services onto their own servers for a few weeks to rule out confusion from those roles clashing?



        Additionally, and since it hasn't been commented on, with respect to the "Not enough storage is available to complete this operation" error. If the server's disks are full then all of its DC functions are going to start to fail. Are the disks full?






        share|improve this answer































          0














          To resolve the issue, kindly remove the Server Bindings (Remember we have to have a Static IP address for the DHCP Server to do this).



          Steps:




          • Click Start, point to Programs, point to Administrative Tools, and then click DHCP.

          • Right click the name of the original DHCP server name.

          • Click on Add/Remove Bindings.

          • In Server Binding Properties, Uncheck the box for the Local Area Connection and click on OK.

          • Restart the DHCP Service if required.






          share|improve this answer


























          • There was no option to remove bindings. It was grayed-out in my case.

            – ewwhite
            Feb 25 '13 at 16:28












          protected by Community 1 hour ago



          Thank you for your interest in this question.
          Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



          Would you like to answer one of these unanswered questions instead?














          10 Answers
          10






          active

          oldest

          votes








          10 Answers
          10






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          3














          Since I've had the privilege of actually working in this specific environment, I can say with certainty that the DC that is hosting DHCP fails replication and goes unresponsive to requests for various Directory Services functions (like authorizing DHCP servers) every few weeks. This DHCP issue is a symptom of the larger replication problem.



          Since the server that DHCP is on is a DC, it only ever looks to itself for authorization. When Directory Services stops functioning on it, so does DHCP.






          share|improve this answer





















          • 1





            Okay. Now fix it!!!

            – ewwhite
            Jul 15 '13 at 22:38
















          3














          Since I've had the privilege of actually working in this specific environment, I can say with certainty that the DC that is hosting DHCP fails replication and goes unresponsive to requests for various Directory Services functions (like authorizing DHCP servers) every few weeks. This DHCP issue is a symptom of the larger replication problem.



          Since the server that DHCP is on is a DC, it only ever looks to itself for authorization. When Directory Services stops functioning on it, so does DHCP.






          share|improve this answer





















          • 1





            Okay. Now fix it!!!

            – ewwhite
            Jul 15 '13 at 22:38














          3












          3








          3







          Since I've had the privilege of actually working in this specific environment, I can say with certainty that the DC that is hosting DHCP fails replication and goes unresponsive to requests for various Directory Services functions (like authorizing DHCP servers) every few weeks. This DHCP issue is a symptom of the larger replication problem.



          Since the server that DHCP is on is a DC, it only ever looks to itself for authorization. When Directory Services stops functioning on it, so does DHCP.






          share|improve this answer















          Since I've had the privilege of actually working in this specific environment, I can say with certainty that the DC that is hosting DHCP fails replication and goes unresponsive to requests for various Directory Services functions (like authorizing DHCP servers) every few weeks. This DHCP issue is a symptom of the larger replication problem.



          Since the server that DHCP is on is a DC, it only ever looks to itself for authorization. When Directory Services stops functioning on it, so does DHCP.







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Jul 15 '13 at 17:04

























          answered Jul 15 '13 at 15:37









          MDMarraMDMarra

          92.9k28174314




          92.9k28174314








          • 1





            Okay. Now fix it!!!

            – ewwhite
            Jul 15 '13 at 22:38














          • 1





            Okay. Now fix it!!!

            – ewwhite
            Jul 15 '13 at 22:38








          1




          1





          Okay. Now fix it!!!

          – ewwhite
          Jul 15 '13 at 22:38





          Okay. Now fix it!!!

          – ewwhite
          Jul 15 '13 at 22:38













          3














          This part really jumps out at me:




          • "Not enough storage is available to complete this operation".


          I'm assuming that you actually do have disk space available on the server. This points to the possibility of data or disk corruption. Have you run a chkdsk? Do the credentials the DHCP service runs under have permissions to the log directory and to the directory where the DHCP db is stored?



          Ruling out those possibilities, next step is to check that there are no invalid entries in DNS for your domain, especially if there was a DC that was removed from the domain at some point. First do a nslookup on the FQDN of your domain, check to make sure there are no invalid IP addresses returned (I've seen sometimes a 2nd unused NIC on a DC with 169.254.x.x address register itself in DNS as a valid NS/DC). Next on the DNS server check SRV entries for LDAP and KRB, make sure they are all valid.






          share|improve this answer



















          • 1





            Not a bad answer, but the out of space error is much more likely about memory or item number/database limits. By the time you have so little disk space, your DHCP service is failing, you'll have noticed other, bigger problems.

            – HopelessN00b
            Oct 7 '12 at 18:48











          • Microsoft is notoriously bad about throwing this kind of error as an "if all else fails" error. Also, "storage space" refers to a specific "flavor" of memory to be allocated rather than disk space very frequently with this error.

            – Evan Anderson
            Jul 15 '13 at 16:16
















          3














          This part really jumps out at me:




          • "Not enough storage is available to complete this operation".


          I'm assuming that you actually do have disk space available on the server. This points to the possibility of data or disk corruption. Have you run a chkdsk? Do the credentials the DHCP service runs under have permissions to the log directory and to the directory where the DHCP db is stored?



          Ruling out those possibilities, next step is to check that there are no invalid entries in DNS for your domain, especially if there was a DC that was removed from the domain at some point. First do a nslookup on the FQDN of your domain, check to make sure there are no invalid IP addresses returned (I've seen sometimes a 2nd unused NIC on a DC with 169.254.x.x address register itself in DNS as a valid NS/DC). Next on the DNS server check SRV entries for LDAP and KRB, make sure they are all valid.






          share|improve this answer



















          • 1





            Not a bad answer, but the out of space error is much more likely about memory or item number/database limits. By the time you have so little disk space, your DHCP service is failing, you'll have noticed other, bigger problems.

            – HopelessN00b
            Oct 7 '12 at 18:48











          • Microsoft is notoriously bad about throwing this kind of error as an "if all else fails" error. Also, "storage space" refers to a specific "flavor" of memory to be allocated rather than disk space very frequently with this error.

            – Evan Anderson
            Jul 15 '13 at 16:16














          3












          3








          3







          This part really jumps out at me:




          • "Not enough storage is available to complete this operation".


          I'm assuming that you actually do have disk space available on the server. This points to the possibility of data or disk corruption. Have you run a chkdsk? Do the credentials the DHCP service runs under have permissions to the log directory and to the directory where the DHCP db is stored?



          Ruling out those possibilities, next step is to check that there are no invalid entries in DNS for your domain, especially if there was a DC that was removed from the domain at some point. First do a nslookup on the FQDN of your domain, check to make sure there are no invalid IP addresses returned (I've seen sometimes a 2nd unused NIC on a DC with 169.254.x.x address register itself in DNS as a valid NS/DC). Next on the DNS server check SRV entries for LDAP and KRB, make sure they are all valid.






          share|improve this answer













          This part really jumps out at me:




          • "Not enough storage is available to complete this operation".


          I'm assuming that you actually do have disk space available on the server. This points to the possibility of data or disk corruption. Have you run a chkdsk? Do the credentials the DHCP service runs under have permissions to the log directory and to the directory where the DHCP db is stored?



          Ruling out those possibilities, next step is to check that there are no invalid entries in DNS for your domain, especially if there was a DC that was removed from the domain at some point. First do a nslookup on the FQDN of your domain, check to make sure there are no invalid IP addresses returned (I've seen sometimes a 2nd unused NIC on a DC with 169.254.x.x address register itself in DNS as a valid NS/DC). Next on the DNS server check SRV entries for LDAP and KRB, make sure they are all valid.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Sep 17 '12 at 14:23









          JayBeeJayBee

          312




          312








          • 1





            Not a bad answer, but the out of space error is much more likely about memory or item number/database limits. By the time you have so little disk space, your DHCP service is failing, you'll have noticed other, bigger problems.

            – HopelessN00b
            Oct 7 '12 at 18:48











          • Microsoft is notoriously bad about throwing this kind of error as an "if all else fails" error. Also, "storage space" refers to a specific "flavor" of memory to be allocated rather than disk space very frequently with this error.

            – Evan Anderson
            Jul 15 '13 at 16:16














          • 1





            Not a bad answer, but the out of space error is much more likely about memory or item number/database limits. By the time you have so little disk space, your DHCP service is failing, you'll have noticed other, bigger problems.

            – HopelessN00b
            Oct 7 '12 at 18:48











          • Microsoft is notoriously bad about throwing this kind of error as an "if all else fails" error. Also, "storage space" refers to a specific "flavor" of memory to be allocated rather than disk space very frequently with this error.

            – Evan Anderson
            Jul 15 '13 at 16:16








          1




          1





          Not a bad answer, but the out of space error is much more likely about memory or item number/database limits. By the time you have so little disk space, your DHCP service is failing, you'll have noticed other, bigger problems.

          – HopelessN00b
          Oct 7 '12 at 18:48





          Not a bad answer, but the out of space error is much more likely about memory or item number/database limits. By the time you have so little disk space, your DHCP service is failing, you'll have noticed other, bigger problems.

          – HopelessN00b
          Oct 7 '12 at 18:48













          Microsoft is notoriously bad about throwing this kind of error as an "if all else fails" error. Also, "storage space" refers to a specific "flavor" of memory to be allocated rather than disk space very frequently with this error.

          – Evan Anderson
          Jul 15 '13 at 16:16





          Microsoft is notoriously bad about throwing this kind of error as an "if all else fails" error. Also, "storage space" refers to a specific "flavor" of memory to be allocated rather than disk space very frequently with this error.

          – Evan Anderson
          Jul 15 '13 at 16:16











          0














          The issues seems that you are not an enterprise administrator of your the tree in your forest. Do you have any other DHCP's in your domain? Because if you do, try to de-authorize it and see if you can, if you can't then you don't have access which proves the point of not being an enterprise administrator. Please also take a look at this article:



          http://technet.microsoft.com/en-us/library/cc775255(v=ws.10).aspx






          share|improve this answer
























          • We have the same issues and being an Enterprise Administrator doesn't solve it. We tried looking but couldn't find a document that describes what exactly associates the DHCP and AD services.

            – nearora
            May 31 '12 at 3:40











          • @nearora how often does this occur in your environment?

            – ewwhite
            Jun 5 '12 at 14:23











          • @ewwhite, it is permanent. Even a reboot hasn't fixed it for us from what I recall. We've only tried it with a R&D setup with stock standard MS Windows Server 2008 R2. If you need any information for debugging, I could get it, but might take a while as I need to hassle a colleague to let me use their setup.

            – nearora
            Jun 5 '12 at 22:09
















          0














          The issues seems that you are not an enterprise administrator of your the tree in your forest. Do you have any other DHCP's in your domain? Because if you do, try to de-authorize it and see if you can, if you can't then you don't have access which proves the point of not being an enterprise administrator. Please also take a look at this article:



          http://technet.microsoft.com/en-us/library/cc775255(v=ws.10).aspx






          share|improve this answer
























          • We have the same issues and being an Enterprise Administrator doesn't solve it. We tried looking but couldn't find a document that describes what exactly associates the DHCP and AD services.

            – nearora
            May 31 '12 at 3:40











          • @nearora how often does this occur in your environment?

            – ewwhite
            Jun 5 '12 at 14:23











          • @ewwhite, it is permanent. Even a reboot hasn't fixed it for us from what I recall. We've only tried it with a R&D setup with stock standard MS Windows Server 2008 R2. If you need any information for debugging, I could get it, but might take a while as I need to hassle a colleague to let me use their setup.

            – nearora
            Jun 5 '12 at 22:09














          0












          0








          0







          The issues seems that you are not an enterprise administrator of your the tree in your forest. Do you have any other DHCP's in your domain? Because if you do, try to de-authorize it and see if you can, if you can't then you don't have access which proves the point of not being an enterprise administrator. Please also take a look at this article:



          http://technet.microsoft.com/en-us/library/cc775255(v=ws.10).aspx






          share|improve this answer













          The issues seems that you are not an enterprise administrator of your the tree in your forest. Do you have any other DHCP's in your domain? Because if you do, try to de-authorize it and see if you can, if you can't then you don't have access which proves the point of not being an enterprise administrator. Please also take a look at this article:



          http://technet.microsoft.com/en-us/library/cc775255(v=ws.10).aspx







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered May 29 '12 at 20:53









          WeAreYoungWeAreYoung

          1




          1













          • We have the same issues and being an Enterprise Administrator doesn't solve it. We tried looking but couldn't find a document that describes what exactly associates the DHCP and AD services.

            – nearora
            May 31 '12 at 3:40











          • @nearora how often does this occur in your environment?

            – ewwhite
            Jun 5 '12 at 14:23











          • @ewwhite, it is permanent. Even a reboot hasn't fixed it for us from what I recall. We've only tried it with a R&D setup with stock standard MS Windows Server 2008 R2. If you need any information for debugging, I could get it, but might take a while as I need to hassle a colleague to let me use their setup.

            – nearora
            Jun 5 '12 at 22:09



















          • We have the same issues and being an Enterprise Administrator doesn't solve it. We tried looking but couldn't find a document that describes what exactly associates the DHCP and AD services.

            – nearora
            May 31 '12 at 3:40











          • @nearora how often does this occur in your environment?

            – ewwhite
            Jun 5 '12 at 14:23











          • @ewwhite, it is permanent. Even a reboot hasn't fixed it for us from what I recall. We've only tried it with a R&D setup with stock standard MS Windows Server 2008 R2. If you need any information for debugging, I could get it, but might take a while as I need to hassle a colleague to let me use their setup.

            – nearora
            Jun 5 '12 at 22:09

















          We have the same issues and being an Enterprise Administrator doesn't solve it. We tried looking but couldn't find a document that describes what exactly associates the DHCP and AD services.

          – nearora
          May 31 '12 at 3:40





          We have the same issues and being an Enterprise Administrator doesn't solve it. We tried looking but couldn't find a document that describes what exactly associates the DHCP and AD services.

          – nearora
          May 31 '12 at 3:40













          @nearora how often does this occur in your environment?

          – ewwhite
          Jun 5 '12 at 14:23





          @nearora how often does this occur in your environment?

          – ewwhite
          Jun 5 '12 at 14:23













          @ewwhite, it is permanent. Even a reboot hasn't fixed it for us from what I recall. We've only tried it with a R&D setup with stock standard MS Windows Server 2008 R2. If you need any information for debugging, I could get it, but might take a while as I need to hassle a colleague to let me use their setup.

          – nearora
          Jun 5 '12 at 22:09





          @ewwhite, it is permanent. Even a reboot hasn't fixed it for us from what I recall. We've only tried it with a R&D setup with stock standard MS Windows Server 2008 R2. If you need any information for debugging, I could get it, but might take a while as I need to hassle a colleague to let me use their setup.

          – nearora
          Jun 5 '12 at 22:09











          0














          Maybe there is a rogue dhcp server (Check with nmap)? Also, check http://support.microsoft.com/kb/938456 describing conflicting records in AD.






          share|improve this answer
























          • Not seeing any rogue dhcp servers on the network.

            – ewwhite
            Jun 5 '12 at 14:22
















          0














          Maybe there is a rogue dhcp server (Check with nmap)? Also, check http://support.microsoft.com/kb/938456 describing conflicting records in AD.






          share|improve this answer
























          • Not seeing any rogue dhcp servers on the network.

            – ewwhite
            Jun 5 '12 at 14:22














          0












          0








          0







          Maybe there is a rogue dhcp server (Check with nmap)? Also, check http://support.microsoft.com/kb/938456 describing conflicting records in AD.






          share|improve this answer













          Maybe there is a rogue dhcp server (Check with nmap)? Also, check http://support.microsoft.com/kb/938456 describing conflicting records in AD.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Jun 1 '12 at 19:04









          JGurtzJGurtz

          491412




          491412













          • Not seeing any rogue dhcp servers on the network.

            – ewwhite
            Jun 5 '12 at 14:22



















          • Not seeing any rogue dhcp servers on the network.

            – ewwhite
            Jun 5 '12 at 14:22

















          Not seeing any rogue dhcp servers on the network.

          – ewwhite
          Jun 5 '12 at 14:22





          Not seeing any rogue dhcp servers on the network.

          – ewwhite
          Jun 5 '12 at 14:22











          0














          maybe you run into a bug.
          http://support.microsoft.com/kb/2632816/en-gb






          share|improve this answer




























            0














            maybe you run into a bug.
            http://support.microsoft.com/kb/2632816/en-gb






            share|improve this answer


























              0












              0








              0







              maybe you run into a bug.
              http://support.microsoft.com/kb/2632816/en-gb






              share|improve this answer













              maybe you run into a bug.
              http://support.microsoft.com/kb/2632816/en-gb







              share|improve this answer












              share|improve this answer



              share|improve this answer










              answered Jun 2 '12 at 21:20









              user1008764user1008764

              1,0862812




              1,0862812























                  0














                  Just a few articles to look at...some may not seem to apply, but look carefully and consider the causes in each article:



                  http://support.microsoft.com/kb/935744



                  http://blogs.technet.com/b/abizerh/archive/2009/07/12/troubleshooting-the-error-not-enough-storage-is-available-to-complete-this-operation.aspx



                  http://forums.whirlpool.net.au/archive/1533833






                  share|improve this answer




























                    0














                    Just a few articles to look at...some may not seem to apply, but look carefully and consider the causes in each article:



                    http://support.microsoft.com/kb/935744



                    http://blogs.technet.com/b/abizerh/archive/2009/07/12/troubleshooting-the-error-not-enough-storage-is-available-to-complete-this-operation.aspx



                    http://forums.whirlpool.net.au/archive/1533833






                    share|improve this answer


























                      0












                      0








                      0







                      Just a few articles to look at...some may not seem to apply, but look carefully and consider the causes in each article:



                      http://support.microsoft.com/kb/935744



                      http://blogs.technet.com/b/abizerh/archive/2009/07/12/troubleshooting-the-error-not-enough-storage-is-available-to-complete-this-operation.aspx



                      http://forums.whirlpool.net.au/archive/1533833






                      share|improve this answer













                      Just a few articles to look at...some may not seem to apply, but look carefully and consider the causes in each article:



                      http://support.microsoft.com/kb/935744



                      http://blogs.technet.com/b/abizerh/archive/2009/07/12/troubleshooting-the-error-not-enough-storage-is-available-to-complete-this-operation.aspx



                      http://forums.whirlpool.net.au/archive/1533833







                      share|improve this answer












                      share|improve this answer



                      share|improve this answer










                      answered Jun 5 '12 at 15:55









                      TheCleanerTheCleaner

                      28.3k23107182




                      28.3k23107182























                          0














                          I would check for AD replication issues.



                          http://www.microsoft.com/en-us/download/details.aspx?id=30005






                          share|improve this answer




























                            0














                            I would check for AD replication issues.



                            http://www.microsoft.com/en-us/download/details.aspx?id=30005






                            share|improve this answer


























                              0












                              0








                              0







                              I would check for AD replication issues.



                              http://www.microsoft.com/en-us/download/details.aspx?id=30005






                              share|improve this answer













                              I would check for AD replication issues.



                              http://www.microsoft.com/en-us/download/details.aspx?id=30005







                              share|improve this answer












                              share|improve this answer



                              share|improve this answer










                              answered Jun 18 '12 at 0:32









                              shouldbeq931shouldbeq931

                              459311




                              459311























                                  0














                                  Couple of questions for you...
                                  Can you try running a DCDiag on both DCs and posting any errors? Are there any other errors in the event logs? If there's no errors now try running it again on both dcs when the service has failed before rebooting the server.



                                  Have you tried simply reinstalling DHCP on the trouble server?






                                  share|improve this answer
























                                  • DCDiag fails on the affected server when this happens. Again, it's once every few weeks, so I need to catch it in progress again before I can troubleshoot more.

                                    – ewwhite
                                    Aug 15 '12 at 20:22











                                  • No problem, those issues are always the hardest to track down.

                                    – Jason
                                    Aug 15 '12 at 20:30
















                                  0














                                  Couple of questions for you...
                                  Can you try running a DCDiag on both DCs and posting any errors? Are there any other errors in the event logs? If there's no errors now try running it again on both dcs when the service has failed before rebooting the server.



                                  Have you tried simply reinstalling DHCP on the trouble server?






                                  share|improve this answer
























                                  • DCDiag fails on the affected server when this happens. Again, it's once every few weeks, so I need to catch it in progress again before I can troubleshoot more.

                                    – ewwhite
                                    Aug 15 '12 at 20:22











                                  • No problem, those issues are always the hardest to track down.

                                    – Jason
                                    Aug 15 '12 at 20:30














                                  0












                                  0








                                  0







                                  Couple of questions for you...
                                  Can you try running a DCDiag on both DCs and posting any errors? Are there any other errors in the event logs? If there's no errors now try running it again on both dcs when the service has failed before rebooting the server.



                                  Have you tried simply reinstalling DHCP on the trouble server?






                                  share|improve this answer













                                  Couple of questions for you...
                                  Can you try running a DCDiag on both DCs and posting any errors? Are there any other errors in the event logs? If there's no errors now try running it again on both dcs when the service has failed before rebooting the server.



                                  Have you tried simply reinstalling DHCP on the trouble server?







                                  share|improve this answer












                                  share|improve this answer



                                  share|improve this answer










                                  answered Aug 15 '12 at 20:20









                                  JasonJason

                                  312




                                  312













                                  • DCDiag fails on the affected server when this happens. Again, it's once every few weeks, so I need to catch it in progress again before I can troubleshoot more.

                                    – ewwhite
                                    Aug 15 '12 at 20:22











                                  • No problem, those issues are always the hardest to track down.

                                    – Jason
                                    Aug 15 '12 at 20:30



















                                  • DCDiag fails on the affected server when this happens. Again, it's once every few weeks, so I need to catch it in progress again before I can troubleshoot more.

                                    – ewwhite
                                    Aug 15 '12 at 20:22











                                  • No problem, those issues are always the hardest to track down.

                                    – Jason
                                    Aug 15 '12 at 20:30

















                                  DCDiag fails on the affected server when this happens. Again, it's once every few weeks, so I need to catch it in progress again before I can troubleshoot more.

                                  – ewwhite
                                  Aug 15 '12 at 20:22





                                  DCDiag fails on the affected server when this happens. Again, it's once every few weeks, so I need to catch it in progress again before I can troubleshoot more.

                                  – ewwhite
                                  Aug 15 '12 at 20:22













                                  No problem, those issues are always the hardest to track down.

                                  – Jason
                                  Aug 15 '12 at 20:30





                                  No problem, those issues are always the hardest to track down.

                                  – Jason
                                  Aug 15 '12 at 20:30











                                  0














                                  So, two virtual Domain Controllers... are both DHCP servers? It sounds like only one is. In which case I'd be tempted to run for a few weeks with the DHCP server only using the other domain controller as DNS. And then for a few weeks with the other domain controller shut down.



                                  You can always revert the change if it impacts on users but it might help narrow down which box (if it is only one) is causing the issue.



                                  I'd also be tempted to add a third DC and then decommission the second one to rule out it being some weird installation corruption of the type Windows loves to flump into.



                                  Have you tried restarting services on the DC rather than rebooting it?



                                  Do the DCs host other services (file, exchange, etc)? Since you've got a virtualised environment do you have headroom to move those services onto their own servers for a few weeks to rule out confusion from those roles clashing?



                                  Additionally, and since it hasn't been commented on, with respect to the "Not enough storage is available to complete this operation" error. If the server's disks are full then all of its DC functions are going to start to fail. Are the disks full?






                                  share|improve this answer




























                                    0














                                    So, two virtual Domain Controllers... are both DHCP servers? It sounds like only one is. In which case I'd be tempted to run for a few weeks with the DHCP server only using the other domain controller as DNS. And then for a few weeks with the other domain controller shut down.



                                    You can always revert the change if it impacts on users but it might help narrow down which box (if it is only one) is causing the issue.



                                    I'd also be tempted to add a third DC and then decommission the second one to rule out it being some weird installation corruption of the type Windows loves to flump into.



                                    Have you tried restarting services on the DC rather than rebooting it?



                                    Do the DCs host other services (file, exchange, etc)? Since you've got a virtualised environment do you have headroom to move those services onto their own servers for a few weeks to rule out confusion from those roles clashing?



                                    Additionally, and since it hasn't been commented on, with respect to the "Not enough storage is available to complete this operation" error. If the server's disks are full then all of its DC functions are going to start to fail. Are the disks full?






                                    share|improve this answer


























                                      0












                                      0








                                      0







                                      So, two virtual Domain Controllers... are both DHCP servers? It sounds like only one is. In which case I'd be tempted to run for a few weeks with the DHCP server only using the other domain controller as DNS. And then for a few weeks with the other domain controller shut down.



                                      You can always revert the change if it impacts on users but it might help narrow down which box (if it is only one) is causing the issue.



                                      I'd also be tempted to add a third DC and then decommission the second one to rule out it being some weird installation corruption of the type Windows loves to flump into.



                                      Have you tried restarting services on the DC rather than rebooting it?



                                      Do the DCs host other services (file, exchange, etc)? Since you've got a virtualised environment do you have headroom to move those services onto their own servers for a few weeks to rule out confusion from those roles clashing?



                                      Additionally, and since it hasn't been commented on, with respect to the "Not enough storage is available to complete this operation" error. If the server's disks are full then all of its DC functions are going to start to fail. Are the disks full?






                                      share|improve this answer













                                      So, two virtual Domain Controllers... are both DHCP servers? It sounds like only one is. In which case I'd be tempted to run for a few weeks with the DHCP server only using the other domain controller as DNS. And then for a few weeks with the other domain controller shut down.



                                      You can always revert the change if it impacts on users but it might help narrow down which box (if it is only one) is causing the issue.



                                      I'd also be tempted to add a third DC and then decommission the second one to rule out it being some weird installation corruption of the type Windows loves to flump into.



                                      Have you tried restarting services on the DC rather than rebooting it?



                                      Do the DCs host other services (file, exchange, etc)? Since you've got a virtualised environment do you have headroom to move those services onto their own servers for a few weeks to rule out confusion from those roles clashing?



                                      Additionally, and since it hasn't been commented on, with respect to the "Not enough storage is available to complete this operation" error. If the server's disks are full then all of its DC functions are going to start to fail. Are the disks full?







                                      share|improve this answer












                                      share|improve this answer



                                      share|improve this answer










                                      answered Aug 21 '12 at 11:48









                                      Paul D'AmbraPaul D'Ambra

                                      90211122




                                      90211122























                                          0














                                          To resolve the issue, kindly remove the Server Bindings (Remember we have to have a Static IP address for the DHCP Server to do this).



                                          Steps:




                                          • Click Start, point to Programs, point to Administrative Tools, and then click DHCP.

                                          • Right click the name of the original DHCP server name.

                                          • Click on Add/Remove Bindings.

                                          • In Server Binding Properties, Uncheck the box for the Local Area Connection and click on OK.

                                          • Restart the DHCP Service if required.






                                          share|improve this answer


























                                          • There was no option to remove bindings. It was grayed-out in my case.

                                            – ewwhite
                                            Feb 25 '13 at 16:28


















                                          0














                                          To resolve the issue, kindly remove the Server Bindings (Remember we have to have a Static IP address for the DHCP Server to do this).



                                          Steps:




                                          • Click Start, point to Programs, point to Administrative Tools, and then click DHCP.

                                          • Right click the name of the original DHCP server name.

                                          • Click on Add/Remove Bindings.

                                          • In Server Binding Properties, Uncheck the box for the Local Area Connection and click on OK.

                                          • Restart the DHCP Service if required.






                                          share|improve this answer


























                                          • There was no option to remove bindings. It was grayed-out in my case.

                                            – ewwhite
                                            Feb 25 '13 at 16:28
















                                          0












                                          0








                                          0







                                          To resolve the issue, kindly remove the Server Bindings (Remember we have to have a Static IP address for the DHCP Server to do this).



                                          Steps:




                                          • Click Start, point to Programs, point to Administrative Tools, and then click DHCP.

                                          • Right click the name of the original DHCP server name.

                                          • Click on Add/Remove Bindings.

                                          • In Server Binding Properties, Uncheck the box for the Local Area Connection and click on OK.

                                          • Restart the DHCP Service if required.






                                          share|improve this answer















                                          To resolve the issue, kindly remove the Server Bindings (Remember we have to have a Static IP address for the DHCP Server to do this).



                                          Steps:




                                          • Click Start, point to Programs, point to Administrative Tools, and then click DHCP.

                                          • Right click the name of the original DHCP server name.

                                          • Click on Add/Remove Bindings.

                                          • In Server Binding Properties, Uncheck the box for the Local Area Connection and click on OK.

                                          • Restart the DHCP Service if required.







                                          share|improve this answer














                                          share|improve this answer



                                          share|improve this answer








                                          edited Feb 23 '13 at 0:33









                                          MDMarra

                                          92.9k28174314




                                          92.9k28174314










                                          answered Feb 23 '13 at 0:01









                                          William MascarenhasWilliam Mascarenhas

                                          1




                                          1













                                          • There was no option to remove bindings. It was grayed-out in my case.

                                            – ewwhite
                                            Feb 25 '13 at 16:28





















                                          • There was no option to remove bindings. It was grayed-out in my case.

                                            – ewwhite
                                            Feb 25 '13 at 16:28



















                                          There was no option to remove bindings. It was grayed-out in my case.

                                          – ewwhite
                                          Feb 25 '13 at 16:28







                                          There was no option to remove bindings. It was grayed-out in my case.

                                          – ewwhite
                                          Feb 25 '13 at 16:28







                                          protected by Community 1 hour ago



                                          Thank you for your interest in this question.
                                          Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



                                          Would you like to answer one of these unanswered questions instead?



                                          Popular posts from this blog

                                          As a Security Precaution, the user account has been locked The Next CEO of Stack OverflowMS...

                                          Список ссавців Італії Природоохоронні статуси | Список |...

                                          Українські прізвища Зміст Історичні відомості |...