Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
software:vnc [2008/12/13 20:42] cyril created |
software:vnc [2013/09/19 16:40] (current) |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== VNC ====== | ====== VNC ====== | ||
| ===== Windows ===== | ===== Windows ===== | ||
| - | RealVNC | + | TightVNC |
| ===== Linux ===== | ===== Linux ===== | ||
| - | x11vnc contains a good server that allows you to access your already running session. You can set a new password with '' | + | x11vnc contains a good server that allows you to access your already running session. You can set a new password with '' |
| - | vncviewer is a good viewer. | + | TightVNC contains a good client. |
| + | |||
| + | |||
| + | ===== About routers and firewalls ===== | ||
| + | |||
| + | The server is behind a router or firewall: | ||
| + | - if the client is not behind a router or firewall: the server invites the client ("vncviewer | ||
| + | - if you can open the port 5900 (or another one you prefer): open it | ||
| + | - if you can access in ssh to the server, or to another machine on the same network: create a ssh tunnel | ||
| + | |||
| + | The client | ||
| + | - but some ports are open, use invitations listening on an open port (need to be root if < 1024). With Linux:: | ||
| + | - if you can access in ssh to another machine on the same network: create a ssh tunnel to send the invitation | ||
| + | - if you can access in ssh to another machine on which you can open ports, create a remote ssh tunnel (''' | ||
| + | |||
| + | If your ssh is completely blocked, and you control another machine somewhere, open an ssh server on port 80 or 443... | ||
