Tips & Tricks

Virtual TimeClock Tips & Tricks - May 2015

Communication is important. This applies to both people and computers. When communication breaks down, we're unable to get the information we need. In this month's newsletter, we'll cover the common reasons why Network Edition users may experience a loss of communication between networked time clocks and provide helpful tips on how to restore this vital function.

Local Clients Can't Connect
Do your local time clock clients sometimes fail to connect to the time clock server? If so, you may receive a message that the network connection failed or the time clock server is not running. There's usually a simple explanation for why this is happening and an even simpler way to fix it. A local client is a time clock that's running on the same LAN (local area network) as the time clock server. This usually means the computers are in the same office, store, or physical location. Here are some things that may be preventing your local time clock clients from connecting to the time clock server.
  • Time clock server computer isn't running.
  • Time clock server computer IP address changed.
  • Time clock server computer is going to sleep or hibernating.
  • Time clock client computer doesn't have a network connection or is connected to the wrong network or subnet.
Quick Tip:
Here are some tips for resolving these local client connectivity issues quickly and permanently.

Remote Clients Can't Connect
What about when your local clients are fine, but your office across town can't connect to the time clock? A remote client is a time clock that's connecting to a time clock server on a different network, usually over the Internet via a VPN (virtual private network) or a port forward. This is how you use the time clock across multiple business locations, or access your time clock data while away from the office. A client connecting over a VPN behaves as if it's on the same network as the time clock server even though it's in a different physical location. When troubleshooting remote client connections, start with the local client troubleshooting tips listed above. If that doesn't resolve the issue, consider the following:
  • Public IP address of the router at the time clock server location changed.
  • Port forward in the router/modem is no longer valid.
Quick Tip:
Here are some tips for resolving remote time clock client connectivity issues.

Non-networking Connection Issues
You may also experience some time clock issues that are unrelated to your current network configuration. Most of these occur after moving the time clock client to a different computer or installing the time clock client on a new computer. You'll always receive a clear message from Virtual TimeClock telling you exactly what the issue is. Here are the most common non-networking connection issues.
  • Time clock client and time clock server versions are not the same.
  • Time clock client is unable to connect due to reaching the maximum client registration count.
  • Unauthorized password is preventing the time clock client from logging in.
Quick Tip:
Solutions to each of these non-networking connection issues can be found here.

We've worked hard over the years to make Virtual TimeClock Network Edition easy for non-technical people to install, configure, and maintain. But if you still need help with your time clock, don't hesitate to contact us. We're here to help!