Today I experienced another issue with Windows 10 upgrade (to the Fall Creators Update) and the VPN server functionality. After quick research, it turned out that errors are written to the event log after each client's attempt to connect:
Friday, December 29, 2017
Wednesday, August 23, 2017
VPN server not working, or how to fix Routing and Remote access service
As everybody knows, system upgrades can from time to time cause more issues that they are supposed to fix. Something similar happened to me after upgrade of my home server from previous Windows 10 to Creators Update. All went good, except... VPN server was not starting any more.
Tuesday, August 22, 2017
VPN server not working after sleep, or how I fixed what Microsoft neglected
So one day I found myself in situation that required VPN connection to my home computer from outside world. As I am running on Windows, I obviously decided to use build-in VPN server feature. Few minutes and I was done. Easy as that. I did what was needed and put computer in sleep. Next day I waked up the computer, tried to connect... and nothing. Quick search showed that this is known issue and workaround does not exits. Luckily, I had a bright moment and tried to manually suspend the responsible RemoteAccess service prior to sleep. Tried to suspend the computer, wake up, start the service and Violaaa! It worked. So I decided to create small utility that does just that.
Subscribe to:
Posts (Atom)