Event ID 62 info

Event ID 62 info

Post by Steve Eclips » Fri, 09 Nov 2001 01:37:13



Source: w32time
Description:
This Machine is a PDC of the domain art the root of the forest. (Yes, I know
that). Configure to sync from External time source using the net command,
'net time /setsntp: <server name>'. (I have no idea where to Externally sync
for the correct time. We use a dialup connection for access to the web. Can
this be configured this way, or can I sync from another PC on the network?

STEVE

 
 
 

Event ID 62 info

Post by Jen » Fri, 09 Nov 2001 09:45:08


Use net time command.

net time /setsntp:ntp2.usno.navy.mil

net time /set

Then reboot and check if you have that event error again.


Quote:> Source: w32time
> Description:
> This Machine is a PDC of the domain art the root of the forest. (Yes, I
know
> that). Configure to sync from External time source using the net command,
> 'net time /setsntp: <server name>'. (I have no idea where to Externally
sync
> for the correct time. We use a dialup connection for access to the web.
Can
> this be configured this way, or can I sync from another PC on the network?

> STEVE


 
 
 

Event ID 62 info

Post by Michael Holzeme » Fri, 09 Nov 2001 17:10:30


This is from a previous post in another ng. Dial up and run the
w32tm -once -v command
Post follows

********************************************************

This is a bit confusing.  The Net Time command has two functions:

 1.  get time from a time source using the Windows native time service,
which is NetBIOS based and is available on Windows NT and Windows 2000
computers (e.g. net time \\computername [/set] [/yes]).

  2. configure the time source for the Windows 2000 NTP based time service
(e.g. net time /setsntp:DNS name or IP address).

These two functions are not related and do not interact.

To test an NTP time source, use the w32tm command:.

  w32tm -once -v

will attempt to get the time from the currently configured NTP time source.
The -v option produces a trace, which you can use to see what source is
being queried and whether it worked or not.

There is no such thing as listening for updates when it comes to the NTP
protocol.  The time source responds to time queries, but does not push time
updates.  The Windows time service will query its time source every so often
(at startup and about twice per day afterwards).

Windows 2000 member computers in a Windows 2000 domain should not have any
time source manually specified.  Instead, they should be configured to
automatically use one of the domain controllers as a time source.  To remove
any previously configured time source, issue the command:

     net time /setsntp:

Then, the time service will get time from a domain controller (as Michael
says).  As far as I'm aware, Michael is correct about the time hierarchy in
a Windows 2000 Domain.

I don't think having a mixed as opposed to native mode Windows 2000 domain
make any difference to how the time synchronisation works for Windows 2000
computers.

--
Bruce Sanderson (242600)

It is perfectly useless to know the right answer to the wrong question.
***********************************************************************
--
Regards,

Mike Holzemer
No email replies please - reply in newsgroup

> Use net time command.

> net time /setsntp:ntp2.usno.navy.mil

> net time /set

> Then reboot and check if you have that event error again.



> > Source: w32time
> > Description:
> > This Machine is a PDC of the domain art the root of the forest. (Yes, I
> know
> > that). Configure to sync from External time source using the net
command,
> > 'net time /setsntp: <server name>'. (I have no idea where to Externally
> sync
> > for the correct time. We use a dialup connection for access to the web.
> Can
> > this be configured this way, or can I sync from another PC on the
network?

> > STEVE

 
 
 

Event ID 62 info

Post by Steve Eclips » Wed, 14 Nov 2001 01:25:23


Thanks to all for the information.

Steve


> This is from a previous post in another ng. Dial up and run the
> w32tm -once -v command
> Post follows

> ********************************************************

> This is a bit confusing.  The Net Time command has two functions:

>  1.  get time from a time source using the Windows native time service,
> which is NetBIOS based and is available on Windows NT and Windows 2000
> computers (e.g. net time \\computername [/set] [/yes]).

>   2. configure the time source for the Windows 2000 NTP based time service
> (e.g. net time /setsntp:DNS name or IP address).

> These two functions are not related and do not interact.

> To test an NTP time source, use the w32tm command:.

>   w32tm -once -v

> will attempt to get the time from the currently configured NTP time
source.
> The -v option produces a trace, which you can use to see what source is
> being queried and whether it worked or not.

> There is no such thing as listening for updates when it comes to the NTP
> protocol.  The time source responds to time queries, but does not push
time
> updates.  The Windows time service will query its time source every so
often
> (at startup and about twice per day afterwards).

> Windows 2000 member computers in a Windows 2000 domain should not have any
> time source manually specified.  Instead, they should be configured to
> automatically use one of the domain controllers as a time source.  To
remove
> any previously configured time source, issue the command:

>      net time /setsntp:

> Then, the time service will get time from a domain controller (as Michael
> says).  As far as I'm aware, Michael is correct about the time hierarchy
in
> a Windows 2000 Domain.

> I don't think having a mixed as opposed to native mode Windows 2000 domain
> make any difference to how the time synchronisation works for Windows 2000
> computers.

> --
> Bruce Sanderson (242600)

> It is perfectly useless to know the right answer to the wrong question.
> ***********************************************************************
> --
> Regards,

> Mike Holzemer
> No email replies please - reply in newsgroup


> > Use net time command.

> > net time /setsntp:ntp2.usno.navy.mil

> > net time /set

> > Then reboot and check if you have that event error again.



> > > Source: w32time
> > > Description:
> > > This Machine is a PDC of the domain art the root of the forest. (Yes,
I
> > know
> > > that). Configure to sync from External time source using the net
> command,
> > > 'net time /setsntp: <server name>'. (I have no idea where to
Externally
> > sync
> > > for the correct time. We use a dialup connection for access to the
web.
> > Can
> > > this be configured this way, or can I sync from another PC on the
> network?

> > > STEVE

 
 
 

1. Event ID 64 Win32time warning and Event ID 62 Win32time Error

Hello,

Event ID 64 Win32time warning and Event ID 62 Win32time Error

Has anyone seen this problem and know how to correct this?

Here is the event log

Event Type: Warning
Event Source: w32time
Event Category: None
Event ID: 64
Date:  4/17/2001
Time:  3:16:07 AM
User:  N/A
Computer: SERVER
Description:
Because of repeated network problems, the time service has not been able to
find a domain controller to synchronize with for a long time. To reduce
network traffic, the time service will wait 960 minutes before trying again.
No synchronization will take place during this interval, even if network
connectivity is restored. Accumulated time errors may cause certain network
operations to fail. To tell the time service that network connectivity has
been restored and that it should resynchronize, execute "w32tm /s" from the
command line.
Data:
0000: e5 03 00 00               ?...

Event Type: Error
Event Source: w32time
Event Category: None
Event ID: 62
Date:  4/17/2001
Time:  3:16:07 AM
User:  N/A
Computer: SERVER
Description:
This Machine is a PDC of the domain at the root of the forest. Configure to
sync from External time source using the net command,  'net time
/setsntp:<server name>'.
Data:
0000: e5 03 00 00               ?...

--
Chris Cerrito

generic levitra india

2. RE-Writable CD questions

3. event source w32time event id 62 & 64

4. harsh problem with logon

5. Event ID 62 in System Event Log

6. e310

7. What's a A1000 worth?

8. Event id 62 w32time

9. Event IDs: 1051, 62, 3113, 105

10. Event ID: 62

11. w32time event id 62 & 64

12. Event ID 62