Windows DOES listen on port 123 for SNTP info. From the Kloth paper
I found using your suggestion to Google:
"The SNTP protocol is described in RFC-2030.
The NTP time server is listening on UDP port 123.
SNTP formats are compatible to the NTP protocol specification, using a
simplified access strategy for servers and clients; the access
paradigm is identical to the UDP/TIME protocol."
Switching to time.windows.com did not help. I don't see anything in
my Linksys router that is blocking anything. I installed Atomic Clock
Set and it works!
I don't know how to find out what Win2KSP4 is blocking. In fact I
don't know if it has a firewall in it. Can anyone tell me?
That leaves my Antivirus, AVAST. or maybe something that CCleaner
install. Or Spyware Blaster that I also use.
=============
Win2000 does not have an inbuilt firewall. I don't remember if it has a
Safe
Mode with Networking but if it has then you should try it in order to
eliminate interference from your various protective programs.
There is another potential problem. Most registry cleaners are considered
either useless (at best) or damaging (at worst). Have you considered the
possibility that CCleaner might be the cause of your problem? Uninstalling
won't help you - if it damaged the registry then the damage is done.- Hide
quoted text -
- Show quoted text -
I tried Safe Mode with Net (no anti-virus software). W32time still
could not find the time server. Atomic Time Sync works fine. Looking
through the registry for W32* didn't show any unusual (smashed)
entries but I didn't see any entry that holds the time-server host
address either. I have no evidence that CCleaner caused any problem.
Is there a way to get W2K to reinstall W32Time and related files?
=================
If your registry "cleaner" modified the some sensitive part of the registry
then it's anyone's guess what it might have done, largely because registry
cleaners have to do a lot of guessing when they go about their "cleaning"
business. After all a typical registry contains 10,000 keys or more, and how
is a registry cleaner supposed to know the exact function of each of them?
Registry cleaners work by applying the FUD factor: Fear, Uncertainty and
Doubt. They report a large number of so-called "errors" and
"inconsistencies", thus creating fear in the user's mind. They then ask him
if he really wants to continue running his machine in this semi-crippled
way. This is the Uncertainty and Doubt part. They then go about their
business and boast at the end that the machine is now "optimised". Most
users will believe this because they never ran any benchmarch tests. If they
had then they would realise that the machine performs no better and no worse
than before - except that some registry cleaners inadvertently break certain
things.
OK, I'll get off my soap box. If I was in your position then I would type
this into a Google search box, then examine the most promising links:
install windows "time server"
Good luck!