simple rdp Port Forward - NAT not working

[astar]

Just deployed OPNSense 16.7.r2. A simple rdp port forward isn't working. I've attached port forward screenshot.
(OPNSense and my test Windows machines are running on separate VMWare hosts). As this is my test lab, on WAN interface, tick mark removed for "Block private networks" and "Block bogon networks".

Replaced OPNSense with pfsense (same environment) and rdp port forward is working.

[domg]

Hi,

Do you have block on log page ?

[syd]

Hey,

What sort of adapters are you using in your OPNsense VM, i had troubles with the VMX Adapters, beter to use the e1000. Had exactly the same problem yesterday made a new VM but now with e1000 and all working fine now.

Syd

[astar]

Thank you for looking into. Nic used is e1000.
I have attached the image of firewall log view, rdp connection is initiated from 172.17.1.12 to OPNSense wan ip 172.17.1.25 (port forward is configured as shown in my first post).

[syd]

Can you try moving the wan side out of a private adres range ?
I had the same problem with lan & wan sitting in privatte adres ranges even with the "block private adresses" unchecked. Never bothered to find out what went wrong. Anybody figured it out ?

[astar]

syd,

I don't have additional wan ip hence I can't move my wan from private ip range to true public ip.  :(

[Julien]

I am having exactly the same problem.
its not a routing or adapter issue, because I tried it with both E1000 and VMX3 none of them works.
hopefully someone can give us a hand here.

[franco]

We have had a bit of internal discussion... does this work when the option "Disable reply-to" is enabled under Firewall: Settings: Advanced?

[BlackDragon381]

Have the same issue, Proxmox KVM, Intel e1000.
Anybody know how to solve this problem?

[BlackDragon381]

Now I use 17.1.1, but port forwarding still don't work!