W2K Cluster not pulling time from W2K3 Domain

  • Thread starter Thread starter Smokey Grindel
  • Start date Start date
S

Smokey Grindel

We have a 2 node windows 2000 SP4 cluster... they used to be domain
controllers... they where later demoted when we brought up our new W2K3
domain controllers... but when we did this the time on the 2 nodes doesn't
sync anymore... and it doesnt seem to want to get it from the domain
either...any idea on what to do to get it to sync time with the domain
agian? thanks!
 
Hello Smokey,

You have to reconfigure the time synchronisation for the demoted servers:

http://technet2.microsoft.com/windo...c594-4d43-9195-e54e4cb89d251033.mspx?mfr=true


Best regards

Meinolf Weber (Myweb)
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.

> We have a 2 node windows 2000 SP4 cluster... they used to be domain
> controllers... they where later demoted when we brought up our new
> W2K3 domain controllers... but when we did this the time on the 2
> nodes doesn't sync anymore... and it doesnt seem to want to get it
> from the domain either...any idea on what to do to get it to sync time
> with the domain agian? thanks!
>
 
Thank you for the information!

"Meinolf Weber (Myweb)" <meiweb@gmx.de> wrote in message
news:ff16fb664c2cc8c9af1c979b7c80@msnews.microsoft.com...
> Hello Smokey,
>
> You have to reconfigure the time synchronisation for the demoted servers:
>
> http://technet2.microsoft.com/windo...c594-4d43-9195-e54e4cb89d251033.mspx?mfr=true
>
>
> Best regards
>
> Meinolf Weber (Myweb)
> Disclaimer: This posting is provided "AS IS" with no warranties, and
> confers no rights.
>
>> We have a 2 node windows 2000 SP4 cluster... they used to be domain
>> controllers... they where later demoted when we brought up our new
>> W2K3 domain controllers... but when we did this the time on the 2
>> nodes doesn't sync anymore... and it doesnt seem to want to get it
>> from the domain either...any idea on what to do to get it to sync time
>> with the domain agian? thanks!
>>
>
>
 
just tried it and its a no-go with the w2k cluster... cant do it locally
since that is a new set of parameters... and cant do it remotely... the
domain itself is syncing time fine, its just the two old ones that dont even
want to talk to the domain's time servers

"Meinolf Weber (Myweb)" <meiweb@gmx.de> wrote in message
news:ff16fb664c2cc8c9af1c979b7c80@msnews.microsoft.com...
> Hello Smokey,
>
> You have to reconfigure the time synchronisation for the demoted servers:
>
> http://technet2.microsoft.com/windo...c594-4d43-9195-e54e4cb89d251033.mspx?mfr=true
>
>
> Best regards
>
> Meinolf Weber (Myweb)
> Disclaimer: This posting is provided "AS IS" with no warranties, and
> confers no rights.
>
>> We have a 2 node windows 2000 SP4 cluster... they used to be domain
>> controllers... they where later demoted when we brought up our new
>> W2K3 domain controllers... but when we did this the time on the 2
>> nodes doesn't sync anymore... and it doesnt seem to want to get it
>> from the domain either...any idea on what to do to get it to sync time
>> with the domain agian? thanks!
>>
>
>
 
Hello Smokey,

Have a look here:
http://www.eventid.net/display.asp?eventid=22&eventno=1084&source=TimeServ&phase=1

Best regards

Meinolf Weber (Myweb)
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.

> just tried it and its a no-go with the w2k cluster... cant do it
> locally since that is a new set of parameters... and cant do it
> remotely... the domain itself is syncing time fine, its just the two
> old ones that dont even want to talk to the domain's time servers
>
> "Meinolf Weber (Myweb)" <meiweb@gmx.de> wrote in message
> news:ff16fb664c2cc8c9af1c979b7c80@msnews.microsoft.com...
>
>> Hello Smokey,
>>
>> You have to reconfigure the time synchronisation for the demoted
>> servers:
>>
>> http://technet2.microsoft.com/windowsserver/en/library/4a63190b-c594-
>> 4d43-9195-e54e4cb89d251033.mspx?mfr=true
>>
>> Best regards
>>
>> Meinolf Weber (Myweb)
>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>> confers no rights.
>>> We have a 2 node windows 2000 SP4 cluster... they used to be domain
>>> controllers... they where later demoted when we brought up our new
>>> W2K3 domain controllers... but when we did this the time on the 2
>>> nodes doesn't sync anymore... and it doesnt seem to want to get it
>>> from the domain either...any idea on what to do to get it to sync
>>> time with the domain agian? thanks!
>>>
 
Alrighty, that fixed the TimeServ problem, now getting w32tm errors in the
event log....

Event Type: Error
Event Source: w32time
Event Category: None
Event ID: 49
Date: 8/17/2007
Time: 2:09:02 PM
User: N/A
Computer: NODE2
Description:
An unexpected error occured while trying to start the server. The port may
already be in use.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 00 00 ....
 
Try:

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

Regards,
John

Visit my blog: http://msmvps.com/blogs/jtoner

"Smokey Grindel" <nospam@nospam.com> wrote in message
news:e8CVcAQ4HHA.3684@TK2MSFTNGP02.phx.gbl...
> Alrighty, that fixed the TimeServ problem, now getting w32tm errors in the
> event log....
>
> Event Type: Error
> Event Source: w32time
> Event Category: None
> Event ID: 49
> Date: 8/17/2007
> Time: 2:09:02 PM
> User: N/A
> Computer: NODE2
> Description:
> An unexpected error occured while trying to start the server. The port may
> already be in use.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: 00 00 00 00 ....
>
>
>
>
 
no no wait I spoke too soon.. now w32tm events coming back saying sync with
domain successful! yay! thanks!

"Smokey Grindel" <nospam@nospam.com> wrote in message
news:e8CVcAQ4HHA.3684@TK2MSFTNGP02.phx.gbl...
> Alrighty, that fixed the TimeServ problem, now getting w32tm errors in the
> event log....
>
> Event Type: Error
> Event Source: w32time
> Event Category: None
> Event ID: 49
> Date: 8/17/2007
> Time: 2:09:02 PM
> User: N/A
> Computer: NODE2
> Description:
> An unexpected error occured while trying to start the server. The port may
> already be in use.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: 00 00 00 00 ....
>
>
>
>
 
Hello Smokey,

For this check out this one:
http://support.microsoft.com/kb/247321

http://dtdocs.ntp-systems.com/kb/kb2002.101.asp

http://www.eventid.net/display.asp?eventid=49&eventno=587&source=w32time&phase=1

Best regards

Meinolf Weber (Myweb)
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.

> Alrighty, that fixed the TimeServ problem, now getting w32tm errors in
> the event log....
>
> Event Type: Error
> Event Source: w32time
> Event Category: None
> Event ID: 49
> Date: 8/17/2007
> Time: 2:09:02 PM
> User: N/A
> Computer: NODE2
> Description:
> An unexpected error occured while trying to start the server. The port
> may
> already be in use.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: 00 00 00 00 ....
 
Hello Smokey,

Nice to hear.

Best regards

Meinolf Weber (Myweb)
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.

> no no wait I spoke too soon.. now w32tm events coming back saying sync
> with domain successful! yay! thanks!
>
> "Smokey Grindel" <nospam@nospam.com> wrote in message
> news:e8CVcAQ4HHA.3684@TK2MSFTNGP02.phx.gbl...
>
>> Alrighty, that fixed the TimeServ problem, now getting w32tm errors
>> in the event log....
>>
>> Event Type: Error
>> Event Source: w32time
>> Event Category: None
>> Event ID: 49
>> Date: 8/17/2007
>> Time: 2:09:02 PM
>> User: N/A
>> Computer: NODE2
>> Description:
>> An unexpected error occured while trying to start the server. The
>> port may
>> already be in use.
>> For more information, see Help and Support Center at
>> http://go.microsoft.com/fwlink/events.asp.
>> Data:
>> 0000: 00 00 00 00 ....
 
Back
Top