› Forums › Technical support › Virtual Machine › Connecting to SSL VPN through the VM
- This topic has 5 replies, 2 voices, and was last updated 4 years, 2 months ago by Simon.
-
AuthorPosts
-
-
October 7, 2020 at 11:41 #12276
I followed all the instructions for setting up an SSL VPN as outlined here:
https://www.ed.ac.uk/information-services/computing/desktop-personal/vpn/vpn-l2tp-clients/linux-ubuntu
And I got this error: sudo: apt-get: command not found
[atlab@localhost ~]$
I thought maybe I got this error because the components were already installed so I skipped to the next step outlined on the same page and add and L2TP vpn connection – but there was no option in the network menu to do this. How can I fix this and connect to the FortiClient VPN? -
October 7, 2020 at 11:56 #12277
Looks like you are trying to install the VPN inside the Virtual Machine. That’s not the way to do it. Install the VPN on your personal computer.
To use the VPN with the Virtual Machine (e.g., for copying the files needed for the first assignment), connect to the VPN on your personal computer, then start the Virtual Machine. The Virtual Machine uses your personal computers network connection, so will also be using the VPN.
-
October 8, 2020 at 07:34 #12282
-
October 8, 2020 at 07:43 #12285
The
$
indicates the shell prompt – the command to run is the part after it. -
October 8, 2020 at 08:50 #12286
I got a new error
[atlab@localhost ~]$ $ sudo rsync -avul –progress –files-from=:/Volumes/Network/courses/sp/manifest.txt s1869308@scp1.ppls.ed.ac.uk:/ /
bash: $: command not found…
[atlab@localhost ~]$ sudo rsync -avul –progress –files-from=:/Volumes/Network/courses/sp/manifest.txt s1869308@scp1.ppls.ed.ac.uk:/ /
[sudo] password for atlab:
Sorry, try again.
[sudo] password for atlab:
ssh: Could not resolve hostname scp1.ppls.ed.ac.uk: Name or service not known
rsync: connection unexpectedly closed (0 bytes received so far) [Receiver]
rsync error: unexplained error (code 255) at io.c(226) [Receiver=3.1.2]
[atlab@localhost ~]$ -
October 8, 2020 at 08:57 #12287
First, try rebooting the Virtual Machine.
Some other possible ways to diagnose the problem:
1. can you reach websites (e.g., http://www.ed.ac.uk or google.com) using Firefox in the VM?
2. are you in University accommodation (in which case you don’t need the VPN – you are already inside the University network)?
3. use a browser on your personal computer, and also in the VM, and type “what is my ip” into the Google search box
-
-
AuthorPosts
- You must be logged in to reply to this topic.