@Clive_A 

Testing all ports from a third-party web server indicates that all ports are closed. Actually, this is the problem - the router does not open the port despite the rule.

From SSH shows that the rule is enabled.

  @DVA_War 

you remove all relevant information so your screenshots make no sense.

remove some of the public ip not nearly all, remove parts of the mac and private ip have millions of others so there is no point in removing anything. how do you test that port forward does not work? when you test you must be on the internet on a different network than the one you have, you can for example turn off wifi on your phone to use mobile data to test.

if you try to test from the LAN on your router then there may be problems.

have you checked that you have the same WAN ip on the router as the one you have on your pc, go to whatip and see if you get the same ip as you have on the router.

try going to this page to see who's IP you get

You also need to check that you don't have any router ACLs that can block, look for WAN/in ACLs, if you have Switch ACLs then verify that nothing is blocking.
When testing I recommend disabling all ACL rules so that you are sure that is not the problem.

You also need to check that the firewall in your windows machine is not blocking, Windows blocks everything remote by default.

  @MR.S 

   If I leave my IP specified, I risk undergoing massive scanning of open ports and hacking attempts through this port.
Showing screenshots, I demonstrate the prescribed rules. I confirm that in all screenshots the ports correspond to the correct ones.
Will something give you their real meaning?

   I check that the port is not open trying to establish an RDP connection. I scan the open ports of the WAN address from the site.

Testing from the LAN, I check the operation of the redirection port and the operation of the RDP server.

From the LAN, I do not test the open WAN port, only the internal port. I test the external port from another Internet connection, not on the local network.

   Multiple computers are connected to the router. Going to the whatip site from any of them, I see the same external address.

   I don't have any rule ACLs. Technical support advised to disable all ALG - which was also done.

  @DVA_War 

When it comes to port forwarding, it's basically very simple, I haven't heard of any problems with this on any of the Omada routers in many years. So there must be a setting on yours that is preventing it from working. Here is an example of how to set up RDP to a PC, port 33380 is redirected to port 3389,

If that doesn't work, you need to look at how you have configured your router, it is mainly the WAN/in ACL that can cause problems.

  @MR.S 

   That's it - this is a basic simple function. And she doesn't work for me!

I set up a large number of different routers and never had any problems with forwarding. I am very surprised and disappointed in this device.
   I ask for help - maybe I'm missing something.

   The router was reset to factory settings. Configured to receive the Internet from the provider, DHCP is disabled (the ip address of the LAN DHCP server is specified in the settings) and a port forwarding rule has been added. That's all. There are no more settings.

   Check WAN port:

  @DVA_War 

there is no point in showing a screenshot when everything is censored away, at least show the port you are testing against. are you testing 3389 or is it the external port you are testing

  @DVA_War 

This tool doesn't work, port 18043 is open.

Do you have any country restrictions in ACL, I have all countries except my home country so that's probably why it's not working.

EDIT: I disabled country restrictions and then it worked and showed that the port is open

MR.S wrote

  @DVA_War 

 

there is no point in showing a screenshot when everything is censored away, at least show the port you are testing against. are you testing 3389 or is it the external port you are testing

 

  @MR.S 

   There are 2 ports in the redirection: an external WAN port and an internal LAN port.

   I changed the internal LAN port for RDP from the standard 3389 to another. It is registered in the computer firewall and it is used to check the operation of the RDP connection in the local network.

   I check the external WAN port for RDP by connecting from another provider or scanning the port. It is not like LAN port.

There are many sites for checking the port's openness. I used different sites for verification.

   There are no rules in the ACL of the router. Or are you talking about some other rules?

The RDP connection is made within the same city.

  @DVA_War 

DVA_War wrote

   Thank you all for your help! The issue has been resolved!

 

   On the advice of technical support, I turned on the DMZ and the internal port was also closed. At the same time, it was connected via LAN without problems. There was a problem in the settings of computer firewall rules. 

   It's always worse to redo after someone than to create your own...

As always, the firewall on the computer, which was written in the TS guide. 

Glad it's resolved anyway.