[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1884
  • Last Modified:

How do I use multiple Static IP's on a CheckPoint Safe@Office 500?

I have a Safe@Office 500 Check Point Firewall. I also have 13 static IP's. I have about 5 Servers on my Network and all of them have services that need to be passed from the Firewall to them.

The IP scheme is 169.130.x.17-30. 17 of course is my Gateway, so the first usable is 18. Now if you go to x.x.x.18:xxx you can log into my Firewall. I have also setup rules to allow any RDP traffic coming to the Gateway to be passed to 10.10.10.2 which is one of my servers. Any TCP traffic going to port 657 on my Gateway is passed to 10.10.10.6 and so on and so forth. The problem is that I have a WEBSERVER that traffic heading to 169.130.x.18 is going to one internal server of 10.10.10.9. Now I need traffic heading for 169.130.x.20 to go to another internal server of 10.10.10.5.

However this firewall is not like any other I have ever setup and I can't figure out how to do it. Netscreen and Calyptix both have MIP's. So I would say any traffic going to x.x.x.x external IP needs to be redirected to an internal IP of 10.10.10.5. But CheckPoint doesn't have that. Has anyone ever done this on a CHeckpoint and can it be done.

0
aando
Asked:
aando
  • 4
  • 3
1 Solution
 
EmpKentCommented:
Aando,

Have you created a static NAT for each public IP to the LAN IP? Once you do that you could create an allow for only port 80 on the two www servers.

Thanks,

Kent
0
 
aandoAuthor Commented:
I have tried but it doesn't work. So I don't know if it is me not setting it up right or if it just won't work.
0
 
EmpKentCommented:
I just dl'd the manual and you can use the Network Object Wizard to setup a single computer object and set that as a static NAT to an external IP.

The process starts on page 135ish.

Kent
0
A Cyber Security RX to Protect Your Organization

Join us on December 13th for a webinar to learn how medical providers can defend against malware with a cyber security "Rx" that supports a healthy technology adoption plan for every healthcare organization.

 
aandoAuthor Commented:
Ok. I was looking at "Using Network Objects" and it says it can be done but it isn't. So I am wondering if it is a configuration issue on my part. Could it be that I already have SMTP traffic going to .18 being routed to the internal server at 10.10.10.5 and now I want owa that is being sent to .20 also to be routed to 10.10.10.5? In other words, can I have two different services going to two different external static IP's route to the same internal IP on this Firewall?
0
 
EmpKentCommented:
Aando,

If you were able to do port forwarding on this box, you might be able to convince it to have individual ports from two public IPs pointing to the same internal IP but I see nothing in the manual to suggest it does.

With static NAT, I suppose that could be done but the bigger question is; why would you want to? If you have your Exchange box as 10.10.10.5 just have your MX (25) and your users (80) point to .18 and leave .20 open for another purpose.

If you really need to differentiate between the two services, use different FQDNs pointing to the same IP...

Thanks,

Kent
0
 
aandoAuthor Commented:
Thanks, EmpKent

I was able to create a Network Object for the Exchange Server and then to a Static NAT One to One from the External .20 to the Exchange Server. Then I had to create a Rule with Allow and Forward, telling it that Traffic from the WAN going to the Gateway running service "WebServer - a predefined service for webservers in checkpoints" to forward to the Network Object I named Exchange Server which has the external .20 being Nat'd to the Internal Exchange Server IP.
0
 
aandoAuthor Commented:
Thanks for the help.
0

Featured Post

Upgrade your Question Security!

Add Premium security features to your question to ensure its privacy or anonymity. Learn more about your ability to control Question Security today.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now