This is a continuation of my previous thread, as seen here:

https://community.tp-link.com/en/business/forum/topic/622434?replyId=1254500

Some personal issues that meant I had just lived with this not working, but I am now back to trying to solve the issue.

The Router works perfectly in standalone mode only.

As soon as it is adopted, I am unable to open any ports.

I have confirmed the server in question does not change IPs when the router is adopted, the server has been manually configured to take the ip 192.168.0.30 and not to use DHCP.

I have since updated my controller to the latest software (v5.13.30.8) with no change in the situation.

Multiple factory resets of the router have been tried.

I have tried opening ports to other machines on the network, which again works perfectly in standalone mode but fails utterly post adoption.

I have also noted that when adopted despite configuring it the router also fails to update its No-ip DDNS, while this works perfectly in standalone. From this I suspect that the controller is somehow failing communicate the settings to the router, but that's just a conjecture.

All the issues are reproducable 100% of the time on my network, I can restore everything to full functionality simply by having the router in standalone mode and it will all fail every time as soon as the router is adopted. Happy to provide any screenshots or logs that could help diagnose these issues.

Please help.

All the best,

Tom