WaspTime and its timeclocks are designed, tested, and supported over local networks/subnets. The information below may be useful to enable communication to clock(s) on networks remote from the WaspTime Server Service PC, but Wasp does not test or guarantee communication in that kind of environment.
If WaspTime is running properly, but it is unable to communicate with the timeclock on the correct IP address, you need to enable port forwarding on your router(s) and/or open up the port on your firewall.
Also in the clock's network settings, the default gateway needs to be set to a router that can communicate with the WaspTime Server Service PC (usually the same as the database PC).
The required port varies by clock model as follows:
TCP port 4370: B1100 and B2000 biometric timeclocks, and the other newer keypad clocks BC100 barcode, RF200 RFID, and HD300 HID
TCP port 1043: B1000 older biometric clock
TCP port 3000: J20xx Job Clock
TCP port 1001: older Wx100 2-button clocks (W1100 barcode, W2100 magstripe, W3100 RFID)
TCP ports 59005 and 59094 or 39005 and 39094*: ESI clock. See KB titled "WaspTime: Not able to communicate with the ESI system" (linked below) if your documentation indicates your system is using 39 or any other base for the ports.
Further information: The article linked below "Multiple products: Is there a way to tell if my ports are being blocked?" has a discussion and utility for testing the network communication.