If you use Kronos TimeKeeper on a large network, you’ve probably had issues with running it in different subnets or VLANs. It says that it can’t find the database even though you have mapped the necessary drives. I’ve had those very issues, but apparently, TimeKeeper doesn’t have a way to fix it. I found a way today.

The best I can figure, TimeKeeper sends out a broadcast packet during the install to find out where the server is. On a subnetted network, this won’t help. TimeKeeper creates several ODBC entries during the install. In these entries, you manually specify the the server IP address. Go to SystemDSN in the ODBC control panel options. You will see three entries for TimeKeeper. Edit each one, and on the Network tab, add Host=[ipaddress] to the TCP/IP options where [ipaddress] is the IP address of the server TimeKeeper is installed. It should work beautifully after that.