The WaspTimeServer service uses two ports: UDP port 65525 is used for broadcast messages, and TCP port 10002 is used for clients to connect to the service. On a Domain Controller, there could be conflicts for either of these ports. Based on the nature of how the DNS service reserves ports, this conflict may not become evident until the server has been running for weeks or months.
On the domain controller, you can try entering the following into a Command Prompt window:
netsh int ipv4 set dynamicport udp start=10000 num=1000
This command reserves UDP ports 10000 - 11000 to the dns.exe process, which should prevent it from attempting to take UDP port 65525 away from WaspTime.
Also, if the server machine is running Small Business Server, TCP port 10002 may be in use, so the WaspTimeServer service would need to be changed to another number. We recommend using TCPView.exe to check the ports and find one 10003 or higher that is not in use to use instead.
http://technet.microsoft.com/en-us/sysinternals/bb897437.aspx
Once you have located your open port, you will need to edit the registry on the server. In HKEY_LOCAL_MACHINE\SOFTWARE\Wasp Technologies\WaspTime5\Options, you will need to modify Service Port, ServicePort, and Time Server Port. Make sure Base is set to Decimal, then enter the new port number. The client machines should locate the service through the UDP port and update their own registry entry. If they do not, you can manually set Time Server Port in HKEY_CURRENT_USER\Software\Wasp Technologies\WaspTime5\Options.
We have had inconsistent results in the past with setting up exclusions for the DNS service, so the recommendation is to move the WaspTimeServer service to a different machine. If the steps given in this article do not work, moving the service would be the only other option. For more information on moving the service, see the Knowledgebase article linked below "WaspTime: Time server will not stay started".
On the domain controller, you can try entering the following into a Command Prompt window:
netsh int ipv4 set dynamicport udp start=10000 num=1000
This command reserves UDP ports 10000 - 11000 to the dns.exe process, which should prevent it from attempting to take UDP port 65525 away from WaspTime.
Also, if the server machine is running Small Business Server, TCP port 10002 may be in use, so the WaspTimeServer service would need to be changed to another number. We recommend using TCPView.exe to check the ports and find one 10003 or higher that is not in use to use instead.
http://technet.microsoft.com/en-us/sysinternals/bb897437.aspx
Once you have located your open port, you will need to edit the registry on the server. In HKEY_LOCAL_MACHINE\SOFTWARE\Wasp Technologies\WaspTime5\Options, you will need to modify Service Port, ServicePort, and Time Server Port. Make sure Base is set to Decimal, then enter the new port number. The client machines should locate the service through the UDP port and update their own registry entry. If they do not, you can manually set Time Server Port in HKEY_CURRENT_USER\Software\Wasp Technologies\WaspTime5\Options.
We have had inconsistent results in the past with setting up exclusions for the DNS service, so the recommendation is to move the WaspTimeServer service to a different machine. If the steps given in this article do not work, moving the service would be the only other option. For more information on moving the service, see the Knowledgebase article linked below "WaspTime: Time server will not stay started".