Depending on what type of PC this is will depend on how to get into the CMOS, most common is during boot, right after the POST test start tapping the *DELETE* button, if this does not then let us know what typ of computer (ie: Dell, Compaq) or if its "home made" then advise what the motherboard is.
Also whaen you are with in Windows you can change the clock by "double clicking" on the time in the System Tray.
If after you do either step and your clock does not keep time then 1) the CMOS battery is not retaining a charge, replace it; 2) check for viruses, trojans etc...
Time synchronisation is crucial within a domain so that everything that is going on can be kept in sync. But as long as time is synchronised to some central point (i.e. your server) you should be okay even if that time drifts a little. So you might have one of two issues here:
1) Check whether the time on your server clock drifts badly during the course of a day. If it does, you need some sort of external clock. You can get hardware clocks or you could time sync from an internet time source
2) If your server clock doesn't drift then check whether your time service (think its w32tm or something similar) is running and properly configured on your server and clients. You can check on the clients by the command 'net time' which should report the time seen at your server if they are talking to eachother okay
i do appreciate your reply. the problem is that at initial logon everything is okay, i can access the server using the "net time" command which as you said displays the time on the server. after a while i just can not get the command to work again, it keeps giving me this error code :