Please ignore - PSS have found a resolution for this.

Cheers,
Katherine

"Katherine Coombs" <katherine_coombsREMOVE@THISbigpond.com> wrote in message
news:...

Can you share the solution with us?

Thanks
Ninon

"Katherine Coombs" <katherine_coombsREMOVE@THISbigpond.com> wrote in message
news:O2qtSrpfEHA.4092@TK2MSFTNGP10.phx.gbl...

See tip 8266 in the 'Tips & Tricks' at http://www.jsiinc.com

On Tue, 10 Aug 2004 09:19:14 -0400, "Ninon Chassé" <nchasse33@NoSpamhotmail.com>
wrote:


Jerold Schulman
Windows: General MVP
JSI, Inc.
http://www.jsiinc.com

Jerold,

That tip is KB 816042, which didn't work as per my original post. PSS have
acknowledged that implementing that solution in their test environment
caused them problems, too, so I'm confident that it wasn't just my system.

In the end, I did as follows:

On Domain Controller:
-ran w32tm /register - set time values to default
-ran w32tm /config /reliable:yes - sets announceflags to 5 in the registry.

-Set Enabled to 0 (No) in the following registry path -
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\W32Time\TimeProviders\N
tpClient This entry indicates if the NtpClient provider is enabled in
the current Time Service.

-ran w32tm /config /update

-Stopped and started w32time service.

Result: No events logged on DC.



On clients and member servers:

Stopped and started w32time service on client.

Result: Event ID 35 logged (indicating that the time is synchronising)



It's been a day now and still no problems, so this solution appears to have
fixed my problems and should work in similar environment.



Hope this helps,

Katherine

"Jerold Schulman" <Jerry@jsiinc.com> wrote in message
news:qcmhh0toqbhupn2jq5sddienti1fdbqv7l@4ax.com...

Thank you Katherine!

Ninon

"Katherine Coombs" <katherine_coombsREMOVE@THISbigpond.com> wrote in message
news:u%23olg0zfEHA.3192@tk2msftngp13.phx.gbl...