 |
 |
|
|
|
|
Welcome to the { mindfrost82.com } forums. You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is fast, simple and absolutely free so please, join our community today! If you have any problems with the registration process or your account login, please contact contact us. |
|
|||||||
 |
|
|
LinkBack | Thread Tools | Search this Thread | Display Modes |
04-29-2008, 07:55 PM
|
|||
|
|||
|
NTPClient on DC fails to contact time source (W2K3 R2 64-bit)
Our W2K3 R2 64-bit DC has been up and running for some time, and getting
time updates regularly. Last week, it started a spate of failed attempts which have become rather chronic. First, I followed advice to set the time source: w32tm /config /manualpeerlist:time.nist.gov,0x8 /syncfromflags:MANUAL net stop w32time net start w32time w32tm /resync Had no luck. I verified that TCP & UDP ports 123 were available to the server and tested successfully with: w32tm /monitor /computers:time.nist.gov I also re-registered the service with: net stop w32time w32tm /unregister w32tm /register net start w32time Also to no avail. I did find a hotfix related (830092), but it appears it is only for the 32-bit version. Anything else I can try? 
|
|
04-30-2008, 09:34 AM
|
|||
|
|||
|
Re: NTPClient on DC fails to contact time source (W2K3 R2 64-bit)
Hello Dvord,
What happend, if you choose another time server? Is that the only DC in your 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 > Our W2K3 R2 64-bit DC has been up and running for some time, and > getting time updates regularly. > > Last week, it started a spate of failed attempts which have become > rather chronic. > > First, I followed advice to set the time source: > > w32tm /config /manualpeerlist:time.nist.gov,0x8 /syncfromflags:MANUAL > net stop w32time > net start w32time > w32tm /resync > Had no luck. I verified that TCP & UDP ports 123 were available to > the server and tested successfully with: > > w32tm /monitor /computers:time.nist.gov > > I also re-registered the service with: > > net stop w32time > w32tm /unregister > w32tm /register > net start w32time > Also to no avail. > > I did find a hotfix related (830092), but it appears it is only for > the 32-bit version. > > Anything else I can try? >
|
|
04-30-2008, 05:08 PM
|
|||
|
|||
|
Re: NTPClient on DC fails to contact time source (W2K3 R2 64-bit)
Thanks Meinolf,
Different time server, same results. The resync command generates this response: Sending resync command to local computer... The computer did not resync because no time data was available. "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message news:ff16fb6697fea8ca78c4df225bb0@msnews.microsoft .com... > Hello Dvord, > > What happend, if you choose another time server? Is that the only DC in > your 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 > >> Our W2K3 R2 64-bit DC has been up and running for some time, and >> getting time updates regularly. >> >> Last week, it started a spate of failed attempts which have become >> rather chronic. >> >> First, I followed advice to set the time source: >> >> w32tm /config /manualpeerlist:time.nist.gov,0x8 /syncfromflags:MANUAL >> net stop w32time >> net start w32time >> w32tm /resync >> Had no luck. I verified that TCP & UDP ports 123 were available to >> the server and tested successfully with: >> >> w32tm /monitor /computers:time.nist.gov >> >> I also re-registered the service with: >> >> net stop w32time >> w32tm /unregister >> w32tm /register >> net start w32time >> Also to no avail. >> >> I did find a hotfix related (830092), but it appears it is only for >> the 32-bit version. >> >> Anything else I can try? >> > >
|
|
04-30-2008, 05:51 PM
|
|||
|
|||
|
Re: NTPClient on DC fails to contact time source (W2K3 R2 64-bit)
I apologize I didn't answer the second question.
No it is not. I have two DC's. "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message news:ff16fb6697fea8ca78c4df225bb0@msnews.microsoft .com... > Hello Dvord, > > What happend, if you choose another time server? Is that the only DC in > your 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 > >> Our W2K3 R2 64-bit DC has been up and running for some time, and >> getting time updates regularly. >> >> Last week, it started a spate of failed attempts which have become >> rather chronic. >> >> First, I followed advice to set the time source: >> >> w32tm /config /manualpeerlist:time.nist.gov,0x8 /syncfromflags:MANUAL >> net stop w32time >> net start w32time >> w32tm /resync >> Had no luck. I verified that TCP & UDP ports 123 were available to >> the server and tested successfully with: >> >> w32tm /monitor /computers:time.nist.gov >> >> I also re-registered the service with: >> >> net stop w32time >> w32tm /unregister >> w32tm /register >> net start w32time >> Also to no avail. >> >> I did find a hotfix related (830092), but it appears it is only for >> the 32-bit version. >> >> Anything else I can try? >> > >
|
|
05-02-2008, 01:40 PM
|
|||
|
|||
|
Re: NTPClient on DC fails to contact time source (W2K3 R2 64-bit)
Hello Dvord,
It is the PDCEmulator where you are running the time server, i assume? Was there another time server before? 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 apologize I didn't answer the second question. > > No it is not. I have two DC's. > > "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message > news:ff16fb6697fea8ca78c4df225bb0@msnews.microsoft .com... > >> Hello Dvord, >> >> What happend, if you choose another time server? Is that the only DC >> in your 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 >>> Our W2K3 R2 64-bit DC has been up and running for some time, and >>> getting time updates regularly. >>> >>> Last week, it started a spate of failed attempts which have become >>> rather chronic. >>> >>> First, I followed advice to set the time source: >>> >>> w32tm /config /manualpeerlist:time.nist.gov,0x8 >>> /syncfromflags:MANUAL >>> net stop w32time >>> net start w32time >>> w32tm /resync >>> Had no luck. I verified that TCP & UDP ports 123 were available to >>> the server and tested successfully with: >>> w32tm /monitor /computers:time.nist.gov >>> >>> I also re-registered the service with: >>> >>> net stop w32time >>> w32tm /unregister >>> w32tm /register >>> net start w32time >>> Also to no avail. >>> I did find a hotfix related (830092), but it appears it is only for >>> the 32-bit version. >>> >>> Anything else I can try? >>>
|
|
05-02-2008, 06:47 PM
|
|||
|
|||
|
Re: NTPClient on DC fails to contact time source (W2K3 R2 64-bit)
Hrm. I have DC #1 which is trying to get the time externally. DC#2 is
looking to DC#1 for it's time. Prior to this arrangement, I had only one DC which was SBS2000. "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message news:ff16fb669837b8ca7a79a1fed540@msnews.microsoft .com... > Hello Dvord, > > It is the PDCEmulator where you are running the time server, i assume? Was > there another time server before? > > 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 apologize I didn't answer the second question. >> >> No it is not. I have two DC's. >> >> "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message >> news:ff16fb6697fea8ca78c4df225bb0@msnews.microsoft .com... >> >>> Hello Dvord, >>> >>> What happend, if you choose another time server? Is that the only DC >>> in your 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 >>>> Our W2K3 R2 64-bit DC has been up and running for some time, and >>>> getting time updates regularly. >>>> >>>> Last week, it started a spate of failed attempts which have become >>>> rather chronic. >>>> >>>> First, I followed advice to set the time source: >>>> >>>> w32tm /config /manualpeerlist:time.nist.gov,0x8 >>>> /syncfromflags:MANUAL >>>> net stop w32time >>>> net start w32time >>>> w32tm /resync >>>> Had no luck. I verified that TCP & UDP ports 123 were available to >>>> the server and tested successfully with: >>>> w32tm /monitor /computers:time.nist.gov >>>> >>>> I also re-registered the service with: >>>> >>>> net stop w32time >>>> w32tm /unregister >>>> w32tm /register >>>> net start w32time >>>> Also to no avail. >>>> I did find a hotfix related (830092), but it appears it is only for >>>> the 32-bit version. >>>> >>>> Anything else I can try? >>>> > >
|
|
05-02-2008, 07:31 PM
|
|||
|
|||
|
Re: NTPClient on DC fails to contact time source (W2K3 R2 64-bit)
Hello Dvord,
Make sure that DC1 is the PDCEmulator with netdom query /d:yourdomain.com fsmo 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 > Hrm. I have DC #1 which is trying to get the time externally. DC#2 > is looking to DC#1 for it's time. > > Prior to this arrangement, I had only one DC which was SBS2000. > > "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message > news:ff16fb669837b8ca7a79a1fed540@msnews.microsoft .com... > >> Hello Dvord, >> >> It is the PDCEmulator where you are running the time server, i >> assume? Was there another time server before? >> >> 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 apologize I didn't answer the second question. >>> >>> No it is not. I have two DC's. >>> >>> "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message >>> news:ff16fb6697fea8ca78c4df225bb0@msnews.microsoft .com... >>> >>>> Hello Dvord, >>>> >>>> What happend, if you choose another time server? Is that the only >>>> DC in your 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 >>>>> Our W2K3 R2 64-bit DC has been up and running for some time, and >>>>> getting time updates regularly. >>>>> >>>>> Last week, it started a spate of failed attempts which have become >>>>> rather chronic. >>>>> >>>>> First, I followed advice to set the time source: >>>>> >>>>> w32tm /config /manualpeerlist:time.nist.gov,0x8 >>>>> /syncfromflags:MANUAL >>>>> net stop w32time >>>>> net start w32time >>>>> w32tm /resync >>>>> Had no luck. I verified that TCP & UDP ports 123 were available >>>>> to >>>>> the server and tested successfully with: >>>>> w32tm /monitor /computers:time.nist.gov >>>>> I also re-registered the service with: >>>>> >>>>> net stop w32time >>>>> w32tm /unregister >>>>> w32tm /register >>>>> net start w32time >>>>> Also to no avail. >>>>> I did find a hotfix related (830092), but it appears it is only >>>>> for >>>>> the 32-bit version. >>>>> Anything else I can try? >>>>>
|
|
05-02-2008, 07:50 PM
|
|||
|
|||
|
Re: NTPClient on DC fails to contact time source (W2K3 R2 64-bit)
Yes looks like it is:
C:\Documents and Settings\...>netdom query /d:domain.com fsmo Schema owner DC1.domain.COM Domain role owner DC1.domain.COM PDC role DC1.domain.COM RID pool manager DC1.domain.COM Infrastructure owner DC1.domain.COM The command completed successfully. "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message news:ff16fb66984248ca7aaa9bf6ae80@msnews.microsoft .com... > Hello Dvord, > > Make sure that DC1 is the PDCEmulator with netdom query /d:yourdomain.com > fsmo > > 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 > >> Hrm. I have DC #1 which is trying to get the time externally. DC#2 >> is looking to DC#1 for it's time. >> >> Prior to this arrangement, I had only one DC which was SBS2000. >> >> "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message >> news:ff16fb669837b8ca7a79a1fed540@msnews.microsoft .com... >> >>> Hello Dvord, >>> >>> It is the PDCEmulator where you are running the time server, i >>> assume? Was there another time server before? >>> >>> 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 apologize I didn't answer the second question. >>>> >>>> No it is not. I have two DC's. >>>> >>>> "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message >>>> news:ff16fb6697fea8ca78c4df225bb0@msnews.microsoft .com... >>>> >>>>> Hello Dvord, >>>>> >>>>> What happend, if you choose another time server? Is that the only >>>>> DC in your 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 >>>>>> Our W2K3 R2 64-bit DC has been up and running for some time, and >>>>>> getting time updates regularly. >>>>>> >>>>>> Last week, it started a spate of failed attempts which have become >>>>>> rather chronic. >>>>>> >>>>>> First, I followed advice to set the time source: >>>>>> >>>>>> w32tm /config /manualpeerlist:time.nist.gov,0x8 >>>>>> /syncfromflags:MANUAL >>>>>> net stop w32time >>>>>> net start w32time >>>>>> w32tm /resync >>>>>> Had no luck. I verified that TCP & UDP ports 123 were available >>>>>> to >>>>>> the server and tested successfully with: >>>>>> w32tm /monitor /computers:time.nist.gov >>>>>> I also re-registered the service with: >>>>>> >>>>>> net stop w32time >>>>>> w32tm /unregister >>>>>> w32tm /register >>>>>> net start w32time >>>>>> Also to no avail. >>>>>> I did find a hotfix related (830092), but it appears it is only >>>>>> for >>>>>> the 32-bit version. >>>>>> Anything else I can try? >>>>>> > >
|
|
05-06-2008, 06:53 PM
|
|||
|
|||
|
Re: NTPClient on DC fails to contact time source (W2K3 R2 64-bit)
*BUMP*
"Dvord Direwood" <dvord@hotmail.com> wrote in message news:O5fXrUIrIHA.5580@TK2MSFTNGP04.phx.gbl... > Yes looks like it is: > > C:\Documents and Settings\...>netdom query /d:domain.com fsmo > > Schema owner DC1.domain.COM > > Domain role owner DC1.domain.COM > > PDC role DC1.domain.COM > > RID pool manager DC1.domain.COM > > Infrastructure owner DC1.domain.COM > > The command completed successfully. > > > "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message > news:ff16fb66984248ca7aaa9bf6ae80@msnews.microsoft .com... >> Hello Dvord, >> >> Make sure that DC1 is the PDCEmulator with netdom query /d:yourdomain.com >> fsmo >> >> 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 >> >>> Hrm. I have DC #1 which is trying to get the time externally. DC#2 >>> is looking to DC#1 for it's time. >>> >>> Prior to this arrangement, I had only one DC which was SBS2000. >>> >>> "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message >>> news:ff16fb669837b8ca7a79a1fed540@msnews.microsoft .com... >>> >>>> Hello Dvord, >>>> >>>> It is the PDCEmulator where you are running the time server, i >>>> assume? Was there another time server before? >>>> >>>> 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 apologize I didn't answer the second question. >>>>> >>>>> No it is not. I have two DC's. >>>>> >>>>> "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message >>>>> news:ff16fb6697fea8ca78c4df225bb0@msnews.microsoft .com... >>>>> >>>>>> Hello Dvord, >>>>>> >>>>>> What happend, if you choose another time server? Is that the only >>>>>> DC in your 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 >>>>>>> Our W2K3 R2 64-bit DC has been up and running for some time, and >>>>>>> getting time updates regularly. >>>>>>> >>>>>>> Last week, it started a spate of failed attempts which have become >>>>>>> rather chronic. >>>>>>> >>>>>>> First, I followed advice to set the time source: >>>>>>> >>>>>>> w32tm /config /manualpeerlist:time.nist.gov,0x8 >>>>>>> /syncfromflags:MANUAL >>>>>>> net stop w32time >>>>>>> net start w32time >>>>>>> w32tm /resync >>>>>>> Had no luck. I verified that TCP & UDP ports 123 were available >>>>>>> to >>>>>>> the server and tested successfully with: >>>>>>> w32tm /monitor /computers:time.nist.gov >>>>>>> I also re-registered the service with: >>>>>>> >>>>>>> net stop w32time >>>>>>> w32tm /unregister >>>>>>> w32tm /register >>>>>>> net start w32time >>>>>>> Also to no avail. >>>>>>> I did find a hotfix related (830092), but it appears it is only >>>>>>> for >>>>>>> the 32-bit version. >>>>>>> Anything else I can try? >>>>>>> >> >> > >
|
|
|
| Thread Tools | Search this Thread |
| Display Modes | |
|
|
Linear Mode
