How Do I Stop Windows Time Server from Flooding My Network
Posted on 2009-02-14
I have set up a Wndows XP machine on my LAN as an Authorative Time Server. It is connected to a hardware clock and serves time information to other WIndows XP machines on the same LAN. These other machines are NTPClient enabled via the registry settings. One of the NTPClient machines ia a WiFi Tablet PC. As such there is no gurantee of always having a strong wireless signal and hence is subject to a number of TCP/IP socket connection/disconnections. During this connection process and when the signal strength is low I have noticed that the time server is flooding the network with UDP/NTP packets directed to WiFi Tablet. This was picked up using the Tamosoft CommView packet analyser. The flooding might last for about 10-20 seconds but it is enough to cause the End User's application software to disconnect its own working copper based socket and report an alarm. When the signal strenth is low, I don't know why the Time Server starts to flood the network with NTP requests every 300-500ms? Looking at the packet analyser, it appears that the Time Server is deciding to do this off its own back. There does not seem to be any indication that it has come form the WiFi Tablet client.
Does anyone know why the Time Server might suddenly decides to send multiple NTP commands? Can I control this in the WS32 registry settings?