Technical Note - Working From Home
This tech note addresses two separate issues to working from home:
- File transfer
- Running software remotely
If you are looking for help with reading email, you should consult the email tech note
Which machine to connect to.
Whether you are wanting to transfer files or connect in a more interactive way, you first need to know what machine to connect to. Your files are visible on any of the School's servers
but depending on what sort of user you are (Undergraduate/Graduate/Staff) you only have access to a subset of them. Likely machines to try are
as these are accessible to all.
File transfer from ECS machines is achieved using SCP or SFTP. There are many clients available for a variety of operating systems.
- Windows: We recommend WinSCP.
- OS X: You can use the command-line
sftp commands, or something like Cyberduck or Fugu, if you prefer GUIs.
- * nix variants: You should have command-line
sftp on your machine.
Older file transfer protocols such as
should not be used since they transmit passwords in clear text (unencrypted) over the network. This is particularly discouraged if you are connecting via the public internet, since you have no idea who might be snooping on the network. The one exception where it is OK to use
is if you are downloading from an anonymous ftp
service (ie: you are not required to log in using your username/password in order to download files).
The ECS network is configured to allow incoming
connections to all
students. You should be able to access a machine from anywhere in the world.
- Windows: Windows users will want to use PuTTY to get an SSH connection.
- OS X, *nix variants: You should have
ssh installed and accessible from the command-line.
Again, older protocols such as
which transmit information in clear text should not be used.
X Forwarding (SSH with X forwarding)
X forwarding is the process of having X windows drawn on your own screen than on the remote machine. This means that you can interact with our NetBSD GUI programs at home.
Because all interactions have to be transmitted to an ECS machine and then the window section redrawn and sent back to you, this method can be slow, particularly so on an international connection. Where possible, it may make more sense to transfer the documents you wish to use with scp, and then run programs on your own machine. Many of the programs ECS utilises are open-source and free to install at home.
To view the X windows, you need an X window server to be running:
- Windows: Cygwin is the best way to achieve this. To start your X server when Cygwin is installed, you run
xinit from the Cygwin window.
More recent (Nov 2016) installations of Cygwin on the School's windows workstations appear to provide a better rendered X window if you type
startxwin instead of
- OS X: You need to install the X11 optional package from your OS X Installation Disc, and then start the X Server application.
- * nix variants: You should already have an X server running.
Once the X server is running, you should run
ssh -X [username]@[host]
. For example, Lindsay Kingston logs in with
ssh -X firstname.lastname@example.org
Full Remote Session (VNC)
Advanced users only
VNC needs to be tunneled through SSH, as the traffic it sends is unencrypted. To get a VNC session, you should do the following:
vncserver on an ECS server using SSH.
- Take note of the outputted information (such as "New 'X' desktop is greta-pt.ecs.vuw.ac.nz:1")
- Create an SSH tunnel:
- For Windows and PuTTY:
- Select Connection -> SSH -> Tunnel.
5900 + 1 + display number into the Source Port box (eg. "5902").
[host]:[5900 + displaynumber] into the Destination box (eg.
- Select Open and login as normal.
- For OS X and *nix variants: Type
ssh -L [5900 + 1 + displaynumber]:localhost:<5900 + displaynumber> (eg.
ssh -L 5902:localhost:5901 greta-pt.ecs.vuw.ac.nz)
- Start your VNC client.
- Type in
localhost:[5900 + 1 + displaynumber] (eg.
- When you are finished close the client.
- Make sure you kill the server with the command
vncserver -kill :[displaynumber] on the ECS server you started it.
- Exit your SSH tunnel.
By default, this will give you a terminal and basic window manager. If you want to run KDE via VNC you need to perform the following commands after SSHing into an ECS server:
mv xstartup xstartup.bak
echo "startkde" > xstartup
chmod u+x xstartup
As of around March 2018 the ability to run KDE under VNC appears to be broken. We will attempt to fix this issue at some point, but since running the simpler default X-Windows session that VNC sets up for you does
still work this may not be a high priority. Watch this space...
The password used by the VNC server to control access is set with the
command and is stored in
Full Remote Session (VPN) [Staff only]
Windows users may use Remote Desktop Connection over VPN for effective access to campus services and ECS Windows servers. For VPN installation see the ITS VPN FAQ