Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 14 replies
  • Subscribers 2 subscribers
  • Views 3080 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

6.300 port forward problem.

Simon Shaw
Patched up to 6.300 today and now my companies web mail and outlook is no longer accessible.

I have an additional IP on external interface, this is supposed to NAT through to our Exchange server, instead, the firewall web admin interface is loading instead!  Argh.  Any ideas??

PS: I suggest a reboot for this patch too, after applying it, CPU usage went very high.  Had to reboot to fix it.


This thread was automatically locked due to age.
Parents
  • 0
    Further to this, if I change the webmin port to something other than 443 my webmail works... (Which uses port 443).

    So this is a workaround that fixes the issue.

    Looks like NAT prioritys are screwed?
  • 0 in reply to Simon Shaw
    Hi All,

    Same problem here... I guess the following rule creates the mess...:

    Chain AUTO_INPUT (1 references)
     pkts bytes target     prot opt in     out     source               destination
        0     0 LOGDROP    tcp  --  *      *       0.0.0.0/0            0.0.0.0/0           tcp spts:1024:65535 dpt:443

    Changing the WebAdmin to another port worked as well for me.

    Regards,
    Simeon
Reply
  • 0 in reply to Simon Shaw
    Hi All,

    Same problem here... I guess the following rule creates the mess...:

    Chain AUTO_INPUT (1 references)
     pkts bytes target     prot opt in     out     source               destination
        0     0 LOGDROP    tcp  --  *      *       0.0.0.0/0            0.0.0.0/0           tcp spts:1024:65535 dpt:443

    Changing the WebAdmin to another port worked as well for me.

    Regards,
    Simeon
Children
No Data
Cookie Information Banner