|
| |||||||||
| Tags: administorator, availableafter, controller, options, w2k3 |
 |
| | Thread Tools | Search this Thread |
|
#1
22-10-2009
| |||
| |||
| How to logon to W2K3 Domain Controller if "domain is not available"after trying to logon as as Administorator ? Options
We have a minor issue with our DC that starts the netlogon service 'paused' after every reboot. Since this happens, we cannot logon to the Domain Controller as Administrator due to "domain is not available" error. The only way that I know of to logon is to boot up our secondary Controller. This happens after a power outage , etc. Our backup Controller always has to be on before we log on to our 'main' Domain Controller. If our secondary controller failed, and the primary cannot log on due to this "domain is not available" error, how would I be able to get around this? TIA.  |
|
#2
23-10-2009
| |||
| |||
| Re: How to logon to W2K3 Domain Controller if "domain is not available" after trying to logon as as Administorator ? Options
Hello Tom, If i understand you correct you have 2 DCs and if you boot the so called secondary DC, everything is fine. This sounds for me that you have only one DC with the DNS server role. To connect/start the domain a DNS server MUST be available. So if the so called primary DC is not DNS server it can not find/start the domain. Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights. ** Please do NOT email, only reply to Newsgroups ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm > We have a minor issue with our DC that starts the netlogon service > 'paused' after every reboot. > Since this happens, we cannot logon to the Domain Controller as > Administrator due to "domain is not available" error. > The only way that I know of to logon is to boot up our secondary > Controller. > This happens after a power outage , etc. Our backup Controller > always > has to be on before we log on to our 'main' Domain Controller. > If our secondary controller failed, and the primary cannot log on due > to this "domain is not available" error, how would I be able to get > around this? > > TIA. > |
|
#3
23-10-2009
| |||
| |||
| Re: How to logon to W2K3 Domain Controller if "domain is not available" after trying to logon as as Administorator ? Options
"Meinolf Weber [MVP-DS]" <meiweb@(nospam)gmx.de> wrote in message news:6cb2911d80c88cc217c45d0ffa1@msnews.microsoft.com... Meinolf, Tom posted this in SBS, too, Check out the thread to what's already transpired. He may be having USN issues. From: Tom S <tsztur@gmail.com> Newsgroups: microsoft.public.windows.server.sbs Subject: How to logon to W2K3 Domain Controller if "domain is not available" after trying to logon as as Administorator ? Date: Thu, 22 Oct 2009 09:13:54 -0700 (PDT) Ace > Hello Tom, > > If i understand you correct you have 2 DCs and if you boot the so called > secondary DC, everything is fine. > > This sounds for me that you have only one DC with the DNS server role. To > connect/start the domain a DNS server MUST be available. So if the so > called primary DC is not DNS server it can not find/start the domain. > > Best regards > > Meinolf Weber > Disclaimer: This posting is provided "AS IS" with no warranties, and > confers no rights. > ** Please do NOT email, only reply to Newsgroups > ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm > >> We have a minor issue with our DC that starts the netlogon service >> 'paused' after every reboot. >> Since this happens, we cannot logon to the Domain Controller as >> Administrator due to "domain is not available" error. >> The only way that I know of to logon is to boot up our secondary >> Controller. >> This happens after a power outage , etc. Our backup Controller >> always >> has to be on before we log on to our 'main' Domain Controller. >> If our secondary controller failed, and the primary cannot log on due >> to this "domain is not available" error, how would I be able to get >> around this? >> >> TIA. >> > > |
|
#4
23-10-2009
| |||
| |||
| Re: How to logon to W2K3 Domain Controller if "domain is not available" after trying to logon as as Administorator ? Options
Hello Ace Fekay [MCT], Thanks, sounds a bit for USN problem, if i understand the error message about restore problems. Unfortunal the OP didn't mention any additional details here. Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights. ** Please do NOT email, only reply to Newsgroups ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm > "Meinolf Weber [MVP-DS]" <meiweb@(nospam)gmx.de> wrote in message > news:6cb2911d80c88cc217c45d0ffa1@msnews.microsoft.com... > > Meinolf, > > Tom posted this in SBS, too, Check out the thread to what's already > transpired. He may be having USN issues. > > From: Tom S <tsztur@gmail.com> > Newsgroups: microsoft.public.windows.server.sbs > Subject: How to logon to W2K3 Domain Controller if "domain is not > available" > after trying to logon as as Administorator ? > Date: Thu, 22 Oct 2009 09:13:54 -0700 (PDT) > Ace > >> Hello Tom, >> >> If i understand you correct you have 2 DCs and if you boot the so >> called secondary DC, everything is fine. >> >> This sounds for me that you have only one DC with the DNS server >> role. To connect/start the domain a DNS server MUST be available. So >> if the so called primary DC is not DNS server it can not find/start >> the domain. >> >> Best regards >> >> Meinolf Weber >> Disclaimer: This posting is provided "AS IS" with no warranties, and >> confers no rights. >> ** Please do NOT email, only reply to Newsgroups >> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm >>> We have a minor issue with our DC that starts the netlogon service >>> 'paused' after every reboot. >>> Since this happens, we cannot logon to the Domain Controller as >>> Administrator due to "domain is not available" error. >>> The only way that I know of to logon is to boot up our secondary >>> Controller. >>> This happens after a power outage , etc. Our backup Controller >>> always >>> has to be on before we log on to our 'main' Domain Controller. >>> If our secondary controller failed, and the primary cannot log on >>> due >>> to this "domain is not available" error, how would I be able to get >>> around this? >>> TIA. >>> |
|
#5
23-10-2009
| |||
| |||
| Re: How to logon to W2K3 Domain Controller if "domain is not available" after trying to logon as as Administorator ? Options
"Meinolf Weber [MVP-DS]" <meiweb@(nospam)gmx.de> wrote in message news:6cb2911d80fa8cc218e6988be5a@msnews.microsoft.com... > Hello Ace Fekay [MCT], > > Thanks, sounds a bit for USN problem, if i understand the error message > about restore problems. Unfortunal the OP didn't mention any additional > details here. > > Best regards > > Meinolf Weber Quoted from the other thread: === "Regarding any errors in the DC, none exist except for "The Active Directory database has been restored using an unsupported restoration procedure. Active Directory will be unable to log on users while this condition persists. As a result, the Net Logon service has paused. " === Looking it up, it's Event ID: 2103. I posted a couple of links for Tom to read up on this error message (KB888794 & KB875495). Not sure if it was restored with imaging software or if the AD database was manually copied at one time or other, because he did state that specific DC's netlogon service was set to manual and not automatic when they had to work on it in the past for some reason. Hope we can hear more from Tom so we can offer specific assistance. Ace |
|
#6
23-10-2009
| |||
| |||
| Re: How to logon to W2K3 Domain Controller if "domain is not available" after trying to logon as as Administorator ? Options
If you don't normally have the secondary dc up, you are creating problems. Specifically if the second dc was turned off for longer than the tombstone lifetime. All dc's should be available all the time to participate in replication, otherwise you can end up with lingering objects. Just reading further on, it appears you have a seond thread on this. You should cross post not double post. -- Paul Bergson MVP - Directory Services MCTS, MCT, MCSE, MCSA, Security+, BS CSci 2008, 2003, 2000 (Early Achiever), NT4 Microsoft's Thrive IT Pro of the Month - June 2009 http://www.pbbergs.com Please no e-mails, any questions should be posted in the NewsGroup This posting is provided "AS IS" with no warranties, and confers no rights. "Tom S" <tsztur@gmail.com> wrote in message news:44ab1adb-f131-4106-a8d2-adfd5785d2c0@m11g2000vbl.googlegroups.com... > We have a minor issue with our DC that starts the netlogon service > 'paused' after every reboot. > Since this happens, we cannot logon to the Domain Controller as > Administrator due to "domain is not available" error. > The only way that I know of to logon is to boot up our secondary > Controller. > > This happens after a power outage , etc. Our backup Controller > always > has to be on before we log on to our 'main' Domain Controller. > > > If our secondary controller failed, and the primary cannot log on due > to this "domain is not available" error, how would I be able to get > around this? > > > TIA. > |
|
|
| Thread Tools | Search this Thread |
| |
