Remotr Desktop

[Lupi]

does the rdp web only work in a LAN or can i remote to my pc at home from a
pc located else where in the world?

 

[Malke]

does the rdp web only work in a LAN or can i remote to my pc at home from
a pc located else where in the world?

You can remote into a home computer if the home computer is running XP Pro.
XP Home can't be the host. If you're behind a router, you will need to set
a static IP on the home computer and open the appropriate ports. Obviously
you'll need to know the WAN IP address (or the home computer's IP address
if not behind a router).

If you have XP Home and don't want to upgrade to Pro, you can use
third-party software such as Ultra/Tight/RealVNC or pcAnywhere
(commercial).

Malke

 

[VanguardLH]

does the rdp web only work in a LAN or can i remote to my pc at home from a
pc located else where in the world?

First check with the IT folks at your company. Adding an outside host
to their network probably violates company policy and can get you into
very hot water really quick. You are trying to punch past their
security boundaries to bring in an untrusted host onto their network.
It's their property so get their permission to do what you want. If a
malware infection got traced to your home host through a remote
connection that violated their policy and for which you didn't get
permission, not only expect termination but a lawsuit to collect damages
for eradication of the malware.

If you can punch out through their security boundaries using Remote
Desktop Protocol (not likely unless they are boobs or it is a small
company with no one who is really a security expert) and after getting
their permission to do so, you'll probably find they want you running a
secure VPN on your host to connect to their network instead of using
RDP. If not, you'll need to know the IP address of your home host.
Since that is likely to be a dynamic IP address, it can and will
eventually change. You need to either pay extra from your ISP to get a
static IP address or using something like DynDNS or No-IP. You use
their service to provide an IP name to your host. You run their client
on your host to report to them your current dynamic IP address. So they
link an IP name (at their domain) to the current IP address of your home
host. You then need to punch a hole in your router's firewall to
port-forward any unsolicited inbound connection requests on port 3389
and specify they go to a particular host in your home network.
Depending on your router's firewall and feature set, you might have to
use a static IP address on your home host (within the IP range allowed
by your router), so you would end up configuring TCP to *not* use DHCP
and instead use a specific static IP address (which also means you have
to specify the IP addresses for your ISP's DNS servers). That way, when
your router gets an inbound connect on port 3389, it knows to which
intranet host to forward the connection. You need to enable RDP on your
host to allow the inbound connect. You also need to ensure your login
is in the list of allowed users to connect to that host using RDP (I
believe admin-level accounts are included by default).

So you use Remote Desktop from your work host using the IP name (from
DynDNS or No-IP) for your home host using port 3389. Your home host is
running an update client that tells DynDNS or No-IP what is your current
dynamic IP address. Your router sees the inbound connect request on
port 3389 and forwards to the static IP address that you configured for
TCP on your home host. With RDP enabled on your home host and if the
login credentials are valid, you then get to connect to your home host
from work. Meanwhile, the IT folks at your company are monitoring their
network traffic and will see packets that target and originate from an
IP address that is not within the ranges defined for their subnets. If
you didn't get permission from them, they WILL know you violated their
security measures.