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

From Linuxintro
imported>ThorstenStaerk
imported>ThorstenStaerk
 
(2 intermediate revisions by the same user not shown)
Line 4: Line 4:
 
! [[program]] !! mean !! possible from Windows !! 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 || yes<sup>3</sup> || 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]], [[webmin]]<sup>2</sup>  || issue commands to a remote computer via a browser || yes || yes<sup>1</sup> || no
 
| [[shell in a box]], [[ajaxterm]], [[webmin]]<sup>2</sup>  || issue commands to a remote computer via a browser || yes || yes<sup>1</sup> || no
Line 27: Line 27:
 
<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 [http://sourceforge.net/projects/xming xming] if you want graphics, [http://www.putty.org/ putty] if text console is enough
+
<sup>3</sup> use [http://mobaxterm.mobatek.net/ mobaxterm] which will give your graphical and console access
  
 
<sup>4</sup> as command use mstsc
 
<sup>4</sup> as command use mstsc
Line 34: Line 34:
  
 
= See also =
 
= See also =
 +
* [[terminal server]]
 
* [[interoperability]]
 
* [[interoperability]]
 
* [[Access the display on a remote computer]]
 
* [[Access the display on a remote computer]]

Latest revision as of 14:48, 1 June 2016

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, webmin2 issue commands to a remote computer via a browser yes yes1 no
xdmcp get a graphical login to a desktop yes no no
vnc get a graphical desktop on a remote computer, sharable with other users yes yes2 no
x11vnc take over a graphical session that has been started out of vnc no no no
guacamole share a Linux desktop over a browser yes yes no
nx get a low-latency graphical login to a desktop yes no no
rdesktop get a dedicated session on a Windows computer yes4 no no
webex, teamviewer, gotomeeting, mymeetingroom take over a graphical session using a browser yes 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 mobaxterm which will give your graphical and console access

4 as command use mstsc

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