Prev: ESENT Event ID 467
Next: Limit User Access within a time frame
From: Les Connor [SBS MVP] on 10 Mar 2007 12:52
Somehow, I missed that this was a virtual machine. I believe there are some
known errors with time sync and VMs in general - but they're all
resolveable.

--
Les Connor [SBS MVP]


"Gary J. Dikkema" <gary_d-no-spam-(a)cdir.ca> wrote in message
news:eFomgonYHHA.596(a)TK2MSFTNGP06.phx.gbl...
> 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
>>>
>>
>>
>
>

First  |  Prev  | 
Pages: 1 2 3 4 5 6 7
Prev: ESENT Event ID 467
Next: Limit User Access within a time frame