Can route RDP traffic, but not ModbusTCP

I’m learning how to configure networks with a RB2011iL-IN. From a factory default state, I have added the NAT rule to allow the remote desktop protocol through. I have a PC behind the MT router (WAN IP 192.168.0.2, LAN IP 192.168.88.2) and can successfully access it via remote desktop with this command

/ip firewall nat
add chain=dstnat action=dst-nat protocol=tcp dst-port=3389 to-addresses=192.168.88.2 to-ports=3389

I also have a device behind the MT that speaks ModbusTCP. I normally connect to it via opening a TCP socket on port 502. Therefore, I would have expected this command to work exactly the same way for this device:

/ip firewall nat
add chain=dstnat action=dst-nat protocol=tcp dst-port=5020 to-addresses=192.168.88.2 to-ports=502

In other words, from outside the MT router I would like to connect to the device by opening a TCP socket on 192.168.0.2 port 5020, which should route all traffic to the device that is expecting a connection on port 502.

    1. Can anyone explain to me possible reasons why this doesn’t work the way I would expect it to, especially given the fact that the remote desktop protocol worked fine?


    1. Since I know that the destination recipient should always be the MT router (192.168.0.2), should I always set the dst-address to 192.168.0.2?