"System clock has been set back" error
If you get a "system clock has been set back" error from LM-X License Manager, LM-X has detected that your system clock has been set back. Under some circumstances, the check can return a false positive. For example, you might have accidentally changed the clock to a future time.
To resolve this problem, you should set the system clock to the correct (present) time. If you believe the error is a mistake and your system clock seems to be correct, ask your application vendor for assistance.
For more information, see System clock check.
Problem with verifying system clock
If there is a problem with using lmxresetsystemclock.exe to synchronize you local system's clock with a remote time server, you may see the following error:
LM-X Error: Could not verify system clock due to failed connection with remote time server
To resolve this problem, it is necessary to verify that UDP port 123 (NTP protocol) is not blocked by a firewall.