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

From Linuxintro
imported>ThorstenStaerk
imported>ThorstenStaerk
Line 2: Line 2:
  
 
{| class="wikitable sortable" border=1
 
{| class="wikitable sortable" border=1
! [[program]] !! mean !! browser enablement possible !! CLI only access possible  
+
! [[program]] !! mean !! possible from Windows !! browser enablement possible !! CLI only access possible  
 
|-
 
|-
| [[ssh]] (successor of telnet and rsh) || issue commands to a remote computer || no || yes  
+
| [[ssh]] (successor of telnet and rsh) || issue commands to a remote computer || yes<sup>3</sup> || 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 || yes<sup>1</sup> || no
 
| [[shell in a box]], [[ajaxterm]]  || issue commands to a remote computer via a browser, also over the borders of a typical corporate network || yes<sup>1</sup> || no
Line 26: Line 26:
  
 
<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
 +
 +
<sup>3</sup> use [[xming]] if you want graphics, putty if text console is enough
  
 
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.
 
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.

Revision as of 14:45, 25 December 2011

There are many ways to take control over a Linux or Windows computer:

program mean possible from Windows browser enablement possible CLI only access possible
ssh (successor of telnet and rsh) issue commands to a remote computer yes3 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
rdesktop get a dedicated session on a Windows computer 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

3 use xming if you want graphics, putty if text console is enough

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