We are experiencing NTP Sync errors, does anyone have any ideas?

28 Mar 2010 04:15:04 PDT ^http-0.0.0.0-9043-10^1001100010151015^3304^BUSINESS_LOGIC^AUTH.USER.ERROR.INVALID_USER_CREDENTIALS_EXCEPTION^com.hosangit.ext.SAML.SAMLHelper^^Invalid user credentials - Invalid Issuer. com.hosangit.saml.exception.SAMLResponseException: Exception Type 17,Description com.hosangit.saml.exception.SAMLException.EXPIRED_ISSUER_INSTANT : Fri Mar 19 10:25:54 PDT 2010, Current time is Sun Mar 28 04:15:04 PDT 2010, it is valid till Fri Mar 19 10:30:54 PDT 2010

        at com.hosangit.saml.AbstractSAMLResponseHandler.validateIssuerInstant(AbstractSAMLResponseHandler.java:72)

        at com.hosangit.saml.opensaml.SAMLResponseHandler.validateAssertion(SAMLResponseHandler.java:652)

        at com.hosangit.saml.opensaml.SAMLResponseHandler.validateSAMLResponse(SAMLResponseHandler.java:538)

        at com.hosangit.ext.SAML.SAMLHelper.getSAMLResponse(SAMLHelper.java:242)

        at com.hosangit.ext.SAML.SAMLHelper.validateSAML(SAMLHelper.java:58)

        at com.hosangit.ext.login.SAMLCredentialsHandler.validateSAML(SAMLCredentialsHandler.java:391)

        at com.hosangit.ext.login.SAMLCredentialsHandler.validate(SAMLCredentialsHandler.java:155)

        at com.hosangit.ext.login.SAMLCredentialsHandler.handleLogin(SAMLCredentialsHandler.java:427)

Are you sure it is an issue with NTP??

NTPv4 can usually maintain time to within 10 milliseconds (1/100 s) over the public Internet, and can achieve accuracies of 200 microseconds (1/5000 s) or better in local area networks under ideal conditions.

Do a bit of troubleshooting on the functionality of NTP on your workstation

Troubleshooting

One of the quickest commands to verify that ntpd is still up and running as desired is ntpq -p. That command will show all peers used and configured together with their corner performance data.

# ntpq -p



     remote      refid    st t when poll reach   delay  offset jitter


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


 LOCAL(0)        LOCAL(0) 3 l    9   64  377    0.000   0.000   0.000


*swisstime.ethz. .DCFa.   1 u   17   64  377   25.088 -10.040   1.071 

Note the column st is stratum where 1-3 is the typical value











Windows 2000 (Win2K) uses a time service, known as Windows Time Synchronization Service (Win32Time), to ensure that all Win2K computers on your network use a common time. The W32Time Service is a fully compliant implementation of the Simple Network Time Protocol (SNTP) as detailed in IETF RFC 1769. SNTP uses UDP port 123 by default. You can download this tool to validate the UDP port 123 is open. If you want to synchronize your time server with an SNTP server on the Internet, make sure that port is available. Check out this article for troubleshooting Windows Time Service







Test NTP server, using

net time /querysntp

Select a NTP server, using

net time /setsntp:swisstime.ethz.ch

Start the W32time service with

net start W32Time

You can also set the start option of the Windows Time Synchronization Service (W32Time) to Automatic, so the service will start when Windows/2000 starts.