Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Thursday, November 2, 2017 8:55 PM | 5 votes
Hi Guys
I am using an ultra book for mobile work and connect to my home network via VPN with an HSDPA WWAN modem. Before the fall creators update everything was working fine. Now after the update I cannot connect anymore via mobile network.
the setup: I have a Win 2016 Server with RRAS configured for L2TP PSK VPN. When I connect from withing the network (LAN or WLAN) everything works as expected. Only the WWAN connection from outside does not work.
Strange thing is, when I do this with my adroind mobile it works, via WLAN and WWAN.
I have forwarded the ports 500, 1701 and 4500 in the router to the vpn server and also enabled the ESP protokol. I have checked with Wireshark if any communication on those ports arrives at the server when connecting with the win 10 (1709) machine, and yes there is traffic. But there are no events logged on the server and the client reports an 809 error in the vpn client events.
I have googled for hours and watched several L2TP howtos on YouTube, so I can say the server seems to be configured correctly and working fine. Also the port forwarding is working as i can connect via android phone. I do not know how to debug or trace this to narrow in on the problem. Maybe you can help.
thanks
Peter
All replies (44)
Monday, November 20, 2017 8:28 PM ✅Answered | 1 vote
The last Update (KB4048955) did the trick. Everything is working again now.
Friday, November 3, 2017 8:03 AM | 1 vote
I just tried removing the WAN miniport devices like stated here (https://social.technet.microsoft.com/Forums/en-US/6ec6b6b4-5137-4cac-b62e-8709b72aeec2/windows-10-creators-update-and-vpn-issues?forum=win10itpronetworking) but it did not help, still get the 809 error.
Friday, November 3, 2017 8:14 AM | 1 vote
Hi,
got a similar problem, error code 789. For both devices, Surface Pro 3 and Lumia 950 L2TP/IPSEC has worked like a charm. But since update to build 1709 (Windows 10 Pro and Windows 10 mobile) I got the same error for both devices.
I have tried removing the WAN miniport adapters without success, I got still the error.
Because the release notes of 1709 stated, there has been changes on VPN, I assume, there is a bug now.
Best regards
Thomas
Friday, November 3, 2017 1:09 PM
One more thing. The registry setting for AssumeUDPEncapsulationContextOnSendRule is set correctly, unless there was something changed in the creators update at this end.
Saturday, November 4, 2017 7:12 PM
I've completed a rollback from 1709 to previous version of windows - before the 1709 release - and the VPN began to work correctly - other components of Windows, such as mail, calendar and other app functions were then broken, but the VPN did work. I've reinstalled the 1709 release to fix the rabbits I spent all last night chasing, and as of this morning can use my email and other windows components, but VPN is out like a light.
I reached out to their organization, tried the few of their suggestions, which of course didn't work - and am back to square one. without working VPN. I did try several other versions of VPN from different providers - and none of them seemed to fare any better.
Saturday, November 4, 2017 11:58 PM
Ever since I installed 1703, VPN stopped working.
I was hoping with 1709 they would have fixed it but it looks like they haven't from what I've been reading. I guess I'll have to be patient to see if they will fix it or not.
Thursday, November 9, 2017 12:25 PM
Hi Peter,
First, we need to double confirm that whether the configuration is the expected or not, we can refer to the following:
http://kswp01.azurewebsites.net/?p=116
Second, we can check whether there is any specified client VPN error (RasClient and RasMan) when issue happens, somethings like the following snapshots:
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Thursday, November 9, 2017 3:21 PM | 1 vote
Hi Carl,
thank you for the detailed answer, I have gone through the guide and added the LAN Routing and NAT configuration. Unfortunately this did not change anything. I have checked the following connections:
Win 10 Laptop from withing LAN (WLAN) --> connection succeded
Win 10 Laptop from outside (WWAN) --> connection failed with 809 VPN Error, No error on Server though
Android mobile from within (WLAN) --> connection succeeded
Adroind mobile from outside (WWAN) --> connection succeeded
As the connection from outside also succeeded from Win 10 latpop before update 1709 and the android still can connect from outside, I suspect the update as reason. Maybe some ciphers or hash algorithms have changed or were disabled?
These are connection details:
CoID={EE26BB91-4822-491B-9E30-DD293B90EBC1}: Der Benutzer "********" hat eine VPN-Verbindung mit einem per-user-Verbindungsprofil mit dem Namen "VPN" angewählt. Die Verbindungseinstellungen lauten:
Dial-in User = Peter
VpnStrategy = L2TP
DataEncryption = Require
PrerequisiteEntry =
AutoLogon = No
UseRasCredentials = Yes
Authentication Type = MS-CHAPv2
Ipv4DefaultGateway = Yes
Ipv4AddressAssignment = By Server
Ipv4DNSServerAssignment = By Server
Ipv6DefaultGateway = Yes
Ipv6AddressAssignment = By Server
Ipv6DNSServerAssignment = By Server
IpDnsFlags =
IpNBTEnabled = Yes
UseFlags = Private Connection
ConnectOnWinlogon = No
IPsec authentication for L2TP = Pre-shared key.
Maybe there are tools do debug the connection initialization / handshake?
Thursday, November 9, 2017 7:43 PM | 1 vote
Hi,
here is the information from my attempt, still not working:
Der Benutzer "SYSTEM" hat eine Verbindung mit dem Namen "SU" gewählt, die Verbindung konnte jedoch nicht hergestellt werden. Der durch den Fehler zurückgegebene Ursachencode lautet: 789.
CoID={50214175-7D56-4949-9D01-620C07A386F3}: Der Benutzer "SYSTEM" hat eine VPN-Verbindung mit einem per-user-Verbindungsprofil mit dem Namen "SU" angewählt. Die Verbindungseinstellungen lauten:
Dial-in User = tmaesing
VpnStrategy = L2TP
DataEncryption = Requested
PrerequisiteEntry =
AutoLogon = No
UseRasCredentials = Yes
Authentication Type = MS-CHAPv2
Ipv4DefaultGateway = Yes
Ipv4AddressAssignment = By Server
Ipv4DNSServerAssignment = By Server
Ipv6DefaultGateway = Yes
Ipv6AddressAssignment = By Server
Ipv6DNSServerAssignment = By Server
IpDnsFlags =
IpNBTEnabled = Yes
UseFlags = Private Connection
ConnectOnWinlogon = No
IPsec authentication for L2TP = Pre-shared key.
Best regards
Thomas
Saturday, November 11, 2017 2:52 PM
I am having a similar problem with with smart card VPN authentication after the 1709 update. I cannot connect to a VPN with smart card authentication, it just hangs when I click connect and never prompts for a PIN. I have tried with a few Yubikey 4 smart cards in PIV mode and also a PIVKEY C910. Same problem with both smart cards. Strange thing is it works fine with certificate authentication where the cert is loaded in the personal store.
I have a Windows Server 2016 server that is fully patched that I am trying to connect to.
Looks like something is broken with the builtin VPN client and 1709...
Monday, November 13, 2017 12:50 PM | 1 vote
Problem with VPN in 1709.
I can connect to my network via VPN. I have internet connection via VPN if I am using Mozilla FireFox ;)
Any thing related to IE, EDGE like Visual Studio and TFS not working anymore.
This just happens after upgrade to 1709, all was good before upgrade.
Tuesday, November 14, 2017 6:17 PM
Just wanted to say, I'm having the same issue. It seems some users on my network are fine.
Maintaining VPN availability for Windows 10 hosts has been an ongoing battle. As others have noted, I have Android, Linux and Mac systems connecting to L2TP without issue as well as Win 7/8.1 systems.
I have PPTP setup on this and another server and I can connect to both.
fyi here's my connection details
CoId={D9CD0170-2DF4-41F7-927A-E95B0D972985}: The user hhhh has started dialing a VPN connection using a per-user connection profile named hhhh. The connection settings are:
Dial-in User = hhhh
VpnStrategy = L2TP
DataEncryption = Requested
PrerequisiteEntry =
AutoLogon = No
UseRasCredentials = Yes
Authentication Type = MS-CHAPv2
Ipv4DefaultGateway = Yes
Ipv4AddressAssignment = By Server
Ipv4DNSServerAssignment = By Server
Ipv6DefaultGateway = Yes
Ipv6AddressAssignment = By Server
Ipv6DNSServerAssignment = By Server
IpDnsFlags =
IpNBTEnabled = Yes
UseFlags = Private Connection
ConnectOnWinlogon = No
IPsec authentication for L2TP = Pre-shared key.
Thursday, November 16, 2017 7:51 PM
Same thing for me. IE, Edge fails to connect when on VPN.
FireFox works.
Thursday, November 16, 2017 8:30 PM | 3 votes
I am also in the same boat. My FortiClient SSLVPN is not able to stablish a connection just after Fall Creator's update. Another workmate told me that he experienced the same problem. There is not any advice on Fortinet's support page. I have read that MS has disabled by default these cryptographic protocols in this update:
TLS_RSA_WITH_RC4_128_MD5
TLS_RSA_WITH_RC4_128_SHA
I tried enabling them again, just creating the subkey
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Ciphers\RC4 128/128, and creating a DWORD entry named "Enabled" with value 0xffffffff
However it doesn't work. Any other hint?
Saturday, November 18, 2017 9:51 AM
Hi,
after the last update with my environment it is working again with Windows 10 Pro and Windows 10 mobile.
Best regards
Thomas
Saturday, November 18, 2017 7:01 PM
Had high hopes for the update, but continue with the 809 error.
Sunday, November 19, 2017 8:17 AM | 1 vote
yes,remove Wan miniport devices not help！
Sunday, November 19, 2017 9:17 AM
Same problem here. Using FortiClient SSL VPN inside Internet Explorer (with Compatibility Setting enabled), running on Windows 10. After updating to Fall Creators version 1709 the vpn has stopped working. After entering username and 8-digit RSA token from my mobile phone, FortiClient gives the usual Tunnel Mode status screen, and then hangs with the status message "Collecting information...".
Reverting back to Windows 10 version 1703 fixed my FortiClient SSL VPN problem.
Tuesday, November 21, 2017 3:01 PM | 3 votes
KB4048955 did not resolve it for me. Edge and IE broken when VPN is running. Firefox works however
Monday, November 27, 2017 4:13 PM | 1 vote
Seemed to take a combination of all reported solutions, KB4048955, registry patch, and uninstalling WAN Miniports. Thanks all for you help
Monday, November 27, 2017 5:07 PM
I mean, if it takes a number of steps like that then it's not really a resolved.
Wednesday, November 29, 2017 2:41 PM
There might be a number of different factors involved after a major update like this, but in our network (L2TP VPN with NAT) I observed two scenarios with the following solutions:
- Re-apply this (already done in the past, which this update seems to have reset):
netsh advfirewall set global ipsec ipsecthroughnat serverandclientbehindnat
(run from elevated command prompt, then reboot)
- Go and check the "classic" Control Panel settings for the VPN connection (not under the more limited "modern" Settings), and make sure that the needed options are still set. In our specific scenario, under Security/Authentication, none of the radio buttons ("Use EAP", "Allow these protocols") was set any longer after the update. Selecting [x] Allow these protocols and [x] Microsoft CHAP Version 2 did the trick.
Monday, December 4, 2017 7:39 AM | 1 vote
You should use PowerShell
Enable-TlsCipherSuite -Name "TLS_RSA_WITH_RC4_128_MD5"
Enable-TlsCipherSuite -Name "TLS_RSA_WITH_RC4_128_SHA"
Thursday, December 7, 2017 10:11 AM
I have tested it, but it doesn't work (Forticlient SSL VPN & Windows 10 1709)
Wednesday, December 13, 2017 7:32 PM
did you execute power shell as an administrator ?
Tuesday, December 19, 2017 11:58 PM
Yes, I did. But it's still not working.
Wednesday, December 20, 2017 11:39 PM
I have similar problem. After update to Win 10 1709 I have problem with IKEv2 connection (strongswan on server side).
Win give me this errors :
Win GUI : Policy match error
Event ID 20227 :
The error code returned on failure is 13868
Event ID 20226
The reason code returned on terminate is 631
Friday, December 29, 2017 10:00 AM | 1 vote
I had an issue where I could connect to the VPN, but it would only work for several seconds. The connection would stay connected, but I couldn't reach any of the remote devices.
I uninstalled all (including ipv6, etc.) WAN Miniport devices in Device Manager, then did the Action -> Scan for hardware changes, and without even rebooting, it fixed the issue.
Tuesday, January 2, 2018 5:54 PM
I'm spitting nails. Remote Unifi USG as VPN server. L2TP w/IPSEC. On the same network, my Android connects, an Apple MacBook connects, Windows 10 Pro connects....Windows 10 Edu nope. This is unacceptable. This is required for work.
Everything I've done:
- Windows 10 Edu fully updated 1709, build 16299.125
- Verified and reverified PSK, login details, CHAPv2
- Deleted and re added VPN
- Registry "AssumeUDPEncapsulationContextOnSendRule"
- Registry "ProhibitIpSec"
- Registry "AllowL2TPWeakCrypto"
- Reinstall WAN miniport drivers
- Disabled firewall
- Ran powershell commands for the ciphers
- "netsh advfirewall set global ipsec ipsecthroughnat serverandclientbehindnat"
- Rebooted 5 Million times
- Reinstalled Windows, TWICE!!!
Nothing works. Anybody else?
Tuesday, January 2, 2018 10:57 PM
This is what my router says:
Jan 2 15:20:54 USG kernel: cavium_delete_hndl : NULL Sa/SA Handle : with x 800000000cf3c800 x->sa_handle
(nil)Jan 2 15:20:59 USG xl2tpd[3510]: Maximum retries exceeded for tunnel 60869. Closing.
Jan 2 15:21:33 USG kernel: cavium_delete_hndl : NULL Sa/SA Handle : with x 800000000cd02400 x->sa_handle
(nil)Jan 2 15:21:33 USG xl2tpd[3510]: Connection established to EXTERNAL IP, 44578. Local: 10055, Remote: 36760 (ref=0/0). LNS session is 'default'
Jan 2 15:21:33 USG xl2tpd[3510]: Call established with EXTERNAL IP, Local: 2073, Remote: 31507, Serial: -405737441
Jan 2 15:21:33 USG pppd[11896]: pppd 2.4.4 started by root, uid 0
Jan 2 15:21:33 USG pppd[11896]: Connect: ppp2 <-->
Jan 2 15:21:33 USG zebra[696]: interface ppp2 index 120 <POINTOPOINT,NOARP,MULTICAST> added.
Jan 2 15:21:34 USG zebra[696]: interface ppp2 mtu changed from 1500 to 1400
Jan 2 15:21:34 USG pppd[11896]: rc_avpair_gen: received unknown attribute 64 of length 4: 0x00000003
Jan 2 15:21:34 USG pppd[11896]: rc_avpair_gen: received unknown attribute 65 of length 4: 0x00000001
Jan 2 15:21:34 USG pppd[11896]: Unsupported protocol 'Compression Control Protocol' (0x80fd) received
Jan 2 15:21:34 USG zebra[696]: warning: PtP interface ppp2 with addr 10.255.255.0/32 needs a peer address
Jan 2 15:21:34 USG zebra[696]: interface index 120 was renamed from ppp2 to l2tp2
Jan 2 15:21:34 USG pppd[11896]: Cannot determine ethernet address for proxy ARP
Jan 2 15:21:34 USG pppd[11896]: local IP address 10.255.255.0
Jan 2 15:21:34 USG pppd[11896]: remote IP address 192.168.8.3
Jan 2 15:21:34 USG zebra[696]: interface l2tp2 index 120 changed <UP,POINTOPOINT,RUNNING,NOARP,MULTICAST>.
Jan 2 15:21:48 USG xl2tpd[3510]: Maximum retries exceeded for tunnel 9479. Closing.
Jan 2 15:21:48 USG zebra[696]: interface l2tp1 index 119 changed <POINTOPOINT,NOARP,MULTICAST>.
Jan 2 15:21:48 USG zebra[696]: interface l2tp1 mtu changed from 1400 to 1500
Jan 2 15:21:54 USG pppd[9872]: Connection terminated: no multilink.
Jan 2 15:21:54 USG zebra[696]: interface l2tp1 index 119 deleted.
Jan 2 15:21:54 USG pppd[9872]: Modem hangupFAKEUSER@USG:~$
Seems...
Jan 2 15:21:34 USG pppd[11896]: Unsupported protocol 'Compression Control Protocol' (0x80fd) received
...looks like the culprit. Anybody know?
Wednesday, January 3, 2018 6:25 AM | 1 vote
I have similar problem. After update to Win 10 1709 I have problem with IKEv2 connection (strongswan on server side).
Win give me this errors :
Win GUI : Policy match error
Event ID 20227 :
The error code returned on failure is 13868Event ID 20226
The reason code returned on terminate is 631
My problem is solved, because :
RSA/AES Encryption for IIS is disabled
We recommend that users use CNG encryption provider.
So windows 1709 change IPSEC policy from :
IKE:AES_CBC_128/HMAC_SHA1_96/PRF_HMAC_SHA1/MODP_1024
to :
IKE:AES_GCM_16_128/PRF_HMAC_SHA1/MODP_1024
So, I've increased security via registry (restart is not needed):
"HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Rasman\Parameters
NegotiateDH2048_AES256"
dword : 2
to :
IKE:AES_CBC_256/HMAC_SHA1_96/PRF_HMAC_SHA1/MODP_2048
and this encryption is supported by my router and all works.
Max
Wednesday, January 3, 2018 9:37 AM
Thanks for the reply, but
NegotiateDH2048_AES256 DWORD: 2
doesn't fix it for me.
Wednesday, January 3, 2018 4:18 PM
izzyfanto,
Not sure why you'd get this series of errors. This looks like it is a PPP config problem, but I'm not really sure. You could try going into adapter options->properties->options->ppp settings and toggle some of those options. But it could also be server side.
Thursday, January 4, 2018 12:23 AM
Thanks so much for the replies, but alas that didn't help. I struggle to think that it's my router. Three other devices, three different brands all work fine. Only this fresh Windows 10 Edu is broke. I literally am putting off working because I refuse to use my Android phone to pinch and zoom for the server work that needs to be done. Thanks again for the reply
Thursday, January 4, 2018 3:16 AM
Wow. 3 days later, and way too much time, I figured it out! Put a post together at my blog detailing everything. Hope it helps someone. I can't post links yet: blog.izzyfanto.net/2018/01/unifi-usg-l2tp-vpn-ccp-mppe-and-windows.html
Saturday, January 6, 2018 12:50 PM
I have installed KB4056892 which as I understand should include KB4048955, since KB4056892 is a cummulative update. However my FortiClient SSL VPN inside Internet Explorer is still not working.
Thursday, February 1, 2018 1:57 PM
With me - i was just using old version of openVPN. After installing 2.44 released on 2017.09.26 everything is back on track.👌
Thursday, February 15, 2018 3:16 PM
Thanks a lot. it worked for me.
Thursday, February 15, 2018 4:42 PM
Recently I have had issues with the Forticlient SSL VPN and being able to access internal websites. Disabling ipv6 on the network adapters allowed us to access the sites again.
Wednesday, February 21, 2018 1:24 AM
Good afternoon,
Same issue with my Windows 10 box and seem to have the same line of code "noccp" in that /etc/ppp/options.xl2tpd file but I'm a little rusty on Linux. When I try to edit it, it says it is a read-only file. Any help would be appreciated.
EDIT: okay sudo lets me edit it, but once I erase the noccp line, then use :wq to write and quit, then reboot, when I come back to it, it's still there. I'm guessing its my cloud key reprovisioning it and writing over it. Don't know what to do now...
Thursday, February 22, 2018 2:42 PM
After a week of troubleshooting, this simple fix finally did it for me. Thanks!
Wednesday, February 28, 2018 3:27 AM | 1 vote
I had to remove the WAN Miniport for L2TP and apply this registry key, reboot the PC and my VPN started working.
Copy and paste the below into a notepad and save as L2TP.reg and let me know how it goes
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PolicyAgent]
"Start"=dword:00000003
"DisplayName"="@%SystemRoot%\System32\polstore.dll,-5010"
"ErrorControl"=dword:00000001
"ImagePath"=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,\
74,00,25,00,5c,00,73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,73,\
00,76,00,63,00,68,00,6f,00,73,00,74,00,2e,00,65,00,78,00,65,00,20,00,2d,00,\
6b,00,20,00,4e,00,65,00,74,00,77,00,6f,00,72,00,6b,00,53,00,65,00,72,00,76,\
00,69,00,63,00,65,00,4e,00,65,00,74,00,77,00,6f,00,72,00,6b,00,52,00,65,00,\
73,00,74,00,72,00,69,00,63,00,74,00,65,00,64,00,00,00
"Type"=dword:00000020
"Description"="@%SystemRoot%\system32\polstore.dll,-5011"
"DependOnService"=hex(7):54,00,63,00,70,00,69,00,70,00,00,00,62,00,66,00,65,00,\
00,00,00,00
"ObjectName"="NT Authority\NetworkService"
"ServiceSidType"=dword:00000001
"RequiredPrivileges"=hex(7):53,00,65,00,41,00,75,00,64,00,69,00,74,00,50,00,72,\
00,69,00,76,00,69,00,6c,00,65,00,67,00,65,00,00,00,53,00,65,00,43,00,68,00,\
61,00,6e,00,67,00,65,00,4e,00,6f,00,74,00,69,00,66,00,79,00,50,00,72,00,69,\
00,76,00,69,00,6c,00,65,00,67,00,65,00,00,00,53,00,65,00,43,00,72,00,65,00,\
61,00,74,00,65,00,47,00,6c,00,6f,00,62,00,61,00,6c,00,50,00,72,00,69,00,76,\
00,69,00,6c,00,65,00,67,00,65,00,00,00,53,00,65,00,49,00,6d,00,70,00,65,00,\
72,00,73,00,6f,00,6e,00,61,00,74,00,65,00,50,00,72,00,69,00,76,00,69,00,6c,\
00,65,00,67,00,65,00,00,00,00,00
"FailureActions"=hex:80,51,01,00,00,00,00,00,00,00,00,00,03,00,00,00,14,00,00,\
00,01,00,00,00,c0,d4,01,00,01,00,00,00,e0,93,04,00,00,00,00,00,00,00,00,00
"AssumeUDPEncapsulationContextOnSendRule"=dword:00000002
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PolicyAgent\Parameters]
"ServiceDllUnloadOnStop"=dword:00000001
"ServiceMain"="SpdServiceMain"
"ServiceDll"=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,\
00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,\
69,00,70,00,73,00,65,00,63,00,73,00,76,00,63,00,2e,00,64,00,6c,00,6c,00,00,\
00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PolicyAgent\TriggerInfo]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PolicyAgent\TriggerInfo\0]
"Type"=dword:00000004
"Action"=dword:00000001
"GUID"=hex:07,9e,56,b7,21,84,e0,4e,ad,10,86,91,5a,fd,ad,09
"Data0"=hex:52,00,50,00,43,00,00,00,54,00,43,00,50,00,00,00,25,00,77,00,69,00,\
6e,00,64,00,69,00,72,00,25,00,5c,00,73,00,79,00,73,00,74,00,65,00,6d,00,33,\
00,32,00,5c,00,73,00,76,00,63,00,68,00,6f,00,73,00,74,00,2e,00,65,00,78,00,\
65,00,00,00,70,00,6f,00,6c,00,69,00,63,00,79,00,61,00,67,00,65,00,6e,00,74,\
00,00,00,00,00
"DataType0"=dword:00000002
Wednesday, April 18, 2018 5:32 AM | 1 vote
didn't help anything above
I've deleted last cumulitive update from 11.04.2018 - vpn started work fine, without any other manipulations.
I'm using win10 1709, vpn - l2tp/ipsec
UPD: helped, but not for long... I've forgot to disable or pause updates and during next restart OS installed some updates - vpn stopped work. deleting all of udpates for this day, didn't help.
also I forget to write down KB number that I've deleted first.
will try same at the evening for my home PC. will see.
UPD2: tried do same with mz home PC - no luck, doesn't work.
I've deleted updates one by one, restarted after each, didn't help.
waiting for fix from microsoft
Tuesday, October 23, 2018 3:12 PM
What happened with the good old habits from 90s, to have unit testing, then system integration testing, then performance testing, then UAT/QA testing, then pre-prod, and then production?
How can the software be released without the above steps? Who allowed that to happen? That one who allowed this all to happen, should be fired.