Use Windows 2008 R2 single network card to build vpn actual combat settings

Use Windows 2008 R2 single network card to build vpn actual combat settings

July 22, 2013 15:12:39

Readings: 125017

      I am original, please indicate CSDN for reprinting, please correct me if there is any mistake, thank you!

     Because the company suddenly refused to let chat tools such as QQ and Want Want, and always rely on QQ for external contact, now suddenly there is no way to use the tools that basically cut off external contact, so I built a small server for myself through a small server of the company. vpn, I will use it for now. The process is not complicated. Now I will share it with you. Because the network segment of the server is not limited, I have decided to do this. The operation is as follows:

   First you need a server (nonsense) as shown below:

   Step 1: Install the role:

    

 

Step 2: Check "Network Policy and Access Services"

 

Step 3: Check the configuration

 

 

Step 4: Tick all the options on the map

 

 

 

 

 

Then: Confirm the installation phase

 

 

one more picture

 

After installation, enter the second stage

 

 

 

Stage 2: Configure the VPN server.

 

 

Click to enter Server Manager - Routing and Remote Access

 

 

 

Right-click "Routing and Remote Access" - click "Configure and Start Routing and Remote Access" as shown below: (because I have already configured it, it is gray, but it is not gray when you configure it)

 

 

The configuration wizard pops up, and click Next:

 

 

Be sure to select "Custom Configuration"

 

In order to avoid unnecessary trouble later, we "select all" all options and click "Next":

 

Wait for the system configuration to complete:

 

The system shows that the service is already running

 

After expanding, please click "IPv4" - right click "NAT" - select "Add Interface"

 

Then add the "internal" interface and "local interface", and "right-click" - "property" as follows:

 

The local connection is as follows:

 

 

Last step of VPN configuration: Right click on "Routing and Remote Access" - click on "Properties"

 

 

 

 

Configure the static IP VPN address allocation list. The IP address segment here can be set as you like (that is, the IP allocated by the client after connecting, I only allocate 10 here, depending on the individual situation)

 

 

 

Third, configure "Network Policy Service" If you do not configure it, an "812" error will be reported when you log in to the VPN

Click "Start Program" - "Administrative Tools" - "Network Policy Service"

 

Right-click on "Policy Name" - click "Properties" to configure as shown in the figure below: red before no policy is allowed, green after both are allowed, press "Confirm" after configuration, it will not appear after configuring the login. 812" error.

 

 

 

 

 

 

Finally: create a new VPN user and set up a simple security group:

 

Create a new VPN user group: Click "Server Manager" - right click "Group" and create a new one as shown below

 

After creating the user group, let's create the VPN user: set as shown below

 

 

 

For the sake of security, let's do a simple local group policy to prevent users from logging into the server indiscriminately, click "Local Security Policy Group"

 

 

 

Click to enter: I suggest that you set the two policies here, so that the user can log in to the server directly, and apply the policy to your corresponding "user group". Here I am the VPN user group.

 

 

In this way, the login of the entire VPN setting is completed, and you can now successfully log in to your own VPN through the newly created user name, and avoid the company's network block.

Guess you like

Origin http://43.154.161.224:23101/article/api/json?id=325931410&siteId=291194637