Are there any known Bugs in Windows/2000s SNTP Server?
According to David Woolley there are some anomalies in the implementation of SNTP in Windows/2000: I just discovered that the office Windows 2000 domain controller and IIS machine have been configured to synchronise to our *nix time server (net time /setsntp:). A quick look at their behavour raises some serious concerns: the stratum is always 2, even when the upstream server was stratum 3, and even when it has never been synchronised.xntpd and ntpd to at least 4.0.99j will synchronise to them even though they are only SNTP (and indicating a false level of reliability). Never synchronised Windows 2000 servers respond with a zero reference time and reference ID and are ignored, even though the leap bits are valid and the stratum is 2. ntptrace reports a root dispersion and synchronisation distance of 1.0 in all cases, but everything else seems to report zero, which makes me wonder whether ntptrace has SNTP detection code that is missing from the real daemon. The xntpd used was the origin
- Are there any known issues or conflicts when the OPCServer is running Windows 2000 Professional or Server and the OPCClient is running Windows NT 4.0 Workstation or Server?
- Where can I learn more about any known issues with Adobe products and Windows Server 2008 R2?
- Are there any known security problems with the Purveyor Server for Windows NT?