Difference between revisions of "Control a computer over the network"

From Linuxintro
imported>ThorstenStaerk
(you will not be able to run e.g. apache on the same port as shell in a box)
imported>ThorstenStaerk
Line 24: Line 24:
  
 
<sup>2</sup> you will not be able to cross a typical corporate network. You will need access to more ports on the server than 80 and 443
 
<sup>2</sup> you will not be able to cross a typical corporate network. You will need access to more ports on the server than 80 and 443
 +
 +
With WebEx and with x11vnc you will be able to take over an existing session and work jointly on it. This is useful for support and training.
  
 
= See also =
 
= See also =
 
* [[Access the display on a remote computer]]
 
* [[Access the display on a remote computer]]

Revision as of 09:35, 17 July 2011

There are so many means how you can take control over a Linux computer:

program mean browser enablement possible CLI only access possible
ssh (successor of telnet and rsh) issue commands to a remote computer no yes
shell in a box, ajaxterm issue commands to a remote computer via a browser, also over the borders of a typical corporate network yes1 no
xdmcp get a graphical login to a desktop no no
vnc get a graphical desktop on a remote computer, sharable with other users yes2 no
x11vnc take over a graphical session that has been started out of vnc no no
guacamole share a Linux desktop over a browser yes no
nx get a low-latency graphical login to a desktop no no
webex take over a graphical session using a browser yes no

1 you will not be able to run e.g. apache on the same port as shell in a box

2 you will not be able to cross a typical corporate network. You will need access to more ports on the server than 80 and 443

With WebEx and with x11vnc you will be able to take over an existing session and work jointly on it. This is useful for support and training.

See also