2003 DC hangs at applying computer settings

  • Thread starter Thread starter MSNewsgrp
  • Start date Start date
M

MSNewsgrp

Guest
I have a strange problem. 1 of 2 DCs (not the PDCe or FSMO)
rebooted/crashed yesterday and it looked like a power failure as the reason
came up unknown and there were no errors/warnings in event log. I also
checked the HP logs
as this is a Proliant server ML350. I removed the network connection and
it booted up OK- notwithstanding the expected errors. I was able to start
the sevrices manually and get the DC online. Now I am trying to find the
problem. I am leading towards a GP cause. The only possible issue was
that it had been pointing to itself as the time source and not the PDCe. I
corrected that but didnt reboot yet as I am letting it run overnight.

Anything else possible with above scenario- oh, I know about the old APC
issue and we fixed that years ago.

Much regards

Cranky
 
Re: 2003 DC hangs at applying computer settings

Hello MSNewsgrp,

Is the DC also DNS server? If not make sure that it uses as preferred DNS
server the other DC/DNS machine. Please post an unedited ipconfig /all from
both DC's to check that the settings are as needed.

Time service has nothing to do with blocking the startup. If time synchronisation
does not work you only get errors in the event viewer. Also you have not
to set any time server by hand on domain machine. All DC's will use automatically
the PDCEmulator for synchronisation. Member servers and clients use one available
DC.

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

> I have a strange problem. 1 of 2 DCs (not the PDCe or FSMO)
> rebooted/crashed yesterday and it looked like a power failure as the
> reason
> came up unknown and there were no errors/warnings in event log. I
> also
> checked the HP logs
> as this is a Proliant server ML350. I removed the network connection
> and
> it booted up OK- notwithstanding the expected errors. I was able to
> start
> the sevrices manually and get the DC online. Now I am trying to
> find the
> problem. I am leading towards a GP cause. The only possible issue
> was
> that it had been pointing to itself as the time source and not the
> PDCe. I
> corrected that but didnt reboot yet as I am letting it run overnight.
> Anything else possible with above scenario- oh, I know about the old
> APC issue and we fixed that years ago.
>
> Much regards
>
> Cranky
>
 
Re: 2003 DC hangs at applying computer settings

Thanks and sorry bout the crosspost.
It points to itself for DNS and it passed all tests in dcdiag and netdiag


"Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message
news:ff16fb66a60e38cac9406e2c8f5e@msnews.microsoft.com...
> Hello MSNewsgrp,
>
> Is the DC also DNS server? If not make sure that it uses as preferred DNS
> server the other DC/DNS machine. Please post an unedited ipconfig /all
> from both DC's to check that the settings are as needed.
>
> Time service has nothing to do with blocking the startup. If time
> synchronisation does not work you only get errors in the event viewer.
> Also you have not to set any time server by hand on domain machine. All
> DC's will use automatically the PDCEmulator for synchronisation. Member
> servers and clients use one available DC.
>
> 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
>
>> I have a strange problem. 1 of 2 DCs (not the PDCe or FSMO)
>> rebooted/crashed yesterday and it looked like a power failure as the
>> reason
>> came up unknown and there were no errors/warnings in event log. I
>> also
>> checked the HP logs
>> as this is a Proliant server ML350. I removed the network connection
>> and
>> it booted up OK- notwithstanding the expected errors. I was able to
>> start
>> the sevrices manually and get the DC online. Now I am trying to
>> find the
>> problem. I am leading towards a GP cause. The only possible issue
>> was
>> that it had been pointing to itself as the time source and not the
>> PDCe. I
>> corrected that but didnt reboot yet as I am letting it run overnight.
>> Anything else possible with above scenario- oh, I know about the old
>> APC issue and we fixed that years ago.
>>
>> Much regards
>>
>> Cranky
>>
>
>
 
Back
Top