Re: Problem with w32time service
From: Kerry Hoskin (kjho_at_pml.ac.uk)
Date: 03/01/04
- Next message: Robin Ball: "Win98 clients"
- Previous message: MichaelS: "Problem with w32time service"
- In reply to: MichaelS: "Problem with w32time service"
- Next in thread: JDTHREE [MVP]: "Re: Problem with w32time service"
- Reply: JDTHREE [MVP]: "Re: Problem with w32time service"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 1 Mar 2004 09:19:28 -0000
Try MS 830092 W32Time frequently logs Event ID 50 and cannot update the
system clock in Windows Server 2003
worked for us
Kerry
"MichaelS" <subscription@swetech.co.il> wrote in message
news:u$XRb22$DHA.2336@TK2MSFTNGP11.phx.gbl...
> Hi,
> We are trying to use the default domain heirarcy for windows time service
on
> about 70 w3k servers in a domain. The synchronization is not working well
> though. We often get error 50 in the event log and if we restart the time
> service it will try to resynch again and it looks like it works, but only
> for a short time. We have also tried to use the command w32tm /monitor
> /computers: (computername) but we always get NTP timeout no response from
> server. If someone have tried this and could give us some details on what
to
> check for we would appreciate that.
>
>
- Next message: Robin Ball: "Win98 clients"
- Previous message: MichaelS: "Problem with w32time service"
- In reply to: MichaelS: "Problem with w32time service"
- Next in thread: JDTHREE [MVP]: "Re: Problem with w32time service"
- Reply: JDTHREE [MVP]: "Re: Problem with w32time service"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
