Welcome, Guest. Please login or register.
Did you miss your activation email?
Friday 13 December 2024, 12:28:13 pm

Login with username, password and session length

Download the latest community FREE version  HERE
14261 Posts in 4377 Topics by 6517 Members
Latest Member: Sandro
Search:     Advanced search
+  EFW Support
|-+  Support
| |-+  General Support
| | |-+  Port forwarding fails after restore to new firewall
0 Members and 3 Guests are viewing this topic. « previous next »
Pages: [1] Go Down Print
Author Topic: Port forwarding fails after restore to new firewall  (Read 9685 times)
lurifax
Jr. Member
*
Offline Offline

Posts: 5


« on: Tuesday 20 October 2009, 02:13:54 am »

Hi,

I use Endian 2.3RC1, and has got it to work as I wanted. I installed Endian on a rather old server and wants to move it to a new one.
During install of the new (also running same version of Endian) I restore a config from file as stated in the installation options.
My new firewall boots, gets the same private IP, external IP's rules and everything seems to be exactly as on the old one.

When I replace the FW, and tries to use it, some of the port forwarding no longer works.
I know, it is an Release candidate, but has anyone else had this same problem?

I use 5 public IP's and forwards both RDP, pop3 +++ to different internal servers.
Som work, some does not respond.

Hope someone could help out, because this FW gives me all I ever wanted in a Firewall, and even some more...
Love it, if I only get it to work flawless.

Very similar to next gen IPCop, but even more smooth and feature rich in my point of view.
(Has been a IpCop user fore many years)

Reg,
Stig
Logged
lurifax
Jr. Member
*
Offline Offline

Posts: 5


« Reply #1 on: Wednesday 28 October 2009, 07:54:35 pm »

Nobody?

To bad, might go back to IpCop again, even if it lacks some functionality.
Logged
bayross
Full Member
***
Offline Offline

Gender: Male
Posts: 23


« Reply #2 on: Wednesday 28 October 2009, 10:57:24 pm »

Try disabling all of them, reboot the firewall and then re-enable them and reboot again.
Let me know if that fixes it.
Thanks,
Garrett
Logged
Pages: [1] Go Up Print 
« previous next »
Jump to:  

Page created in 0.078 seconds with 18 queries.
Powered by SMF 1.1 RC2 | SMF © 2001-2005, Lewis Media Design by 7dana.com