#6 – Configure and connect the P2S VPN Client to the Windows Azure P2S VPN.


 

This post is Part #6 of the:

Windows Azure Monitoring over P2S VPN using System Center 2012 Operations Manager

Available here: http://blogs.technet.com/b/manageabilityguys/archive/2013/11/05/windows-azure-infrastructure-as-a-service-iaas-point-to-site-p2s-test-vpn-setup-virtual-machine-monitoring-over-p2s-vpn-by-using-system-center-2012-operations-manager.aspx

  

Please make sure you read previous post(s) beforehand.

  

Link to previous part:

#5Create and Export the P2S VPN Client Certificate

 

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

  

After configuring Windows Azure to allow connections into our P2S VPN now it's time to configure the VPN Client machine.

  

First we start by importing the certificate exported in the previous post:

  

  

Select Local Machine as the Store Location:

  

  

And then specify the pfx file to be imported:

  

  

After you'll have to type the certificate password used when exporting the certificate:

(leave the remaining options set as shown)

  

  

Click next to use the Automatic option as shown:

  

  

And finish the certificate import:

  

  

  

After importing the client certificate you have to download and install the VPN Client software.

  

To do it you login to the Windows Azure Management Portal.

  

Select Networks > P2S-Network-1 and then click one of the highlighted options to download the software (either 64-bit or 32-bit)

  

  

Save the file:

  

  

Note that the msi file name is a guid:

  

Install it by using the Administration environment:

  

  

Notice that the install Window references the Virtual Network name:

  

  

After finishing the installation hover over the networks icon on the taskbar and click it:

  

You should be able to see the Virtual Network:

  

  

By double clicking it you'll open the connection manager dialog window:

  

  

Click connect and then you'll have to authorize the cmroute library to update your local routing table with the required routing info to connect to your Windows Azure Virtual Network:

  

  

You should then see the guid referenced on the VPN Client package showing as connected:

  

  

To check the IP Address settings run ipconfig in a command prompt window:

  

  

Take note of the IP of the PPP Adapter as you will need it on the next part 7 of this Blog series.

  

Important: Every time you re-establish connection the IP will change.

  

To confirm the connectivity is established you can log back into the Windows Azure Management Portal and check the Virtual Network status.

  

In the following screenshot you can see the connection in place and also how many clients connected:

  

  

In the next part we will focus on setting up cross-premises name resolution over the P2S VPN connection.

  

Next Part:

#7 – Configure Name resolution over P2S VPN Connection

 

 

Comments (0)

Skip to main content