Changes between Version 35 and Version 36 of VmServer

Timestamp:

Jun 6, 2008, 1:42:20 PM (16 years ago)

Author:

davea

Comment:

--

VmServer

@@ -95 +95 @@
 
 === NAT ===
+
 In this mode, the VM shares the IP address of the host machine in order to make outgoing connections
 (access Internet sites from within the VM).
 Scanning the network will only reveal one machine.
 
-Incoming connections from other machines (except the host machine) are, in principle, not possible.
-However, there is a way to circumvent this lack of incoming (to your server) connectivity and,
-thus, be able to receive connections from BOINC clients outside your network:
-port forwarding (not available with the free VMware player).
-This can be done using the VMware virtual network editor (Edit > Virtual Network Settings > NAT > Edit > Port Forwarding).
+Incoming connections (except the host machine) are generally not possible.
+However, this can be circumvented using port forwarding (not available with the free VMware player).
+To do this, use the VMware virtual network editor (Edit > Virtual Network Settings > NAT > Edit > Port Forwarding).
 More information in [http://www.vmware.com/support/ws5/doc/ws_net.html Configuring a Virtual Network].
 On Windows, if NAT is to be used and not already set,
-you need to do the following to get network access in the VM:
+do the following to get network access in the VM:
 {{{
 Start | Programs | VMware | VMware Server | Manage Virtual Networks
@@ -116 +115 @@
 }}}
 
+=== SSH ===
 
+The VMWare player provides only a 24x80 non-scrolling console window.
+Once you have networking, it's much handier to SSH into the server.
+To enable the SSH daemon:
+{{{
+su -c '/usr/sbin/sshd'
+}}}
 == The 'compatibility' VM for building and testing apps == #compatibility