Koozali.org: home of the SME Server

Port forward not working

Offline Daniel B.

  • *
  • 1,699
  • +0/-0
    • Firewall Services, la sécurité des réseaux
Re: Port forward not working
« Reply #15 on: April 01, 2017, 02:49:27 PM »
As for iptables output, use iptables -L -vn if you want more details
C'est la fin du monde !!! :lol:

Offline DanB35

  • ****
  • 764
  • +0/-0
    • http://www.familybrown.org
Re: Port forward not working
« Reply #16 on: April 02, 2017, 01:46:25 AM »
...and it's somewhat orthogonal to the original question, but it looks like you're trying to connect to two different computers via RDP from the WAN.  I have no idea how secure RDP is (though I don't think I'd be optimistic), but a completely different way to address this, that would certainly work, and would almost certainly be more secure, is to set up a VPN connection--I like OpenVPN, but there are a few different contribs for VPNs.  That way, you can simply connect to the desired remote IP address using your client machine.
......

Offline CharlieBrady

  • *
  • 6,918
  • +3/-0
Re: Port forward not working
« Reply #17 on: April 02, 2017, 01:57:27 AM »
Multihoming must be managed on your final box, that's not an SME Server issue. My guess (which you can verify using wireshark or tcpdump) is that connections going to 10.0.0.3 are replied by your w2k8 box using 10.0.0.2 IP address. Can you explain why you want to different IP addresses here ?

I agree that this is likely a win2k problem.

Offline CharlieBrady

  • *
  • 6,918
  • +3/-0
Re: Port forward not working
« Reply #18 on: April 02, 2017, 02:03:57 AM »
My guess (which you can verify using wireshark or tcpdump) is that connections going to 10.0.0.3 are replied by your w2k8 box using 10.0.0.2 IP address.

If that is the case, the return traffic would be dropped by iptables, and logged in /var/log/iptables/current.

Offline chuzz

  • 9
  • +0/-0
[solved] Port forward not working
« Reply #19 on: April 02, 2017, 04:15:13 AM »
To all who have taken time to respond, thank you. The issue has been resolved.

Turns out it was actually my fault - the firewall on the remote workstation I was trying to connect from was blocking it. So I offer my humble apologies to all those who wasted time thinking about what could be wrong.

 :oops:

The reason I never thought to check the firewall on the connecting box (my firewall) was because it used to work before I installed sme in the remote site. It seems I had manually added the firewall rules to allow ports 10002 & 10003 out (so it used to work before sme was installed) and then thought I had better add them to the firewall startup script. At some stage I rebooted my firewall. Turns out I had only added port 10002 to the startup script. D'oh.

PS. For those interested, the reason for 2 IPs on the win2k8 box is 1) the box has 2 built-in NICs to start with, and 2) it runs hyper-v so I channel the VM traffic out the 2nd NIC.

[edit] add embarrassment
« Last Edit: April 02, 2017, 04:41:10 AM by chuzz »