Remote Desktop under different network

[cashng]

How to remote desktop under different network, what are the ports need to forward?

I've have a computer at home and I would like to remote desktop, I've forwarded port 3389 to the destination computer in the router, but I still cannot remote. But when I am in the same network, I can remote.

Need help on this, I personally think that there is some settings I've overlook. My client computer is running win7 ultimate x86 build 7600, my destination computer is running the same version of OS. Please help~~ thank you

 

[osholt]

Hi, remote desktop can be very very tricky to setup manually. It's much easier to use a solution such as Windows Live Mesh or Teamviewer

If you have any queries don't hesitate to ask.

Oli

 

[Jonathan_King]

Welcome!

First, to eliminate as many factors as possible, disable any firewalls you might have.

Then, forward something like this:



The .35 part is my IP address. Modify that to match your computer's IP address.

 

[CommonTater]

Hi, remote desktop can be very very tricky to setup manually. It's much easier to use a solution such as Windows Live Mesh or Teamviewer

If you have any queries don't hesitate to ask.

Oli

Why... it's just more bloat --and win7 has tons of that-- and it offers no new functionality at all.

This is a settings problem not a capability problem.

 

[cashng]

I've forwarded 3389 tcp port in my router to the destination ip as what u did. but i still couldn't remote, I've stopped windows firewall too, however, i can connect the VPN, as well as ping to my ip. It works, but not remote desktop :shock:

 

[Jonathan_King]

Make sure the remote settings are configured like mine:



Also make sure your user is added to the allowed list.

On your client, disable any firewalls too.

 

[dajogejr]

Make sure the remote settings are configured like mine:

View attachment 65259

Also make sure your user is added to the allowed list.

On your client, disable any firewalls too.

That's what I was thinking...need to give rights to use RDP to users as well.

 

[cashng]

Make sure the remote settings are configured like mine:

View attachment 65259

Also make sure your user is added to the allowed list.

On your client, disable any firewalls too.

That's what I was thinking...need to give rights to use RDP to users as well.

I've done that too, file attached is the print screen that I've done under [Allow remote assistance], still no luck. I am thinking, could it be the ISP? is there any possibility on this?

 

[Jonathan_King]

Make sure to set a static IP on your host. The 35 can be replaced with just about any number you choose.



Now just to confirm, the syntax in Remote Desktop is your External IPort. If you don't enter any port number, it defaults to 3389, which is forwarded in your router.

 

[cashng]

I've done that steps too, I've also forwarded the port to the IP i've set. So if i don't forward any port, by default its 3389? :sarc:

 

[Jonathan_King]

No, you need to forward port 3389 to your computer. Here's what I mean: let's say I have 2 computers in my network, and I use RD for both. I could tell my router to forward port 3333 to one computer, and 3389 to the other. I would need to instruct the router to change 3333 to 3389 after it's forwarded.

Say my IP address is 66.67.111.111. Outside my network, to access computer 1, I would enter 66.67.111.111:3333.

To access computer 2: 66.67.111.111:3389

If you leave off the port, it automatically sends out the request on port 3389.

 

[cashng]

No, you need to forward port 3389 to your computer. Here's what I mean: let's say I have 2 computers in my network, and I use RD for both. I could tell my router to forward port 3333 to one computer, and 3389 to the other. I would need to instruct the router to change 3333 to 3389 after it's forwarded.

Say my IP address is 66.67.111.111. Outside my network, to access computer 1, I would enter 66.67.111.111:3333.

To access computer 2: 66.67.111.111:3389

If you leave off the port, it automatically sends out the request on port 3389.

I see, got it, thank you very much

 

[dajogejr]

Actually...that's half right...or half way there I should say.
The computer that is using port 3333 on the router would have the change the registry entry to listen for RDP traffic on port 3333...or the traffic wouldn't get to it. Even though you told the router to forward to a specific IP inside your LAN...RDP by default will listen to port 3389 on the computer.
This is how you change the listening port for RDP:
How to change the listening port for Remote Desktop

I sat there playing with a RDP app for my iPod for half an hour before I realized my brain fart...

 

[Jonathan_King]

Actually...that's half right...or half way there I should say.
The computer that is using port 3333 on the router would have the change the registry entry to listen for RDP traffic on port 3333...or the traffic wouldn't get to it. Even though you told the router to forward to a specific IP inside your LAN...RDP by default will listen to port 3389 on the computer.
This is how you change the listening port for RDP:
How to change the listening port for Remote Desktop

I sat there playing with a RDP app for my iPod for half an hour before I realized my brain fart...

You could always have the router change 3333 to 3389 before it sends it to the computer.

 

[dajogejr]

Too much work, IMO...
Here's a screen shot of what I mean, my setup in my router.
Not all routers may support that...either.

 

[Jonathan_King]

It's a bit easier with mine:

 

[dajogejr]

Very nice post...
I just have my ATT provided router/modem...no need for anything fancy...and I don't have a public/private programming option.
At work, I would program a Cisco PIX or ASA device to do what you're talking about...obviously a lot more options and keeps from having to customize and put your hands on PCs, when you can do it with hardware.
Central administration is the name of the game!!
If the user doesn't have the ability to port map inside/outside interfaces...he'll have to do my way.
If he does...go your way...

Good info JK.

 

[cashng]

these both are a very good way, thanks man, i will try it later when i am home, thank you all very much~

 

[cashng]

Before I had all settings well done on my home computer and tried to connect RDC, but failed. I had forwarded port 3389 but still failed. Until port 443, SSL port, is also forwarded. Then, I can remote desktop and connect to VPN from my work place, which is very far and reachable only by sea and air. I am not too sure, if these port443 is as important. Need to someone to correct me if I am wrong. Thanks guys.