YATS32

Frequently Asked Questions

The registration key you sent me doesn't work, why?

Please see the General FAQ webpage for the answer.

I installed YATS32 as a service under WindowsTM XP/Vista, but it doesn't do anything, why?

YATS32 is not able to connect to any Internet time servers from behind a firewall or proxy server. What can I do?

Typically firewalls are not configured by default to allow SNTP protocol messages. This prevents YATS32 from contacting or receiving messages from Internet time servers. In order for YATS32 to operate correctly using the standard SNTP protocol, you will need to get your firewall administrator to allow IP/UDP outbound packets to port 123, and inbound IP/UDP packets from port 123.

The following firewall incoming packet filter rule will allow YATS32 to operate using the SNTP protocol while maintaining the security of your site. Please note that for incoming packets the source refers to the time server, and the destination refers to the machine running YATS32 as a client.

If you use a proxy server to connect to the Internet from a LAN, you may have make a configuration change to the proxy server to use YATS32. At the proxy server, map UDP port 123 to an actual Internet time server on port 123. When you use YATS32, use the address or name of the proxy server as the NTP host in YATS32's server settings. This will only allow you to access a single Internet time server.

If you cannot achieve this, but you are able to use a web browser via an HTTP proxy to the Internet, then you could try configuring the YATS32 client to use the DayTime protocol via the proxy. This is more complex to set up, has 1 second resolution, and is subject to time zone errors. To determine if you can access a time server this way, substitute you chosen time server IP address into this URL, http://tycho.usno.navy.mil:13 , and use it in your web browser. If a text timestamp is returned, then you should be able to configure YATS32 to use the HTTP proxy.

How can users be prevented from enabling server functions?

It can be desirable to prevent users from enabling server functions in order to avoid network disruption. Starting at version 8.1 build 28, YATS32 provides a mechanism for doing this. It requires that you modify the registry using a registry editor such as REGEDIT or REGEDT32.

Under key: HKEY_CURRENT_USER\Software\Dillobits\yats32\AppOptions

Create a DWORD value called ClientServer and give it a value of 0.

YATS32 closes or disappears before I can enter my registration key or change my options!

The most common cause of this problem is that you have accidentally set the following two run options: Set Time at Startup and Close after setting time. With both these set YATS32 will often set the time and close before you have time to do anything. It is precisely to handle this kind of situation that the -noauto command line option was implemented. It tells YATS32 to disable all of its automated features. To use it, invoke YATS32 from a DOS window by issuing the command:

"C:\program files\Dillobits Software\YATS32\yats32.exe" -noauto

If you selected a different install directory at install time, you will have to adjust the above command appropriately. If YATS32 starts up minimized, you can maximize it by clicking on the small clock icon that appears in your task bar tray.

Why does YATS32 fail to run as a server or listen for SNTP time broadcasts under Windows XP/Vista?

This occurs because, under the Windows XP, the Windows Time service ties up port 123. You can avoid this problem by using the Computer Management console to stop the Windows Time service, and then setting its startup type to 'Disabled'. This will not have any detrimental effect on your system unless your system is a member of a server cluster.

If your question was not answered here, please check the General FAQ webpage.