Well it was synchronizing with time.windows.com, but still was 1 hour behind. Tried asia.pool.ntp.org, and still the same, brought me an hour back.
In the end i run net time /setsntp:enigma where enigma is the name of the server, and now it works. In my opinion, since i don't think a time server is running on that server, windows just leaves the time as is, who knows, anyway problem is fixed...

Jaime

>>Hi all
>>I have a SBS2003 machine which is the domain controller. All workstations synchronize time with that machine (using net time \\myserver /set ). My problem is the main server is 1 hour behind, and when i locally fix the time it gets back to the wrong one after a few minutes. What gives?
>
>As Ric points out it's probably a timezone or daylight savings time issue. First, check that those are set correctly.
>
>Then, at a CMD prompt on the server check the NTP time source(s):
>

>NET TIME /QUERYSNTP
>NET TIME /SETSNTP
>
>for help, type NET HELP TIME
>

>Windows servers default to time.windows.com as their NTP time server. Outside of North America you may have better luck with the NTP Pool: http://www.pool.ntp.org/ That link has good general information, and explains how to use it from Windows or other OSs.
>
>One esoteric problem I ran into was a case where the Internet router on one network was configured to intercept outgoing NTP requests and respond using its own internal time. While the router had its own NTP client and was configured to get accurate time from a time server, its firmware was old and didn't properly account for the date change for daylight savings time start/finish here in North America. So, for several weeks in the spring and fall, time would be off by an hour.