Remote Desktop requires old user name after account rename

Issue

User account name was changed in via Control Panel > User Accounts > Change Your Account Name. While local login screen shows new user name, Remote Desktop Connection only works when the old login name is provided.

L2TP/IPsec VPN from Windows 10 fails with error "remote server is no responding..."

Background

  • Synology DS413 NAS configured as L2TP/IPSec VPN server and located behind Draytek Vigor 2860 NAT.
  • L2TP VPN pass through enabled on Draytek Vigor Router (VPN and Remote Access > Remote Access Control > remove checkboxes from Enable IPSec VPN Service and Enable L2TP VPN Service).
  • UDP ports 1701, 500 or 4500 are forwarded from Draytek Router to Synology NAS.
  • Windows 10 Pro client trying to connect using built-in Windows VPN client.
  • VPN connection over PPTP works fine.

Issue

  • VPN connection over L2TP/IPsec fails with following error:

    The network connection between your computer and the VPN server could not be established because the remote server is not responding. This could be because one of the network devices (e.g, firewalls, NAT, routers, etc) between your computer and the remote server is not configured to allow VPN connections. Please contact your Administrator or your service provider to determine which device may be causing the problem.

Windows Defender - The threat service has stopped. Restart it now

Issue

Windows 10 Security Centre shows red X next to Virus & thread protection. Status reads "The threat service has stopped. Restart it now."

Clicking Restart Now button doesn't help. Following error is displayed "Unexpected error. Sorry, we ran into a problem. Please try again."

Newsletter

Subscribe to receive occasional updates on new posts.
Your email will not be used for any other purpose and you can unsubscribe at any time.
Please wait