Overclock.net › Forums › Software, Programming and Coding › Networking & Security › Enabling RDP over IP?
New Posts  All Forums:Forum Nav:

Enabling RDP over IP? - Page 2

post #11 of 26
Thread Starter 
Quote:
Originally Posted by Riou View Post
DynDNS is for when your external IP address changes like I said in my prior post.

Lets say your external IP address is 1.1.1.1. I am trying to connect to your server and it works. Then a week later, your ISP changes your external IP address to 2.2.2.2. I cannot access your server because I still think you are on 1.1.1.1.

DynDNS keeps track of this external IP address change. Instead of me trying to connect to 1.1.1.1, you make a hostname called myserver.dyndns.org. I use myserver.dyndns.org to connect to you instead.

Now when your external IP address changes, myserver.dyndns.org will go to 2.2.2.2 instead of 1.1.1.1 like before.
Thanks for the explanation. That makes it much easier to understand now. How does it keep track of the change? Is it something you install on your computer that sends information back to the original website?

Would having a static IP eliminate the need for this service? (I would assume obviously, but I have to ask.)
post #12 of 26
Quote:
Originally Posted by xyeLz View Post
Thanks for the explanation. That makes it much easier to understand now. How does it keep track of the change? Is it something you install on your computer that sends information back to the original website?

Would having a static IP eliminate the need for this service? (I would assume obviously, but I have to ask.)
You enter in your account information into your FIOS router. The router sends this information to DynDNS, and DynDNS updates the IP address of the hostname you created.

Yes if your external IP address was static, there would be no need for DynDNS.
Edited by Riou - 7/29/11 at 7:27am
post #13 of 26
Thread Starter 
Thanks for the help. Repped.

So it does not matter what I make the external port in my router settings, as long as the internal port is 3389 for the RDP? I can make the external ports 100, 200, and 300 if I wanted to - or do they need to be in the range of 339x?

Do static and dynamic IP addresses apply to both public and private IPs? If I'm using DHCP and my router shuts off (which does happen frequently), both my private (192.168.1.3) and public IP will be changed?
Edited by xyeLz - 7/29/11 at 8:17am
post #14 of 26
Quote:
Originally Posted by xyeLz View Post
So it does not matter what I make the external port in my router settings, as long as the internal port is 3389 for the RDP? I can make the external ports 100, 200, and 300 if I wanted to - or do they need to be in the range of 339x?
Yes, when you port forward, it opens up a port in the router's NAT table so an Internet computer can access your computer. Your computer likely has a software firewall on, so you have to configure the software firewall to allow the port/application through.

TCP port 3389 is the default port for Microsoft RDP. If you configure RDP to use a different port, you have to also use that same for port forwarding in your router accordingly.

Quote:
Do static and dynamic IP addresses apply to both public and private IPs?
Yes they do apply to public and private IPs. However, you are only in control over your private (internal) IP addresses and whether they are dynamic (DHCP) or static. Your ISP controls the public (external) IP address. Most ISP set your external IP to dynamic.

The default internal IP address range for FIOS routers is 192.168.1.1-192.168.1.254. Your external IP address is given to you by Verizon. It will be something else. A website like http://www.whatismyip.com/ will tell you your external IP.

Quote:
If I'm using DHCP and my router shuts off (which does happen frequently), both my private(192.168.1.3) and public IP will be changed?
The DHCP server on your router and the external IP address that Verizon grants you are on a lease time. If your computer/router does not renew the lease within the lease time, you may get a different IP address.

For example, if Verizon says your external IP address is 173.1.1.1, you may lose that address if your router does not renew in time. Your IP address may change to 173.1.1.99 if someone else' FIOS router gets your old 173.1.1.1 address.

Now for the DHCP server on your router. Your router gives your laptop an internal IP address of 192.168.1.50. If your laptop is off and does not renew within the lease time, it may get a different IP address like 192.168.1.61 if your Xbox360 decides to take your old 192.168.1.50 address.
Edited by Riou - 7/29/11 at 8:20am
post #15 of 26
Thread Starter 
Thanks Riou. You've been really generous in helping me with my issues and all input is greatly appreciated.

It appears as if the logical thing to do here would get a free DynDNS name and use that for the time being.

Just a quick final follow-up on my first and second questions:

I will forward port 3389 to allow for RDP.

Sorry for the confusion, but are you saying that the external port can be anything as long as the internal port matches 3389 (RDP)? Or were you saying that the external IP has to be within 339x? My question is because I have two computers I want to set up, so they will both be using different ports if I am not mistaken to represent which is which?

As for the static and dynamic IP addressing process, so if I change my IP to static, I am only changing my private IP and vice versa for dynamic? Changing my IP to static does not affect my public IP and it will remain as dynamic? If so, I would NEED DynDNS anyways as it takes my public IP, right?
post #16 of 26
Thread Starter 
I opened port 3389 and set up a DynDNS. Whenever I try to connect to the computer via IP doing xx.xx.xx.xx:3389, it takes a long time and eventually tells me it could not connect.

When I try to connect via the DynDNS, it instantly says "Remote Desktop can't find the computer "xx.dyndns.org". This might mean that "xx.dyndns.org" does not belong to the network..."

I did an NSLOOKUP and it is indeed pinging the correct IP, without the port at the end so it looks like xx.xx.xx.xx.

Any suggestions?

EDIT: Now the DNS is functioning the same as the IP. It will show that it is attempting a connection, but then tells me it can't connect. Any ideas? Did I do something wrong setting it up in the router? Am I connecting wrong?
Edited by xyeLz - 7/29/11 at 10:28am
post #17 of 26
Okay, this is what you need to do.

This is how I setup on my router under port forward:




I selected the name of my computer "P6TD-PC" and it has an IP address of 192.168.1.75. Port forward the destination address TCP port 3889. This is the computer we want to RDP into.





Under Remote Desktop Connection, set the server name to connect to be:
hostname.dyndns.org:3889



hostname is the name for what you set on the DynDNS website for your router's external IP address. There were several options, but I chose dyndns.org for simplicity since the FIOS router defaults to that. 3889 is the TCP port you set for port forwarding in your router.

Click connect and you should be able to then enter in your user account name and password for the computer you want to connect to. Another message about a certificate warning will pop up. Just check the box to the left to allow and click okay.

You have now RDP into your computer over the internet.

If you have a second computer you want to RDP into, pick another port to forward in your router and use that second computer's IP address. Instead of port 3889, pick something like 3900.

To RDP into the second computer, use hostname.dyndns.org:3900 for the server name in Remote Desktop Connection.

Basically the port you assign in port forwarding will direct Remote Desktop Connection to the corresponding computer.



Edited by Riou - 8/2/11 at 12:16am
post #18 of 26
Thread Starter 
Thanks again.

I followed you every step except for when it asks for username and password. At home on the private IP, I would do that, get through the worthless security measures, and be in.

Through the Internet, it won't get to that stage. It just says I can't connect, it's not available. It tells me to make sure the PC is on, has it enabled, etc. Which it does because I can still connect internally.

In my router settings there was no option for TCP so it automatically did it for both TCP and UDP.

Am I missing something?

\\\\Sent from my iPhone\\
post #19 of 26
Quote:
Originally Posted by xyeLz View Post
Thanks again.

I followed you every step except for when it asks for username and password. At home on the private IP, I would do that, get through the worthless security measures, and be in.

Through the Internet, it won't get to that stage. It just says I can't connect, it's not available. It tells me to make sure the PC is on, has it enabled, etc. Which it does because I can still connect internally.

In my router settings there was no option for TCP so it automatically did it for both TCP and UDP.

Am I missing something?

\\\\Sent from my iPhone\\
Are you using your own DynDNS address?
Edited by Riou - 7/29/11 at 12:01pm
post #20 of 26
Thread Starter 
I used acoolname.dyndns.org because it looked the most professional out of the bunch. I just picked a random word for the actual subdomain in the DNS name.
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Networking & Security
Overclock.net › Forums › Software, Programming and Coding › Networking & Security › Enabling RDP over IP?