The clocks on the client and server machines are skewed

  • Hi all,

    When running SP which read data from remote server (linked server), after few minutes, I get the following error: "Failed with the following error: ERROR: SQL Network Interfaces: The clocks on the client and serevr machines are skewed".

    We checked the clocks on both machines, they are both on the same domain and connected to the same DC.

    Does any body have an idea?

    Thanks,

    Ran.

  • Regional settings???

    -----------------------------------------------------------------------------------------------------------

    "Ya can't make an omelette without breaking just a few eggs" 😉

  • Two articles on setting regional settings:

    http://support.microsoft.com/kb/273558

    http://stackoverflow.com/questions/211549/how-to-change-system-default-regional-settings-in-windows-xp

    😉

    For better, quicker answers on T-SQL questions, click on the following...
    http://www.sqlservercentral.com/articles/Best+Practices/61537/

    For better answers on performance questions, click on the following...
    http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

  • Hi Ran

    Are the clocks on all machines and the DC showing the same time?

    Best Regards

    Chris

  • Thank you all, but I forgot to mention that it is not happening all the times...

    So if it was regional setting, it would have occur all the time...

  • that might be a problem of Time synchronization with domain controller,schedule the time synchronize with Domain controller command on OS level on the machine who creating this problem

    Regards,
    Syed Jahanzaib Bin Hassan
    BSCS | MCTS | MCITP | OCA | OCP | OCE | SCJP | IBMCDBA

    My Blog
    www.aureus-salah.com

  • I agree with Syed.

    The clocks on the client and server machines are skewed".

    Had same issue, seems some servers were losing time sync with domain controller/s.

    Affected browsing certain in-house websites, also could not logon to one server via RDP.

    Once server time sync with DC's was resolved, the 'clocks skewed' error disappeared.

  • I get ... error: ERROR: SQL Network Interfaces: The clocks on the client and serevr machines are skewed".

    Please treat as urgent.

    Kindly give the solution.

  • Hi,

    I tried to find the solution which helped us.

    If i'm not wrong - we installed lated SP to the OS.

    Ran.

  • hi,

    error : The clocks on the client and server machines are skewed".

    solution : Once server time sync with DC's was resolved, the 'clocks skewed' error disappeared.

  • Your organisation should have a Group Policy Object (GPO) in place to force correct clock synchronisation and frequency of synchronisation. This is something you can raise with your Windows Administrators.

    If you do not have a GPO governing this, there is a risk that some machines may have a configuration where they check direct with an internet time server, which can be different to the domain time - this problem gets worse if the relevant machines do not have access to the internet as their local time will drift.

    If you have a mixture of Workgroup machines and domain-connected machines then your Windows people should have a process in place to ensure clock synchronisation over the entire network, as any GPO will only deal with the domain-connected machines.

    Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.

    When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara

Viewing 11 posts - 1 through 10 (of 10 total)

You must be logged in to reply to this topic. Login to reply