This "tip" seems to describe horrid internet manners.
To quote:
"In addition, make sure that all of your clients' time properties are
configured properly."
This article already makes the mistake of telling the readership that every server ontheir network should sync directly against a NIST time source.
The quoted section then componds this error by impling that every client should also point to a NIST source.
If the advice in this "tip" is followed, we will soon see that the various public agency reliable time-sources will be so swamped with requests that they will be as overloaded & useless as microsoft's time.microsoft.com.
Who checks these "tips"!
First off, setting through the clock is NOT the correct method, and there should only be one device per site (or maybe one per connection if you have multiple pipes to the internet) that touches a reliable time source.
Each server and client in an organization should then point to the local server at it's time source.
Additionaly in Win2000 and Win2003 you should use a list of timesources so that there is some failover.
The correct basic method of configuring your local NTP Win2000/2003 server to query an external timesource is with:
Net time /setsntp:"xxx.xxx.xxx.xxx yyy.yyy.yyy.yyy zzz.zzz.zzz.zzz"
Where the xxx/yyy/zzz is the ip address of level 2, level 2, level 1 timesource.
More advanced time source configuration can be done by using (in Win2003) w32tm command (w32tm /? for options).