Solved

Looking for experts in Nokia IP350 firewall (very urgent)

Posted on 2006-06-12
5
868 Views
Last Modified: 2013-11-16
Hi there, I have a nokia IP350 firewall, in which I change some setting from the web-based Voyager which are as follows:

1. change the IP interface for one the the port
2. add in a static route
3. change the "host address assignment" IP

After changing, I did a reboot of the firewall.

now I can't ping the firewall from my servers. I can't use voyager to change back the settings, Can anyone help urgently? Thanks alot.
0
Comment
Question by:simonlai
5 Comments
 
LVL 51

Expert Comment

by:Keith Alabaster
ID: 16891872
Simon, thought you had sorted this one?
0
 
LVL 12

Expert Comment

by:srikrishnak
ID: 16892109
Can you telnet/ssh to any of the other interfaces. If so see in the routing table what went wrong.
0
 
LVL 5

Accepted Solution

by:
dbardbar earned 500 total points
ID: 16895325
Most likely the firewall is blocking traffic to the machine, as the security policy it has contains all the old IPs. It is especialy sensitive to changes in the IP defined as the main IP of the machine.

Another possibilty, is that the FW-1 license you have is for the old IP, which basicly means your IP is not valid now.

Login to the machine using the serial port, and run "fw printlic"/"cplic print" (depending on your version). If you see the license, and it is for the IP you do not have on the machine, then you will need to obtain a new license (for no extra charge) for the new IP, from Check Point's user center site. If you got the license from an integrator, than you should talk to him about obtaining the new license.



If that isn't the issue, than the problem is probably just FW-1 blocking traffic.
What you should do is unload the security policy, connect with the GUI, change ALL the relevant settings (interfaces, antispoofing, Firewall object main IP, encryption domains, etc.), and then install the policy. There is some chance that once you install the new policy, your GUI will disconnect (depending on your FW-1 version). Check with "fw stat" on the console if the date on the policy has been updated. This means that indeed the new policy works.

Now, before you unload the security policy, it is important to understand that until you reload the new policy, the machine is unprotected. It would be wise to take the machine offline, physicly disconnecting all the cables, and connect with the GUI with a cross cable from a isolated PC/laptop.
To unload the policy, run "fw unload localhost" or "fwm unload local" or "fw unloadlocal", depending on your version. Run "fw stat" to make sure it has been unloaded.


0
 
LVL 1

Author Comment

by:simonlai
ID: 16896759
Hi Keith, yes I have sort this out. Just that forgot to remove this post. anyway, dbardbar's comment is correct. I unload the policy and reload after going into voyager to change back the settings. Thanks everyone.
0
 
LVL 51

Expert Comment

by:Keith Alabaster
ID: 16896777
Phew.... Thanks Simon :)
0

Featured Post

On Demand Webinar - Networking for the Cloud Era

This webinar discusses:
-Common barriers companies experience when moving to the cloud
-How SD-WAN changes the way we look at networks
-Best practices customers should employ moving forward with cloud migration
-What happens behind the scenes of SteelConnect’s one-click button

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Wikipedia defines 'Script Kiddies' in this informal way: "In hacker culture, a script kiddie, occasionally script bunny, skiddie, script kitty, script-running juvenile (SRJ), or similar, is a derogatory term used to describe those who use scripts or…
Do you have a windows based Checkpoint SmartCenter for centralized Checkpoint management?  Have you ever backed up the firewall policy residing on the SmartCenter?  If you have then you know the hassles of connecting to the server, doing an upgrade_…
How to Install VMware Tools in Red Hat Enterprise Linux 6.4 (RHEL 6.4) Step-by-Step Tutorial
Attackers love to prey on accounts that have privileges. Reducing privileged accounts and protecting privileged accounts therefore is paramount. Users, groups, and service accounts need to be protected to help protect the entire Active Directory …

685 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question