Have you forwarded TCP port 3389 on the router to the server? If so, it should be as simple as connecting your RDP client to 10.222.221.249.
Hello,
Trying to get a server to respond on an RDP session but is on another router
Server Config:
IP: 10.222.221.1
SBmask 255.255.255.0
Gtway 10.222.221.254
other router is the one that is allowing internet access here is the config on that
ip address 66.236.235.xxx 255.255.255.248 secondary
ip address 10.222.221.249 255.255.255.0
ip nat inside
no ip route-cache
no keepalive
speed auto
no cdp enable
How do I get this server to see an RDP coming from the public IP? Add the other gateway? 10.222.221.249?
Note: both ethernet cards on the routers are plugged into the same switch
Thanks
Joseph
Have you forwarded TCP port 3389 on the router to the server? If so, it should be as simple as connecting your RDP client to 10.222.221.249.
63,000 bugs in the code, 63,000 bugs,
ya get 1 whacked with a service pack,
now there's 63,005 bugs in the code!!
Hello Countach44,
Thanks for the reply,
I forwarded 3389 to 10.222.221.1 but I have a config issue at the moment.
Ok, it appears that the .249 is the gateway for the ethernet side of this router. Should I add this as an IP address or a gateway in the advanced settings in the NIC?
Here is what we have now
ip nat inside source list 1 interface Serial0 overload
ip nat inside source static tcp 66.236.235.xxx 3389 10.222.221.1 3389 extendable
ip classless
ip route 0.0.0.0 0.0.0.0 Serial0
ip route 10.222.223.0 255.255.255.0 10.222.221.132
no ip http server
Thanks
Joseph
Is the router where the RDP server reachable from the client?
63,000 bugs in the code, 63,000 bugs,
ya get 1 whacked with a service pack,
now there's 63,005 bugs in the code!!
Actually that is what I am trying to find out.
If I add this gateway 10.222.221.249 in the advanced section of the NIC then this should find the RDP port as the gateway knows this.
Haven't tried it yet just getting some feedback on it and maybe some help.
Thanks
Joseph![]()
I don't think it needs to be a gateway, it should just see it on the network since they have the same subnet. Try 'ping 10.222.221.249' from the client
63,000 bugs in the code, 63,000 bugs,
ya get 1 whacked with a service pack,
now there's 63,005 bugs in the code!!
Thanks for the reply,
I think you're right however I have goofed and added the public IP too. I am not at that location now but I will try this tomorow.
There is something that does make me think that it will not work though....
If I were to have two seperate PC's on a network and I had two routers faced to the internet with two seperate Public IP's and then set the LAN to say
192.168.1.1 and the other router to 192.168. 1. 2
Yes they are on the same network however if you wanted to RDP from the public IP that has a router IP of 192.168.1.2
You could still ping any gateway
You couldn't use the gateway of the other and vise vera. So this is why I was thinking gateway.
If you wanted to come in through the 1.1 router and go to the 1.2 router, you could use an ssh tunnel, provided you have an ssh server listening behind the 1.1.
ssh -L:[port]:192.168.1.2:3389 username@publicip
provided your 192.168.1.2 router is forwarding port 3389 to the RDP server, it should work. Just connect your client to 127.0.0.1:[port] (where port can be any open TCP port) after opening the ssh session.
63,000 bugs in the code, 63,000 bugs,
ya get 1 whacked with a service pack,
now there's 63,005 bugs in the code!!
Bookmarks