Rdesktop for remote access to workpc

Using applications, configuring, problems
Post Reply
Message
Author
spb37
Posts: 14
Joined: Tue 03 Oct 2006, 06:23

Rdesktop for remote access to workpc

#1 Post by spb37 »

Hi,
I have no trouble using rdesktop (pup 212) from the command line to remotely access windoze computers within my home network. But even after googling I'm stumped how to connect to my work computer or how to connect to my home computer from work. My linux level is beginner intermediate. I'm currently paying through the nose to access work pc with gotomypc. Also, I run a small medical research lab and if I understand rdesktop better maybe I can get some in my lab to try linux more if they could quickly access a core university workstation pc with our labs programs. Thx

Ipconfig describes work windoze computer as
Connect specific dns: ohsu.edu
ip: 137.53.24.213
subnet mask 255.255.255.1
default gateway 137.53.24.1

Anyone know what I type into the terminal to get rdesktop to work similar to gotomypc. Or do I need to install anything on the windoze side.
User avatar
rarsa
Posts: 3053
Joined: Sun 29 May 2005, 20:30
Location: Kitchener, Ontario, Canada
Contact:

#2 Post by rarsa »

First, your problem has nothing to do with linux but everything to do with understanding your networks (home and office) and how much control you have over the networking infrastructure at work.

Actuallt the RDP (rdesktop) protocol also called Terminal services, is a protocol for windows computers.

The rdesktop utility (and the GUI included in Puppy) is to connect to windows computers.

Regardless of using windows or Linux, at the most basic level, to connect using RDP through a firewall, you need to open TCP port 3389.

Of course that is not wise or advisable for computers connecting through the internet.

The secure way of doing it is creating a VPN (Virtual Private Network) connection, that will take you securely past the firewall and you will be able to connect. That's how I connect to my office.

An alternative way is to use VNC through SSH. Most firewalls allow SSH trafic to pass through. That's how I connect to my home linux computer from work.

You could also use the call-back functionality of VNC to connect to your office computer from home. Of course, tunneling through SSH for security.

The point here is that to really help you we need to understand your home and work networks. What can you tell us about them?
[url]http://rarsa.blogspot.com[/url] Covering my eclectic thoughts
[url]http://www.kwlug.org/blog/48[/url] Covering my Linux How-to
spb37
Posts: 14
Joined: Tue 03 Oct 2006, 06:23

#3 Post by spb37 »

Thanks Rarsa. I know I can put in a work order for getting a VPN on the firewalled school work station so that should solve my problem. Appreciate the quick response.
User avatar
paulh177
Posts: 975
Joined: Tue 22 Aug 2006, 20:41

#4 Post by paulh177 »

rarsa wrote:An alternative way is to use VNC through SSH. Most firewalls allow SSH trafic to pass through. That's how I connect to my home linux computer from work.
i would really like to know how to do that rarsa
User avatar
rarsa
Posts: 3053
Joined: Sun 29 May 2005, 20:30
Location: Kitchener, Ontario, Canada
Contact:

#5 Post by rarsa »

paulh177 wrote:i would really like to know how to do that rarsa
I don't know how much detail you need, so here is the high level.

PREPARATION
You'll have to do this just once. It should about 10 minutes in each computer if you haven't done it before.

On your home Puppy linux side:
1. Create a password for root on your home Puppy linux. Choose a very complex password!
2. Install the vncserver dotpup. (Search the forum)
2. Install the sshd dotpup (Search the forum)
3. Open port 22 on your home firewall if you are connected directly. If you connect through a router, forward port 22 to your puppy computer
4. If you want sshd to always start whenever you boot your computer: Add the command to the rc.local file.

On your work computer (Assuming it is windows)
1. Install an ssh client. I actually have cygwin which has an ssh client, but if you google you will find many different clients
2. Install the realVNC client from the realVNC web site

TO CONNECT
You'll have to do this every time you connect.

1. Connect to your home IP address using SSH (see note below), make sure you include port 5901 tunelling.
e.g.
using the cygwin console:
ssh -l root -L5901:localhost:5901 73.158.96.87

2. On that ssh session start a vncserver session if you don't have one already

3. Open a VNC session to the address "localhost:1" or "localhost:5901" (It depends on how your particular ssh client tunnels the port)

NOTE: If you don't have a static IP at home (most likelly) then you must do one of these two things:
- Before leaving for work every morning, check what's the IP (www.whatsmyip.com)
- OR, get a dynamic DNS address. I use http://www.dyndns.com, that way you don't need to know the IP address as long as you keep your address synchronized.
[url]http://rarsa.blogspot.com[/url] Covering my eclectic thoughts
[url]http://www.kwlug.org/blog/48[/url] Covering my Linux How-to
User avatar
paulh177
Posts: 975
Joined: Tue 22 Aug 2006, 20:41

#6 Post by paulh177 »

Thanks rarsa, that's really helpful.
I also found this tutorial -- http://www.vanemery.com/Linux/VNC/vnc-over-ssh.html -- so between the two I ought to be able to work it out.

paul

PS it's http://www.dyndns.org/ by the way
Post Reply