- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-24-2021 05:51 AM
Hi,
I configured port forwarding (on port 3389) on a Cisco C881-K9 V01 router (currently using Cisco IOS Software Release 15.4). It worked fine for a while, then stopped. Through console I went through the config and confirmed it was set up right. It surprisingly worked again for a while and again stopped (left me clueless).
I've tried to telnet to confirm whether the port is open from a remote network and the connection refuses. What could be the issue?
Solved! Go to Solution.
- Labels:
-
Small Business Routers
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-06-2021 11:01 PM
Thanks @marce 1000 and @Georg Pauwen. I found out the problem was I forgot to save the changes I'd made to the config to allow for remote desktop connection. When there was a power blackout (happens frequently here in Kenya) and the UPS was faulty, then the console reset back to the initial config.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-24-2021 09:37 AM
- Could be a bug , you may try with a Suggested (software) Release for this platform.
M.
-- Each morning when I wake up and look into the mirror I always say ' Why am I so brilliant ? '
When the mirror will then always repond to me with ' The only thing that exceeds your brilliance is your beauty! '

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-24-2021 09:57 AM
Hello,
hard to tell what is causing this. You could try and exclude the static 3389 translation from the dynamic NAT. Below is an example (IP addresses are arbitrary):
ip nat inside source static tcp 192.168.1.10 3389 interface GigabitEhernet0/0 3389
ip nat inside source static udp 192.168.1.10 3389 interface GigabitEthernet0/0 3389
ip nat inside source list 101 interface GigabitEthernet0/0 overload
!
access-list 101 deny tcp host 192.168.1.10 any eq 3389
access-list 101 deny udp host 192.168.1.10 any eq 3389
access-list 101 permit ip 192.168.1.0 0.0.0.255 any
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-06-2021 11:01 PM
Thanks @marce 1000 and @Georg Pauwen. I found out the problem was I forgot to save the changes I'd made to the config to allow for remote desktop connection. When there was a power blackout (happens frequently here in Kenya) and the UPS was faulty, then the console reset back to the initial config.
