Windows Server time off by one minute exactly

Yes, SV1 is a domain controller.
I will read through those links you've posted.

In the Event Viewer, there was nothing in the way of an "error" or "information" or anything that looked bad regarding time syncing.  The only indication of anything "time-related" was with W32Time on SV2, but that was a month ago was realted to a network outage here.  SV1, as expected, showed no events regarding time syncing.

thanks.

Important to note --

SV2 is the only machine on our network that is Server 2003, and it is the only machine that seems to have this problem.  All workstations (XP, W7) sync to SV1 and do not have this issue.

Also, I am told by our network guy here that SV2 is actually syncing it's time with SV1 every 5 minutes (in an effort to fix this problem).  It's been set like that for a week, yet the problem occured this morning again -- AND -- the problem persisted through many 5-minute cycles.

We are assuming that the syncing happened many times, yet stayed exactly 60 seconds off-sync with the domain controller SV1.

Update:  
Turns out, we have not one but two servers that are running Windows Server 2003 (SV2 and SV3).  Both of their clocks are off by 60 seconds.  Both sync their clocks with the domain controller SV1 (Server 2008R2).  SV2 is an exchange server, SV3 is a file server.  

All our other serves are Windows 2008 R2, and all of them are synced perfectly.

Did you run the command within the link I posted

From the Event Viewer, we can tell that the "bad" server is trying to sync with the proper domain controller SV1, so that's good.

So, we ran:

    w32tm /config /syncfromflags:domhier /update
    net stop w32time
    net start w32time

A clue may be that then we run:
    w32tm /resync /rediscover
it does not do anything -- the clock remains un-synced. So, we fiddled with a registry settings for w32time and got that command to work.  However, that is something that we have to manually execute.

The big question is "why i it happening?"  -- One (or many) of our servers get exactly 60 off-sync with the domain controller SV1 ---  Why would that happen?

A key point here is that the 60-second offset happens only on servers running Server 2003.  The domain controller is Server 2008.

Are you running in any virtual environment by chance?

No, no virtual environments.  Everything here is pretty standard stuff.

Today we've been looking at event logs, etc.  We have not been able to figure out any sort of pattern as to "when" the servers get 60 seconds off-sync.  All workstations stay in sync, so we are still focusing on the Windows 2003 Servers.

One of the 2003 Servers is a VPN machine, and serves no other function.  (on top of that, it's never really VPN'd into).  The other 2003 Server is running IIS7 to run an intranet app we have here.
Both servers those were out-of-sync by 60 seconds when we checked them, but we can not tell if they became out-of-sync simultanously.

hi.  Yes, we were using the "w32tm /monitor" command.  Since this is happening on production servers, we had to "drop back and punt" as they say -- we are now syncing the time on the Win2003 servers with the Win2008 domain server every 5 minutes, in an effort to keep everything in syns.  Why it's happening only on the Win2003 servers is a mystery.

We have given up -- it seems to be a bug in 2003, although there must be something unique here, since i assume everyone is suffering from this same problem.  We are moving to 2008 or 2012 soon, so maybe this will go away.