Exercise 1: Installing a Network Adapter
In this exercise, we need to install a second network adapter to the Server VM to support RRAS. The Lab shows it being done in Hyper V and since we are using VSphere it’s done differently but I’ll follow it as much as possible.
The lab wanted an ‘External Network’ so let’s hope this does not cause me issues later on.
Exercise 2: Examining Unsecured Traffic
This exercise is about understanding the risks involved with unsecured network traffic.
I need to log in on the Server VM and create a subfolder named SECRET, then a text doc named CONFIDENTIAL and enter in ‘The password is Courage’
Now we need to create a new share on the server.
Now switching to the Client VM we need to run Wireshark and start capturing.
Now I need to see if I can see secret$ when I type \\SERVER in the run prompt.
To no surprises, I can’t because the $ makes a file hidden.
Now I need to enter \\SERVER\secret$ in the file explorer, open the Confidential file and then stop the Wireshark Capture.
Now we need to look through the Wireshark results and find ‘NetShareEnumAll Response’
Here you can see in the frame you can see that the information shows the secret$ share.
Now we need to look for ‘Create Response File: ;Find Response;’
Here we can see the text file being accessed.
Now we need to look for ‘Read Response’ and see if we can see the data, which we can.
Exercise 3: Configuring a VPN
We start this on the Server VM and using ‘Add Roles and features’ and selecting Remote access role, and the DirectAccess and VPN (RAS) service.
Now we need to ‘Configure and Enable Routing and Remote Access’
Now I need to edit the firewall settings inbound rules, my firewall rules were allowed by default.
Last we need to configure user rights to join a VPN, using Users and Computers.
Exercise 4: Joining a VPN
Using the Client VM, we need to setup a new connection to the VPN.
Exercise 5: Examining VPN Traffic
Now we want to see what information we can capture using Wireshark.
On the Client VM we need to start Wireshark and capture data, then connect to the VPN and try read the confidential file created in our secret folder.
Now it’s time to see what Wireshark picked up, by putting pptp or ppp or gre.
The only information I found was the names of the talking VM’s and the user name.
I enjoyed creating the VPN in this lab, but I am confused on the purpose of the second NIC, was that just so we could install the VPN? Because the VPN was also configured on the orignal NIC not the new one… Kinda confused.
Anyway, the lab went smoothly without any issues, which surprised me as I was expecting the VPN to just not work.
I would not change my approach to this lab as I did not face any real issues.