remote gateway not using the external NAT'd IP address of log server

[nflnetwork29]

Hi there we have a  Domain log server with a static External  NAT'd IP address. 

When i browse the security logs on the gateway it shows that the logs are being sent to the PRIVATE IP address of the log server and NOT the EXTERNAL.

Some gateways work some do not.  It's hit or miss. The yare all configured identically

ie "send logs according to policy" 

How to fix this?

[PhoneBoy]

Is the NAT defined on the management server object or as a manual NAT rule?

[nflnetwork29]

i have NAT defined on the management server object. 

[Maarten_Sjouw]

When you have a seperate log server there are 2 things you can do:

1. on each extranal gateway edit the masters file to contain the External IP of the log server
2. create a second Check Point host and set logging on it to on and give it the external IP of the log server, now in the object of the remote gateways  add this object as the log server instead of the real object with the internal IP. 

Option 2 works best and with additional comments in the object you can make sure others also understand why that object is there.

[nflnetwork29]

Would setting this on the gateway be the equivalent of option 1?

[PhoneBoy]

It's similar to Option 1, yes.

[nflnetwork29]

Is it possible to use the Same External IP address for management and logs if they are each on their own dedicated server?

Can it be done with port forwarding? 

or does each server need it's own unique External NAT'd IP address?

[PhoneBoy]

Never seen that done before...but it might work.