To: 	Arren Conner (Xenix)
Subject: 	TimeServ KB

Are there any KB for TimeServ already?  If not, we should at least make the following MS Internal so that PSS can find it, and consider moving it to External to help the customers who know how to help themselves.  Let me know if we should edit it, etc.

keywords: TimeServ Time Service NTP clock
Subject: TimeServ FAQ

Q: TimeServ from the Windows NT 3.5 Resource Kit runs for awhile and then uses up 100% of my CPU.
A: If you have type=internet, this is a known bug which is fixed in the version of TimeServ contained in the 3.51 Resource Kit.  The problem starts when there is an error from USNO over the Internet, and the workaround is to stop the Time Service and then Start it again (the error might continue to re-occur).

Q: Does TimeServ support NTP (Network Time Protocol)?
A: Yes, Simple NTP client support was added to the version of TimeServ in the 3.51 Resource Kit (it did not exist in the 3.5 Resource Kit version).

Q: Does TimeServ support the RFC-868 Time protocol?
A: No, current versions don't support this protocol (which does not have sub-second resolution).

Q: I'm having trouble with TimeServ from the Windows NT 3.5 Resource Kit and the "new shell" pre-release.
A: This is a known problem, fixed in the version of TimeServ contained in the 3.51 Resource Kit.

Q: I'm having trouble with a modem call to Germany from TimeServ in the 3.51 Resource Kit.
A: If this is a regression from the previous version of TimeServ, contact DougHo@microsoft.com for a potential update which will go into a future release of the Resource Kit.  Note that Germany's PTB phone number is in timeserv.ini of the 3.51 Resource Kit.

Q: The modem phone number for Sweden doesn't work anymore.
A: The number has been replaced with a premium number that can only be dialed from within Sweden.  The new number is 0719 312 719, run by Precision Timing.

Q: My modem used to work fine calling NIST, but stopped working sometime in '95 - any ideas?
A: If you have speed set to something other than 300 or 1200, try one of those two settings.  A potential update to improve compatibility with NIST's new V.32bis modems will go into a future release of the Resource Kit (contact DougHo@microsoft.com if you desire to test it).

Q: TimeServ says my modem timed-out (may be busy); I use pulse-dialing if that matters.
A: TimeServ expects the other modem to have connected by a certain time after the dialing starts.  In the first version of TimeServ the value was 35 seconds, in the second version it was 45 seconds.  The next version will use a timeout value of 55 seconds.  If you need to test the value, contact DougHo@microsoft.com.

Q: TimeServ from the 3.5 Resource Kit doesn't work with my normal modem, but it works with another modem.
A: Try adding V1 (verbose results) to the modem command.  If this works, the fix for allowing non-verbose results in is the 3.51 Resource Kit.

Q: I use the Simple NTP support in the version of TimeServ that came in the 3.51 Resource Kit and get an error message near December 31st '95.
A: A minor bug exists because of the impending leap second notification.  TimeServ will skip setting the time that day (UTC) but should recover automatically the following day.

Q: Can I "log" time set events (not errors)?
A: Yes, such a feature was added to the version of TimeServ in the 3.51 Resource Kit (it did not exist in the 3.5 Resource Kit version)

Q: Can I set the period to be less often than once per day?
A: Good suggestion - a future version should allow setting every two, three, or seven days.

Q: Will TimeServ support Spectracom's NETCLOCK/2 or NETCLOCK/GPS or Model 8170?
A: The version of TimeServ in the Windows NT 3.51 Resource Kit should support these, although the NETCLOCK/GPS is untested.

Q: Is TimeServ source code available outside Microsoft (I'd like TimeServ to support my special clock hardware)?
A: Source code is probably not available, but check with Louis Kahn of Microsoft.  Sometimes new clock hardware can be supported by contacting DougHo@microsoft.com (binary, not source).

Q: The help file seems to be missing something.
A: Correct, the documentation is TimeServ.wri

Q: What is the latest version of TimeServ - have there been fixes/enhancements?
A: The 3.51 Resource Kit contains a revision of TimeServ which has various fixes/enhancements (not limited to the ones described), including binaries for the PowerPC.

Q: I want a client on non-Windows NT machine.
A: If something like NET TIME \\server /set /y in a logon script isn't satisfactory, try one of the alternative client/server programs.

Q: (random problem)
A: Check the description of error messages and a few common questions in TimeServ.wri, the latest version is kept on \\dougho\public\timeserv.  WARNING: do NOT distribute files from this location to customers, the directory contains source code.

Q: (random question)
A: If none of the above helps and it sounds interesting, feel free to contact DougHo@microsoft.com.  Although I try, I can't promise to resolve every situation (for example, I don't plan to make any graphical front-end).
