n00b: Does RDP Require Static IP

Cannibal Corpse

[H]ard|Gawd
Joined
Sep 22, 2002
Messages
1,285
Hey all,

I need to know what are the requirements for a remote desktop connection from work to home: Am I required for a unique static IP if I want to RD to my home PC from work? (accessing from a public IP to Internal IP).

What is the best setup for this purpose? (server, etc. recommendation)

What about PCAnywhere solution?

Thanks in advance.
 
well with rdp you need to know the IP address of the targeted machine.
so if you have a dynamic ip on that computer then i would suggest you to try out dyndns.
the dyndns program updates itself with the server and gives you a hostname.
you dont really need a server for rdp, just make sure you forward the ports if you are bahind a router. the port is 3389
as for pc anywhere, i havent tried it so i cannot say.
 
Thanks for your input, when you say I don't need a server, does it mean I can rdp from one XP Pro (Work) to another XP Pro (Home)? That would be cool, I was always under the impression that a server (possibly 2000 or 2003 RD2) would facilitate the rdp capabilities.

Thanks again.
 
Cannibal Corpse said:
Hey all,

I need to know what are the requirements for a remote desktop connection from work to home: Am I required for a unique static IP if I want to RD to my home PC from work? (accessing from a public IP to Internal IP).

What is the best setup for this purpose? (server, etc. recommendation)

What about PCAnywhere solution?

Thanks in advance.

I think theres enough of this software out there that no matter what your configuration you can still get around whatever barrier, save a complete lack of Internet and electricity. If your home PC is directly connected to the DSL/Cable Modem/Normal Modem/whatever, you should have an external facing IP address, seen via ipconfig would be something that does not begin with 192. or 10. (theres others I believe but I can't think of any routers that use them). If you are hooked up to a NAT gateway/router, then you would have an internal IP address and the router would have the external IP address. If you are hooked up to the gateway with NAT, you will either need to forward the IP address (see your routers manual for configuration) or list your machine as the DMZ (not suggested). Unless RDP catastrophically fails behind a NAT that would probably work. Then all you would need is as just noted while I'm writing this, the known external IP address of your home computer. I'd suggest (as listed) a dynamic ip address program (as once again listed).
 
Cannibal Corpse said:
Thanks for your input, when you say I don't need a server, does it mean I can rdp from one XP Pro (Work) to another XP Pro (Home)? That would be cool, I was always under the impression that a server (possibly 2000 or 2003 RD2) would facilitate the rdp capabilities.

Thanks again.

I believe every XP release has RDP included (XP Pro definitely does), though I could be wrong. It should be somewhere in the accessories part of the start manu IIRC.
 
Would you kindly let me know how does dyndns works? Is it s 'free' service (at least for my purpose), how do I utilize their services?

Here is my configuration by the way:

Cable modem subscriber, behind a Motorola Cable Modem, using a D-Link DGL-4300 Router. (dynamic service).

Thanks!
 
it is a free service. all you need to do is register and follow the directions, they will let you setup a free host like NAME.dyndns.com, and the software should update your current ip, whether it be dynamic or not ot the hostname.
hope that helps
 
hokatichenci said:
I believe every XP release has RDP included (XP Pro definitely does), though I could be wrong. It should be somewhere in the accessories part of the start manu IIRC.
XP Home doesn't let you connect to it remotely, but does have the RDP client so you can connect to other machines. MCE and Pro both allow incoming connections.
edit: beaten to it
 
Thanks for all the inputs and being so patient with my (n00b! :D ). The thing that I want to know is that when I am at work, how can I possibly check my home's IP address? (using the suggested links) (doesn't it change because it is dynamic?)

Of course I can check it when I am home, but next time I go to work, wouldn't it be a different IP address?

Thanks for your patience with me! :D ;)
 
You can do a ipconfig from command, or go into the router
If you are using a router, you will have to open the port for RDP.
Also make sure that your firewall allows it as well
And if you have a Dynamic IP from a router with a Static IP from the your ISP
Check into www.no-ip.com and setup a account and download their updater program
I use it and works great :D
 
Cannibal Corpse said:
Thanks for all the inputs and being so patient with my (n00b! :D ). The thing that I want to know is that when I am at work, how can I possibly check my home's IP address? (using the suggested links) (doesn't it change because it is dynamic?)

Of course I can check it when I am home, but next time I go to work, wouldn't it be a different IP address?

Thanks for your patience with me! :D ;)


It depends on each ISP retention policies. Some will give you a IP for a few days, others for only a few hours. But most times, if you note the IP before leaving for work, it's almost guaranteed it's the same IP during your work day.

otherwise, check DynDNS for a way to learn the IP anywhere.
 
Cannibal Corpse said:
Of course I can check it when I am home, but next time I go to work, wouldn't it be a different IP address?

For most ISPs the dynamic part means it could change whenever they want... in practice I know with Comcast I had the same IP for 2 years straight.

If your ISP changes your IP more often you can download a small program from places like DynDns.org and it will check your current IP (every X number of hours/days) and then update DynDns with your new information.

Then all you need to do is use the DNS name you picked out whatevernameyouwant.mine.nu (or whatever it is) with Remote Desktop client and it will direct you to your home system.
 
DragonNOA1 said:
You can download the client to any modern M$ OS.
Or set up the server with iis and connect to it from a browser w/ activex.
 
Xilikon said:
It depends on each ISP retention policies. Some will give you a IP for a few days, others for only a few hours. But most times, if you note the IP before leaving for work, it's almost guaranteed it's the same IP during your work day.

otherwise, check DynDNS for a way to learn the IP anywhere.

thats what is nice with no-ip the program updates itself every time you login so if your ip changes it updates the website, so you just goto your dns and not the ip. Its very nice
 
Your D-Link DGL-4300 router supports Dynamic DNS updates.

Its on page 50 of the manual if you download it from the D-Link web site. No client software required on your PC. Almost every Home "router" on the planet released in the last 4 years has support for DynDNS built-in.
 
I do this all the time. It's not really that hard. Basically, you need to:

1. Enable RDC on your XP Box at home (My computer/properties/remote/Remote Desktop).
2. Set your XP Box to a static IP Address within your NAT address space (make sure it doesn't confict with DHCP).
3. In your router, route port 3389 (the RDC port) to the static set in your XP Box.

Now, as for your WAN IP Address. There are two ways around this...

First, you could go the DynDNS route as others have suggested.

If you don't want to bother with this, there are a couple of utilites out there that will email you your WAN side IP address whenever it changes. Sorry, but I forget the name of them.

For a fee, I suspect you can get a fixed IP from your provider.

I'm a bit lucky in this regard. Although my ISP uses DHCP, my address never changes unless I unplug the cable modem for more than 24 hours, and even then it almost never changes. I've had the same IP now for over 2 years.

The RDC client you need is already on XP, under Start/Accessories/Communications (I think). Mine moved when I upgraded to the newly-released version of the RDC client came out to support Windows Vista connections.

The new RDC client is killer...

-Larry
 
Would you please let me know if this is the correct way to open port 3389 on my D-Link DGL-4300 gaming router:

Advanced ---> Gaming

Add Game Rule

Name: RDP
IP: My PCs IP?
TCP Ports to open: 3389
UDP Ports to open: 3389

Save.

Thanks in avance!
 
You don't need UDP.

DynDNS usually works "OK"...naturally you'll occasionally run into some lag time if your IP changes but the update client and/or their servers haven't caught up to it yet. It's not as reliable as static IPs..but for a budget thing like a home use need..it works OK.

Many routers support dynamic dns services in their firmware..but how well this works varies...often the routers client hammer dyndns services too much and they react by ratcheting back the allowed uptime frequencies. They flat out state they don't like how router manufacturers do it..and they ask that you run their software clients instead.
 
As long as the IP is in the correct segment and is not conflicting with another machine, internet access works just fine.

In fact, this is how you use statics on most home routers. You start the DHCP Scope addressing at a number, say 100, and use everything below that as Static IP's because they won't get assigned to other equipment as DHCP addresses.

In fact, you _could_ use an address that can possibly be assigned by DHCP, and it will work, but eventually DHCP may try to assign it to something else and then you have a conflict.

-Larry

Cannibal Corpse said:
I found the correct link:

http://www.portforward.com/english/routers/port_forwarding/Dlink/DGL-4300/Terminal_Services.htm

The part that I am bit surprised is that even though I have DHCP enabled, when I changed my PC from Dynamic to Static IP, I could still get on the Internet.

How's that possible?
 
In the DGL-4300 you can also assign statics at the DHCP Level. In other words, it will always assign the same DHCP address to a particular NIC's MAC address regardless of whatever else happens on the network.

That's the way I have mine set up. That way I can just leave all the individual pieces on DHCP. It's simpler, for me at least.

-Larry

YeOldeStonecat said:
You choose a static IP that's outside of the DHCP pool. DHCP clients still pull their IPs, and static clients get what they are given. They both co-exist.
 
TechLarry said:
In the DGL-4300 you can also assign statics at the DHCP Level. In other words, it will always assign the same DHCP address to a particular NIC's MAC address regardless of whatever else happens on the network.

That's the way I have mine set up. That way I can just leave all the individual pieces on DHCP. It's simpler, for me at least.

-Larry

Yup..most routers support "reservations". I usually do it from true servers DHCP though. ;)
 
Back
Top