Topic: Port forwarding for internal web server

[Hemeltje]

I have a web server listening to port 8040 behind SME.
The web server works ok when I use a simple hardware router (D-Link, SMC, USR, all work ok).
But not with the sme server!?
In the server-manager I created a port forwarding rule that redirects all TCP/UDP to webserver:8040.

What's going wrong?

Peter

[briank]

Should work fine - are you using the portforward contrib? You can easily check the firewall rules with the masq-manager contrib. I guess you are sure you have the correct ip for the webserver
Regards
Brian

[Hemeltje]

Brian

Is a portforward contrib needed for 6.0.1-01?

Peter

[briank]

Hi - what I mean is did you do the portforward from the server-manager or try to write a firewall rule?
Cheers
Brian

[Hemeltje]

Yep!
TCP - 8040 - 192.168.0.12 - 8040

I guess I do better a complete new install and try again on a clean server.

[jackl]

Peter,
It is port 80 you are forwarding to the webserver listening on 8040?

Jack

[Hemeltje]

Jack

The router is listening on port 8040 and forwarding to the same port 8040 on the webserver (192.168.0.12).
This works with USR router.
Now I try this with SME server but I get:

...
The following error was encountered:

Connection Failed
The system returned:

    (111) Connection refused
...

Any idea?

Peter

[briank]

If you throw on Muzo's firewall management contrib you could check the rule has been created - it should show up under NAT Chain PortFowarding. You can also list the rules at a command prompt with iptables -L and use Shift Pageup & Down to scroll.Otherwise I'm out of ideas.
Cheers
Brian

[Hemeltje]

I found this:

Chain PortForwarding_1404 (1 references)
target prot opt source destination
DNAT tcp -- anywhere anywhere tcp dpt:8040 to:192.168.0.12:8040

So it should work, I suppose? But it doesn't! (and internal - http://192.168.0.12:8040 works fine)

I'm out of ideas...

[briank]

Hemeltje - did you ever get this working?
Brian