01-26-2021 08:22 AM
01-26-2021 09:49 AM
You say that 3389/tcp is working just fine? I'm assuming that you only did it for testing and then removed the configuration?
Can you verify that 8920/tcp is allowed on whatever that host on the inside is? Sometimes the host firewall is the culprit and not the actual configuration of the router. You can verify that the translation is working by performing the following command:
show ip nat statistics
Look for increasing numbers on the "Hits".
01-26-2021 12:07 PM
01-26-2021 03:15 PM
Hello,
you could try and block the port from being used for overloading:
ip nat settings interface-overload block port tcp 8920
01-27-2021 03:35 AM - edited 01-27-2021 03:35 AM
Hello
Is the nat device open for tcp 8920?
Try removing the static route pointing your lan subnet via it wan interface and also remove that specific host from the global NAT
no ip route 192.168.16.0 255.255.255.0 Dialer1
ip access-list extended 100
10 deny tcp host 192.168.16.240 any eq 8920
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide