Dealer Network Home
Dealer Network Home    DNet-KM.com    DNet-KM.com  Hop To Forum Categories  Making The Connection    remote desktop
Go
New
Find
Notify
Tools
Reply
  
remote desktop
 Login/Join 
Senior Member
Posted
I know how to remote connect within my LAN, how do I do it beyond my own network? for instance, there are a million IPs "192.168.1.10", or hostname "BobsComp". Just wondering, not urgent. Thanks!
 
Posts: 465 | Registered: September 11, 2007Reply With QuoteReport This Post
Imaging god
Picture of Scotty
Posted Hide Post
Using RDP (Remote Desktop Protocol) accross the internet requires port forwarding exceptions on the customers router/firewall - and usually a static internet IP (if you need to be able to do it on a regular basis).

Routers and firewalls can have very different configurations from manufacturer to manufacturer, but most of the consumer or small business mainstream products will have an advanced configuration page with 'Port Forwarding' - others may call it 'Port Exceptions', 'Firewall Exceptions' or 'Pinholes'.
Any workstation or server that you wish to use RDP with needs to be on either a reserved IP (a DHCP address reserved for the MAC address of the workstation) or a static LAN address.
On the port forwarding (or whatever) page you simply direct WAN port 3389 to LAN 3389 of the static address of the workstation.
Many routers will allow forwarding from an alternate port redirection - like WAN 4020 to LAN 3389 - this is very useful if you need to access multiple desktops in the same organization - In RDP you would use something like "66.55.44.33.2:4020" to connect to the alternate desktop.

Also, I highly recommend you NOT use the default 3389 port exposed to the internet, since it's an obvious target. If your router doesn't allow port forwarding with redirection, you can change the desktops receiving port from 3389 to another port by a registry change.
See http://support.microsoft.com/kb/306759 for more information on this.

I frequently only set up the server (or the main workstation if it's a peer to peer network) for RDP and then setup VNC for other stations on the LAN if I need to administer those - so that only one RDP port is open to the internet. I just connect to the server and then connect to workstation from it if need be.

It is NOT a good idea to use VNC directly (with it's port open to the Internet).

Although I do recomment a static internet IP, an alternative is to use a dynamic dns service like dyndns.org that uses a utility on your server or workstation to keep track of your current internet IP address so that you can use a host name like myserver.dyndns.org to connect.


Relax? When?!
 
Posts: 1131 | Registered: November 15, 2005Reply With QuoteReport This Post
Senior Member
Posted Hide Post
Scoful, you're a good man. Thanks for taking the time to explain this, I will add this post to my folder of resources.
 
Posts: 465 | Registered: September 11, 2007Reply With QuoteReport This Post
  Powered by Social Strata  
 

Dealer Network Home    DNet-KM.com    DNet-KM.com  Hop To Forum Categories  Making The Connection    remote desktop

© 2002-2012 Dealer Network
home | about | rules | donation | message board | contact