Port Forwarding Good/Bad!

Hi, and welcome to the UTM Community!

Please Edit your original post, and insert your images into the post. We can't know if imgur is properly protected. The only malware I've gotten in over 10 years was from an external link to a picture in this forum several years ago.  Thanks in advance!

I obviously can't critique your config at the moment[;)], but I would take a different approach.  I don't like opening ports to the world, so my recommendation would be to configure a Remote Access method and to use that instead of a DNAT.  I prefer the SSL VPN.

If you want to figure out what's going wrong here, it's probably #3 or possibly #4 in Rulz.

Cheers - Bob

I just updated my original posting with a picture included :)

I was thinking of setting up a SSL VPN regardless but I currently have a site-to-site VPN router that I want to allow into the network but the traffic keeps getting dropped its an IPSEC setup. I always see the connection being attempted port 500 but the firewall kills it. :(

Thanks for the pic - I can see that #4 isn't violated, but how about #3 in Rulz for "Efraim Desktop?"

Please start a thread in the VPN forum to ask about your site-to-site.

Cheers - Bob

Here is my desktop it doesnt look like it violating #3 ?

If your desktop has the IP of "Internal (Address)" as its default gateway, then I think we can eliminate routing as the cause of the problem.

In 'Network Protection >> Firewall', select "All" instead of "User-created firewall rules" at the top.  Edit the one related to your NAT rule and activate logging.  If the firewall is allowing forwarded packets to your desktop, then you have a problem in the desktop.

Cheers - Bob

I am still stumped because for whatever reason its still blocking via internet to RDP but locally it works, I will setup an SSL VPN to be able to connect locally.

I was able to allow my media server to be connected via internet so I have the proper config setup :)

When I tried to connect via RDP using my public IP it fails but when I check to see if the port is open it says the ports open

I am still stumped because for whatever reason its still blocking via internet to RDP but locally it works, I will setup an SSL VPN to be able to connect locally.

I was able to allow my media server to be connected via internet so I have the proper config setup :)

When I tried to connect via RDP using my public IP it fails but when I check to see if the port is open it says the ports open

Did you edit the automatically created rule in 'Firewall' so that you can see in the Firewall Live Log if the packet is going to your PC?

I still think your description indicates that the PC does not have the UTM as its default gateway.  Try replacing the DNAT with a Full NAT that changes the Source to "Internal (Address)."  If that solves the problem, we've proven that the PC doesn't have the UTM as its default gateway.

Cheers - Bob