11-15-2014 02:20 PM - edited 03-05-2019 12:10 AM
Solved! Go to Solution.
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 11:11 AM
That will do it.
I'm glad I could be of help. If you could rate any more helpful comments and mark one or more as correct, I would appreciate it.
11-15-2014 03:43 PM
You should be able to do this with the following command:
ip nat inside source static tcp 20.30.40.x 3389 interface GigabitEthernet0/1 3389
Once this is in place, connections to GigabitEthernet0/1's dynamic IPv4 address on 3389/tcp will forward to 20.30.40.x on 3389/tcp.
11-15-2014 04:14 PM
Does not work.
So to be clear, what I am trying to do, is connect to the 20.30.40.* by coming from an extern connection. In another building other network. a standard RDP session.
thanks in advance
11-15-2014 04:54 PM
What result do you get when you attempt to connect to the GigabitEthernet0/1 address on 3389/tcp from a machine on the 192.168.0.0/24 network?
Also, can you telnet to 20.30.40.x on 3389/tcp from the router using GigabitEthernet0/1 as the source?
11-16-2014 01:53 AM
Hello,
I don't know how I can test the connectivity on that exact port :/
What I can do is acces the router from the 192.168.0.0 range.. (http only)
Thanks in advance..
11-16-2014 08:07 AM
From a machine on 192.168.0.0/24:
telnet 192.168.0.a 3389
From the router:
telnet 20.30.40.a 3389 /source GigabitEthernet0/1
11-16-2014 08:15 AM
Thanks, output:
From the router: Connection timed out. remote host not responding.
From a machine: does not work also..
So I don't really see the problem.. :/
11-16-2014 08:20 AM
Looks like it might be a gateway issue on the host or a firewall problem.
Do these work from the router?
telnet 20.30.40.a 3389
ping 20.30.40.a
11-16-2014 08:27 AM
telnet 20.30.40.a 3389 - ... open
ping 20.30.40.a - works from the 20.30.40.1 router
still I can't connect via rdp to the machine.
from an external server ofc.
So I think; when i RDP to my ISP's IP: **.*.***.**:3389 it does not route correctly?
11-16-2014 09:05 AM
This definitely sounds like a gateway problem. Can you check the machine you're forwarding to and make sure it has a correct default gateway and subnet mask? The fact that you can ping from the LAN interface of the router, but not from its WAN interface is telling.
11-16-2014 09:13 AM
My gateway is 192.168.0.114, right?
When I test via open port, port 3389 is not open..
Thanks in advance!
11-16-2014 09:19 AM
No. The gateway has to be on the same subnet, so it should be 20.30.40.1.
11-16-2014 09:20 AM
Tried that, not working...
It's strange, the port isn't open on my WANIP
11-16-2014 09:24 AM
The port is forwarded, but if there's nothing answering at the other end, it won't be open. So the target machine has 20.30.40.x as an IPv4 address, 255.255.255.0 as the subnet mask and 20.30.40.1 as the gateway? Can it successfully connect outbound to the Internet?
11-16-2014 09:29 AM
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