Cisco NATT'ing Help Please

Can someone let me know if it’s possible to have a router forward RDP requests?

Basically, I’m trying to RDP from PC1, in London, with a private address of 192.168.1.2 to Windows Server in the Cloud in Washington, with a private address of 192.168.3.2. However, to connect to PC2 located in Washington, I need to connect via Internet router with public ip address of 74.187.125.6

At present, I’m connecting to PC2 from PC1 by simply assigning PC2 with the address 74.187.125.6/29 Gtw 74.187.125.7 and RDP directly from PC1 by putting in the address 74.187.125.6:3389 in RDP

However, I need to RDP to more than one remote PC, but I only have one public ip address. Therefore, I want to configure the router with the public address of 74.187.125.6 and have the router point my request to PC2 on port 3389.

Just so you know I have already purchased a publicly accessible router that I can assign an public ip address to.

I think it might be possible by natting the public address on the router, but not sure.

This should work:
On your Cisco router you need to create one to one static NAT assign for each port forward. So anyone who tries to access your public IP address on port some port will be redirected to specific device.

Please remember the router is already on the internet (which is opposite to how nat usually deployed). And the private addresses are trying to RDP to another set of private addresses that sit behind the router on the internet..

Please remember the router is already on the internet (which is opposite to how nat usually deployed). And the private addresses are trying to RDP to another set of private addresses that sit behind the router on the internet..

You have reversed logic in you network, WAN is inside.
In your case 192.168.0.2 is outside, and 64.XX.XX.XX is outside according to your configuration. So according to that
do #show ip nat translations
and rewrite nat translation according to that or change direction of NAT inside and outside interface.

In your case 192.168.0.2 is outside, and 64.XX.XX.XX is inside according to your configuration.

You can set outside and in any direction, depending in which direction you will do NAT.
Issue command #show ip nat translations and verify that NAT is operating as intended (what is inside and what is outside and adopt static NAT according to that). You can set

RDP uses both protocols (at least both are reserved for RDP).
:)
You don't need routing protocol (at least you should not need it).
I just tested NAT rules and redirection in GNS3 for telnet from port 3389 and 3388 to port23. This worked, I was redirected to different routers and I was able to log in. Some filtering on interfaces could interfere, but basically this should work.

We've almost cracked it. I have changed my configs, see attached. Now, when I try to RDP to remote desktop I get the following:
show ip nat translations
tcp 64.XX.XX.XX:3389 192.168.0.2:3389 86.6.44.221:5959 86.6.44.221:5959

Imagine you have a shopping list of items you need to get at the grocery store. You have two options:
A. Take one trip to the grocery store and get everything you need for the week, or
B. Take multiple trips, buying an item at a time, to achieve t…

In the world of WAN, QoS is a pretty important topic for most, if not all, networks. Some WAN technologies have QoS mechanisms built in, but others, such as some L2 WAN's, don't have QoS control in the provider cloud.

After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…

After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…