Time Servers
|
From: Gary J. Dikkema on 5 Mar 2007 16:05 Yes, those settings are back at default. The .bat file was the one posted by Les that is supposed to correct these sort of things. I am going to prep a new virtual R2 box unless you have some other suggestions <VBG>. Thanks so much for the help; I know troubleshooting can be a delicate long running task at times. Regards! "kj" <kj(a)nowhere.com> wrote in message news:ebZdqh2XHHA.1244(a)TK2MSFTNGP04.phx.gbl... > Gary J. Dikkema wrote: >> Did those, ran the .bat file; saw the time get set correctly and then >> a few secs later revert to the +3 to +4 minutes head.... >> >> Strange! >> >> FWIW, ran that same hotfix on my backup R2 box and it failed... > > You changed the registry settings back to default and ran a bat file > previously posted? ( I'm confused) > > Are the reg settings still at default or back to the ones you had > originally? > > ... ah, the DNS hotfix? > > -- > /kj >
From: kj on 5 Mar 2007 16:27 Gary J. Dikkema wrote: > Yes, those settings are back at default. > > The .bat file was the one posted by Les that is supposed to correct > these sort of things. > > I am going to prep a new virtual R2 box unless you have some other > suggestions <VBG>. > > Thanks so much for the help; I know troubleshooting can be a delicate > long running task at times. > > Regards! > Well I hope there are other reasons to be rebuilding. Seems like something else is at work changing the time, maybe one of those "net time /set" bat files at work somewhere. try a; net time /querysntp you should get; "This computer is not currently configured to use a specific SNTP server." Three to four minutes is an awfull amount of difference for reliable time sources. It acts as if it's configured for a hardware (cmos) clock as the reliable time source. -- /kj
From: Gary J. Dikkema on 6 Mar 2007 15:41 i get the current sntp value is: time.windows.com,0x8 small domains can be easily rebuilt overnight; all that leaves is just reconnecting machines, userids and the mail store files. however, i would like to get to the bottom of this. "kj" <kj(a)nowhere.com> wrote in message news:O%2370a02XHHA.4560(a)TK2MSFTNGP03.phx.gbl... > Gary J. Dikkema wrote: >> Yes, those settings are back at default. >> >> The .bat file was the one posted by Les that is supposed to correct >> these sort of things. >> >> I am going to prep a new virtual R2 box unless you have some other >> suggestions <VBG>. >> >> Thanks so much for the help; I know troubleshooting can be a delicate >> long running task at times. >> >> Regards! >> > > Well I hope there are other reasons to be rebuilding. Seems like something > else is at work changing the time, maybe one of those "net time /set" bat > files at work somewhere. > > try a; > > net time /querysntp > > you should get; > > "This computer is not currently configured to use a specific SNTP server." > > Three to four minutes is an awfull amount of difference for reliable time > sources. It acts as if it's configured for a hardware (cmos) clock as the > reliable time source. > > -- > /kj >
From: Gary J. Dikkema on 9 Mar 2007 13:38 By way of follow up, I rebuilt the virtual machine on my Test box, migrated it back to the Prod box and am running STRONGER than ever with the right time. FWIW, I built the machine in VPC2007, and am running that on my X64 WXP and I must say it's using LESS ram than when I used to run it in VS2005 R2 B2... Thanks to those who offfered all of their time to help me resolve this. Regards! "Gary J. Dikkema" <gary_d-no-spam-(a)cdir.ca> wrote in message news:etjna9CYHHA.4000(a)TK2MSFTNGP02.phx.gbl... >i get the current sntp value is: time.windows.com,0x8 > > small domains can be easily rebuilt overnight; all that leaves is just > reconnecting machines, userids and the mail store files. > > however, i would like to get to the bottom of this. > > > "kj" <kj(a)nowhere.com> wrote in message > news:O%2370a02XHHA.4560(a)TK2MSFTNGP03.phx.gbl... >> Gary J. Dikkema wrote: >>> Yes, those settings are back at default. >>> >>> The .bat file was the one posted by Les that is supposed to correct >>> these sort of things. >>> >>> I am going to prep a new virtual R2 box unless you have some other >>> suggestions <VBG>. >>> >>> Thanks so much for the help; I know troubleshooting can be a delicate >>> long running task at times. >>> >>> Regards! >>> >> >> Well I hope there are other reasons to be rebuilding. Seems like >> something else is at work changing the time, maybe one of those "net time >> /set" bat files at work somewhere. >> >> try a; >> >> net time /querysntp >> >> you should get; >> >> "This computer is not currently configured to use a specific SNTP >> server." >> >> Three to four minutes is an awfull amount of difference for reliable time >> sources. It acts as if it's configured for a hardware (cmos) clock as the >> reliable time source. >> >> -- >> /kj >> > >
From: kj on 9 Mar 2007 13:49
Gary J. Dikkema wrote: > By way of follow up, I rebuilt the virtual machine on my Test box, > migrated it back to the Prod box and am running STRONGER than ever > with the right time. > > FWIW, I built the machine in VPC2007, and am running that on my X64 > WXP and I must say it's using LESS ram than when I used to run it in > VS2005 R2 B2... > Thanks to those who offfered all of their time to help me resolve > this. > Regards! > VS2005 R2 has issues with Windows 2003 SP1 Guest OSs, but I don't recall it being a memory problem. The imminent release of VS2005 R2 SP1 should fix that problem though. I gotta say, I do like VPC2007 for many VM needs (especially on X64). Thanks for the update! -- /kj |