In many situation this short additional procedure (remember additional) helps.
1. Create of a "dummy" Check Point Host object pointing to public IP which is used as a Static NAT IP for original LogServer.
2. Enable Logging&Status function.
3. Edit each problematic gateway and add host from point 1 as a primary log server.
4. Install Policy on problematic Gateways.
5. With command, netstat -apn | grep ":257" on problematic GW You can now monitor if connection with SmartLog public IP is now in ESTABLISHED state. If You see such connection state, logs should be sent to and processed by SmartLog.