Remote desktop via network

It would be nice if it was possible to be on the Pi's desktop (remote desktop) through the network connection.

This way I - or We - could run the RPi without it's own KB, Mouse and Monitor. What a relief...

...or maybe through the USB connection (This would require a special P2P USB cable, which is possible to buy)

Where to begin... there are various ways to accomplish what you want.

First, through SSH, with X forwarding. This works on pretty much all platforms known to man. I describe the process for solaris, openindiana, linux, mac and windows here:

http://raspberry-python.blogspot.com/2012/09/sidekick.html

and here:
http://raspberry-python.blogspot.com/2012/09/sidekick-2.html

Does that work for you? If not, other options include vnc and derivatives, xrdp, freenx etc, but you dont say what desktop you have that you are wanting to remote from to the Pi.

Francois

I would like to show and control the Pi's Xwindows desktop - on an active running windows PC over the network.

This requires of course som P2P program that communicates the monitor / Keyboard and mouse data...

In this case a linux and a win client.

this of course for running xwindows programs on the pi remotely from a windows pc.

hope its more clear now - it would save a separate monitor/kb/mouse for the pi.

If all you want is to run the programs on the pi and have them displayed on your linux or windows box, then the links I sent you do exactly that. From a linux box you ssh -X and from windows instead you would use putty with X forwarding enabled. It's all in details on that link. This is by far the best approach since you have integration of native and raspberry pi apps in one desktop. Have you read the 2 articles?

If you are still insisting in a more traditional KVM like approach over IP, then you'll need to use something like tightvnc. The funny thing, most people end up doing VNC over an SSH tunnel, because VNC is insecure, and after a while, you get used to just starting the app you want instead of the whole desktop. Anyway, the VNC step by step is here http://elinux.org/RPi_VNC_Server.

The condensed version if you've followed the instructions on the sidekick articles I posted earlier, you can then:

ssh -X raspberrypi
[enter password]

$ sudo apt-get tightvnc

$ tightvncserver :1

You will require a password to access your desktops.

Password:
Verify:
Would you like to enter a view-only password (y/n)? n

New 'X' desktop is raspberrypi:1

Creating default startup script /home/fdion/.vnc/xstartup
Starting applications specified in /home/fdion/.vnc/xstartup
Log file is /home/fdion/.vnc/raspberrypi:1.log


And then from your desktop you use a vnc client (there's at least a dozen out there) and connect to raspberrypi:1 (because we started a listener on 1).

I could also have started tightvnc with a resolution, to force a specific desktop size, ie:
$ tightvncserver -geometry 1024x768 :1


If you reboot, the vnc server will not restart automatically, but the elinux tutorial has that covered too.

Francois

Have you tried VNC?

It is a remote desktop solution.

VNC is good but on a Pi I think it's too sluggish that's the problem with most Remote Desktop apps

Here's a site with 15 possibilities try em all tell us what you think works the best.

http://www.mynitor.com/2010/02/07/15-remote-desktop-solutions-for-linux/

Using X forwarding is muuuuuuuch faster than VNC since most of the GUI interactions are handled on the PC (moving widows etc.).

Where to begin... there are various ways to accomplish what you want.

First, through SSH, with X forwarding. This works on pretty much all platforms known to man. I describe the process for solaris, openindiana, linux, mac and windows here:

http://raspberry-python.blogspot.com/2012/09/sidekick.html

and here:
http://raspberry-python.blogspot.com/2012/09/sidekick-2.html

Does that work for you? If not, other options include vnc and derivatives, xrdp, freenx etc, but you dont say what desktop you have that you are wanting to remote from to the Pi.

Francois

Nice tutorials! I like the name "sidekick" for this type of headless, remote access mode of using a Raspberry Pi. Given how fiddly displays and USB peripherals are, this might easily be the preferred configuration for many users - at least those who already have another computer of some sorts. (See http://blog.kugelfish.com/2012/09/raspberry-pi-tethering.html for an example of a sidecar-sidekick configuration...)

got the Pi gui on my galaxy note screen!
I have just followed the linux newsletter article for N900 (see below remote login with my Samsung Galaxy note.
it looks good, phone connect as wi-fi-hotspot teathered usb. Android terminal on phone , ssh pi@192.168.42.154 gets connection . I had to set all 3 rsa,dsa,cedsa passwords on raspian OS saved in /etc/ssh.... filename ...and make the .desktop file as per N900 article but eventually got the startx gui on the galaxy note screen. will use Rii keyboard when it arrives but should have a nice compact system. sorry for the lack of detail, i had help from those who know. android vnc on phone and x11vnc on pi. so i can use the pi with just my phone and a tiny keyboard. I just need to make my head 4" wide to fit the screen.
http://www.linuxjournaldigital.com/linu ... pg=46#pg46

There's also Synergy, which does something slightly different than the solutions proposed above. Instead of displaying the Pi's desktop inside a window on your local machine, it shares the keyboard & mouse on your desktop with your Pi.

Set the Pi's monitor next to your desktop's, and you can scroll your mouse over, and the pointer then appears on the Pi's desktop. I use this all the time, though not yet with the Pi. I'm sure someone has ported it by now, though