NTP

[Guest]

Dear, Microsoft Coporation Inc.

Does the Microsoft Corproation's Windows XP Professional operating
system utilize coordinated universal time (UTC), UDP, TCP, NTP in a cohesive
to maintain time or is it a combination of all these items and associated
ethemeral ports?

Very Respectfully
Mr. Garrett Hord
Microsoft Research Panelist
CompTIA Research Panelist

http://www.securitytalks.com

 

[Bob I]

You aren't addressing Microsoft, this is a peer to peer user newsgroup.

 

[Tim Slattery]

Dear, Microsoft Coporation Inc.

Does the Microsoft Corproation's Windows XP Professional operating
system utilize coordinated universal time (UTC), UDP, TCP, NTP in a cohesive
to maintain time or is it a combination of all these items and associated
ethemeral ports?

Huh??

Windows XP has a built-in NTP client. It uses the standard,
RFC-specified NTP protocol to get the correct time from an NTP server
of your choice and keep its internal clock accurate. NTP sends the
time as UTC, your computer then translates that to your time zone.

 

[G.T.]

Huh??

Windows XP has a built-in NTP client. It uses the standard,
RFC-specified NTP protocol to get the correct time from an NTP server
of your choice and keep its internal clock accurate. NTP sends the
time as UTC, your computer then translates that to your time zone.

It does not use NTP to keep the clock in sync, it grabs the correct time on
bootup or periodically (weekly?) but it does not keep the clock synced to an
NTP server.

Greg

 

[Guest]

Dear, Forum

Iwant to first thank you all for helping me with this question.
Secondly, what I am really trying to figure out is how the NTP server
fault-tolerant in relation towards time accuracy. I do know that the NTP
server is or maybe based on the actual ICMP timestamp and the NTP server
denotes an actual primary server for the time to slave the entire network or
is it based solely on the ISN begginng segment number of a particular SA and
or session itself?

Very Respectfully
Mr. Garrett Hord
Microsoft Research Panelist
CompTIA Corproation Research Panelist
http://www.securitytalks.com

 

[G.T.]

Dear, Forum

Iwant to first thank you all for helping me with this question.

Why is there so much freakin' top-posting here?

Secondly, what I am really trying to figure out is how the NTP server
fault-tolerant in relation towards time accuracy.

Which NTP server? XP doesn't have a NTP server, it has a very simple
client.

I do know that the NTP
server is or maybe based on the actual ICMP timestamp and the NTP server
denotes an actual primary server for the time to slave the entire network or
is it based solely on the ISN begginng segment number of a particular SA and
or session itself?

What does this have to do with XP?

Try man ntp on a UNIX box.

Greg

 

[Tim Slattery]

It does not use NTP to keep the clock in sync, it grabs the correct time on
bootup or periodically (weekly?) but it does not keep the clock synced to an
NTP server.

I beg to differ. It does indeed grab the correct time every week (by
default, I believe). It certainly does use NTP to do that.

 

[Tim Slattery]

Why is there so much freakin' top-posting here?

Ugh...Because this is an MS forum, and most people use OE to post, and
it does that by default.

Try man ntp on a UNIX box.

Or read the RFC that describes the protocol at
http://www.faqs.org/rfcs/rfc1305.html

I expect the accuracy of the time given would depend on the clock
attached to the computer. The Naval Observatory, NIST, and a few
others maintain primary time standards (atomic clocks), which are
incredibly accurate. There are many secondary standards, which have
very accurate clocks and which synchronize frequently with a primary
standard, and are more than accurate enough for normal computer users.

 

[Guest]

Dear, Mr. Tim Slattery

THank you for all of your support in this endeavor of continuing
professioonal development for myself.

Very Respectfully

 

[G.T.]

I beg to differ. It does indeed grab the correct time every week (by
default, I believe). It certainly does use NTP to do that.

That's just a periodic scheduling of the simple NTP client. XP is not
running an NTP daemon which keeps the clock constantly in sync with it's
pool of NTP servers. It may be semantics but that's a huge difference
in functionality, i.e. running the NTP client once a week versus an NTP
daemon running 100% of the time.

Greg

 

[G.T.]

Ugh...Because this is an MS forum, and most people use OE to post, and
it does that by default.

So? Check the headers on my previous post, not this one.

Or read the RFC that describes the protocol at
http://www.faqs.org/rfcs/rfc1305.html

I expect the accuracy of the time given would depend on the clock
attached to the computer. The Naval Observatory, NIST, and a few
others maintain primary time standards (atomic clocks), which are
incredibly accurate. There are many secondary standards, which have
very accurate clocks and which synchronize frequently with a primary
standard, and are more than accurate enough for normal computer users.

Or hook up your NMEA GPS device to a computer running ntpd:

http://www.openbsd.org/cgi-bin/man....manpath=OpenBSD+Current&arch=i386&format=html

I played with this for awhile but I was using the GPS I use for mtn
biking and hiking so I took it down.

Greg

 

[Tim Slattery]

That's just a periodic scheduling of the simple NTP client. XP is not
running an NTP daemon which keeps the clock constantly in sync with it's
pool of NTP servers.

Yes, I agree. It uses a simple NTP client, it does use the NTP
protocol once a week (unless you've messed with the registry). It does
not run an NTP server - unless you install one - or anything more
complex.

 

[G.T.]

Yes, I agree. It uses a simple NTP client, it does use the NTP
protocol once a week (unless you've messed with the registry). It does
not run an NTP server - unless you install one - or anything more
complex.

Just to be clear here running an NTP daemon does not necessarily mean that
one is running an NTP server. The NTP daemon is used for keeping a client
constantly in sync with an NTP server or pool of servers and the config is
just as simple as setting the time server in XP's Date and Time Properties.
In addition to running as a client it can also be used for serving up the
time to other servers and/or clients.

Once a week or even once a day is not adequate to keep a PC with a bad clock
in decent time.

Greg