11-15-2014 02:20 PM - edited 03-05-2019 12:10 AM
Solved! Go to Solution.
11-16-2014 09:32 AM
Just to be clear, you're testing your inbound port forwarding from a machine that's physically on the 192.168.0.0/24 network, correct?
11-16-2014 09:34 AM
No, I am trying to connect from an other network. Like the neighbors, work area, the office,
Thanks
11-16-2014 09:39 AM
Let's keep it simple for starters and try connecting directly from the 192.168.0.0/24 network. If that works, the configuration on the Cisco is good.
Given that you're using a 192.168.0.0/24 address on your WAN interface, I suspect that both your upstream router and your Cisco are doing NAT. If so, you will need to do port forwarding on the upstream router.
11-16-2014 09:45 AM
Hello,
Sorry for my bad knowledge..
I am now on a device 192.168.0.227 trying to connect to 20.30.40.53:3389
This does not work. I also can not ping 20.30.40.1 from here.
From my 20.30.40.53 machine I can ping 192.168.0.0 range.
11-16-2014 09:51 AM
From the 192.168.0.0/24 network, you want to try to connect via RDP to the WAN IPv4 address of the Cisco, which I think was 192.168.0.114, but you'll want to verify that.
Just as a side note, if you're doing port forwarding, you may want to set a static IPv4 address on the WAN interface rather than use DHCP.
11-16-2014 09:54 AM
My WAN interface now has the static ip of 192.168.0.114
from the 192.168.0.0/24 network I cannot open a RDP to the wan IPv4 Adress.
What I just want to do is.
Open an RDP session to 20.30.40.53 from an other location outside my country.
As I cannot ping 20.30.40.1/24 range from 192.168.0.0/24, is their an IP route command not given correct?
11-16-2014 10:14 AM
Alright. Let's go back to basics then.
You have a Cisco 1941 router with a 192.168.0.114/24 WAN address and a 20.30.40.1/24 LAN address.
You have an ISP router (most probably performing NAT) with a public WAN address and a 192.168.0.1 LAN address.
You want to be able to reach the 20.30.40.53 host from the Internet, but are having difficulties due to the complexity of having two NAT routers in the path.
The simple solution to what you're trying to accomplish, assuming no other requirements, is to change the LAN address of the ISP router to 20.30.40.1, do the port forwarding on that router and take the 1941 out of the picture.
For the record. You really should change 20.30.40.0/24 to 10.30.40.0/24. The 20.0.0.0/8 network really shouldn't be used internally.
11-16-2014 10:21 AM
Hello,
Thanks for ur work..
Sad enough here in Belgium we cannot change the ranges/ip of our ISP router.
Now I really want to port forward on my cisco 1941..
Do u have any tips/tutorials?
Thanks still...
11-16-2014 10:24 AM
Does your ISP router allow you to do port forwarding? Also, does it allow you to set static routes? Without that first one, port forwarding on your 1941 won't work because there won't be a way to get the traffic to your router in the first place.
11-16-2014 10:30 AM
Our ISP does support portforwarding, also DMZ can be given. For devices that need direct acces to the internet.
It also support static IP routes. Before the Cisco I had a C7 TP Link, everything I portforwarded there was not a problem and got picked up instantly.
Thanks in advance
11-16-2014 10:35 AM
Okay, let's set your ISP router's DMZ to the Cisco's WAN address and continue from where we were.
11-16-2014 10:39 AM
DMZ IP address: 192.168.0.114/24
What now?
11-16-2014 10:49 AM
Ultimately, this is what needs to happen.
Internet traffic needs to flow to your ISP router, which will "DMZ" forward everything it doesn't have a NAT entry for to 192.168.0.114. It doesn't need any kind of routing for this because 192.168.0.0/24 is directly-connected.
Your Cisco 1921 needs to forward traffic from its WAN interface's 3389/tcp port to 20.30.40.53's 3389/tcp port. It also needs to have a static route to the Internet via 192.168.0.1, which it already has. No other routing needs to be configured because everything else is directly-connected.
Relevant configuration is as follows:
interface GigabitEthernet0/0 ip address 192.168.0.114 255.255.255.0 ip nat outside ! interface GigabitEthernet0/1 ip address 20.30.40.1 255.255.255.0 ip nat inside ! access-list 100 permit ip 20.30.40.0 0.0.0.255 any ! ip nat inside source list 100 interface GigabitEthernet0/0 overload ip nat inside source static tcp 20.30.40.53 3389 interface GigabitEthernet0/0 3389 ! ip route 0.0.0.0 0.0.0.0 192.168.0.1
The inside machine should use address 20.30.40.53, subnet mask 255.255.255.0 and gateway 20.30.40.1.
It looks like I typoed the 3389/tcp forwarding command earlier in the conversation and had things running off of the wrong interface. It's corrected in the commands above.
That should make everything work.
11-16-2014 10:57 AM
Hello Sir,
When I try to enter this command:
ip nat inside source list 100 interface GigabitEthernet0/0 overload
it says: %Dynamic mapping in use, cannot change
What to do now?
11-16-2014 11:02 AM
This only means that the command is already in the configuration. As long as all of the commands above are present in the configuration when you're done, everything should be fine.
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