Who rated this post

A quick and dirty workaround for this issue is to temporarily move the gw or mgmt clock 24h ahead in the future.

Yep, it's that easy.
That's far off from being an ideal workaround, but if you're stuck knee deep in this where-did-my-Feb-29th-go craze, that's worth a try.
Moving the clock forward should cancel the bug in every piece of yet to be fixed Check Point code.

Works for:
- the CPUSE "Connection Error, FDT - Unexpected error code" issue
- new gateways unable to download their license
- new gateways unable to connect to Smart-1 Cloud / MaaS

Again, not ideal, but worth a try.
If your equipment is going through initial setup or planned maintenance, the system date being off by 1 day is probably not that bad.

This whole March 1st bug it totally effed up.