2008R2 precautions for configuring L2TP pre shared key VPN

Reference resources https://me.jinchuang.org/archives/665.html To configure l2tp vpn, If this link fails , Please refer to this attachment .

2008 R2 Install configuration on the system L2TP IPsec VPN [ Connect using a preshared key ].zip

matters needing attention ：

In Alibaba cloud and Tencent cloud vpc End of configuration l2tp Pre shared key vpn after , relevant 3 A service is running , At first, mobile phones can be connected , But after restarting the server , The mobile phone can't be connected , Tencent cloud and Alibaba cloud VPC All have this phenomenon , Tencent cloud basic network is normal . What's the difference ？ The basic network is static IP Than private networks DHCP Get network fast .

Restart what happened ？

The process is rather tortuous , Several times after I just restarted the server, I couldn't connect it for many times , Just sit still and go to sleep , It will be normal to connect again after waking up , I wonder if I was too anxious to connect after restarting , Would it be better to wait a few minutes and then continue ？ Later, I configured automatic login observation in the server （ When I turn on this way vnc You don't have to enter a password to log in , You can take the opportunity to see the startup of relevant services just started ）, I found that when the machine was just restarted , relevant 3 Services did not start , The service did not start until the system entered the desktop for oneortwo minutes , also 3 Services have 1 One is manual （ After entering the desktop 3 None of the services started , After a while 2 About minutes ,3 All services are started , It has nothing to do with the manual mode service ）, Then I put that 1 The change from manual to automatic is still the same as before ： After restarting the machine, you can't hurry , It will take a few minutes , Otherwise you will have to wait for hours if you fail , Or restart the phone to connect it immediately . Later, we re review3 A service , Find the one displayed in the server manager 2 An automated service startmode It is actually a delayed start ,

The final will be 3 A service person startmode Change to automatic （ Non delayed start ） Restart the observation , Found that after restart 3 The service soon became normal , The previous phenomenon never happened again .

From the server vpn The log shows that there is no sign of server rejection , Log location ：C:\Windows\system32\LogFiles The one in the catalog .log Log No 5 The number in the column is only 1、 2 、4 Did not see 3（ The server refused ）

Refer to Microsoft documentation for relevant log parsing ：https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc771748(v=ws.10)?redirectedfrom=MSDN

summary ： The key is to put l2tp vpn Involved 3 The startup mode settings of the services are automatically started , About that 3 Service and virtual network segment routing , It also applies to other versions of windows server. in addition , The machine purchased by Tencent cloud public image is initialized with all vpc Route of network segment , If you match vpn Virtual network segment is in it , It will affect vpn Business （ such as vpn The connection was established successfully , however ping no vpn Virtual network segment IP）, At this time, you need to delete the default route of the virtual network segment , May refer to https://cloud.tencent.com/developer/article/1893670 Inside 【 Question 1 】vpn Show connected , But I can't visit vpn Virtual segment , It is because of the problem of routing To deal with it , Two other cases are recorded in this document

【 Question two 】 even vpn It's a mistake , The client registry needs to be adjusted

【 Question 3 】vpn Connected to 、 Virtual segment devices can also access , But I can't get on the Internet

solve Windows Connect PPTP/L2TP Unable to connect to the Internet when Internet The problem of

https://www.tintsoft.com/articles/676.html