locked
Windows Clock become running slow RRS feed

  • 問題

  • We have several clients occur the same problems. They are using Windows 2003 R2 SP2 32bit Chinese version. We found that the server windows clock will be slower in every day. However, their server will not connect to Internet for security issue, so they now need to adjust the time manually. We have found IBM for checking any hardware problem occur, and no problem found in hardware. IBM engineer also said their internal server also has the same problem.

     

    So do we only can adjust the clock manually everyday to solve the problem? Any document in Microsoft.com related the above problem?

    2009年1月22日 上午 02:38

解答

  • Dear Customer,

     

    Thank you for your post.

     

    Analysis:

    =============

     

    1. In a Windows 2000/2003 forest, time is synchronized in the following manner

     

    - The primary domain controller (PDC) emulator operations master in the forest root domain is the authoritative time source for the organization;

     

    - All PDC operation masters in other domains in the forest follow the hierarchy of domains when selecting a PDC emulator to synchronize their time. The PDC in the child domain can synchronize the time with any DC from Parent domain;

     

    - All client desktop computers nominate the authenticating domain controller as their in-bound time partner. Domain controllers with different FSMO roles and in different Sites have different proprieties;

     

    - All member servers follow the same process as client desktop computers;

     

    - Domain controllers may nominate the primary domain controller (PDC) operations master as their in-bound time partner but may also use a parent domain controller based on stratum numbering.

     

    2. Therefore, the client should contact its logon server for time synchronization, which should be a local DC if everything works.

     

    To better address this issue, may I know how you notice the problem? Is it from an event log error, or a command result? Please send me a screen shot if necessary.

     

    More Reference:

    ==================

     

    How Windows Time Service Works

    http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/techref/en-us/w2k3tr_times_how.asp

     

    Using Windows Server 2003 in a Managed Environment

    Windows Time Service

    http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/security/ws03mngd/26_s3wts.mspx

     

    Windows 2000 Time Service Whitepaper

    http://www.microsoft.com/windows2000/docs/wintimeserv.doc

     

    I look forward to your reply. Also, if you have any questions or concerns, please do not hesitate to let me know. I am happy to help. :-)

     

    Thank you for your time and cooperation!

     

    Sincerely,

    Tom Zhang

     

    2009年1月22日 上午 09:07
    版主

所有回覆

  • Hi Nick,

    Have you asked IBM to check the battery on your server's motherboard?
    Sometime it could cause by the motherboard's memory.
    E.g. You can try to switch on the server and go to BIOS and see if the time in BIOS is wrong as well.

    As they will not connect to Internet for security issue, so I do not think they want to install some software which can connect to Internet and synchronize the Clock.

    If you want more information about Slow Computer Clock, please have a look at the URL below
    http://www.pcnineoneone.com/howto/slowclock.html

    Hope this can help.
    2009年1月22日 上午 08:39
  • Dear Customer,

     

    Thank you for your post.

     

    Analysis:

    =============

     

    1. In a Windows 2000/2003 forest, time is synchronized in the following manner

     

    - The primary domain controller (PDC) emulator operations master in the forest root domain is the authoritative time source for the organization;

     

    - All PDC operation masters in other domains in the forest follow the hierarchy of domains when selecting a PDC emulator to synchronize their time. The PDC in the child domain can synchronize the time with any DC from Parent domain;

     

    - All client desktop computers nominate the authenticating domain controller as their in-bound time partner. Domain controllers with different FSMO roles and in different Sites have different proprieties;

     

    - All member servers follow the same process as client desktop computers;

     

    - Domain controllers may nominate the primary domain controller (PDC) operations master as their in-bound time partner but may also use a parent domain controller based on stratum numbering.

     

    2. Therefore, the client should contact its logon server for time synchronization, which should be a local DC if everything works.

     

    To better address this issue, may I know how you notice the problem? Is it from an event log error, or a command result? Please send me a screen shot if necessary.

     

    More Reference:

    ==================

     

    How Windows Time Service Works

    http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/techref/en-us/w2k3tr_times_how.asp

     

    Using Windows Server 2003 in a Managed Environment

    Windows Time Service

    http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/security/ws03mngd/26_s3wts.mspx

     

    Windows 2000 Time Service Whitepaper

    http://www.microsoft.com/windows2000/docs/wintimeserv.doc

     

    I look forward to your reply. Also, if you have any questions or concerns, please do not hesitate to let me know. I am happy to help. :-)

     

    Thank you for your time and cooperation!

     

    Sincerely,

    Tom Zhang

     

    2009年1月22日 上午 09:07
    版主