What's new
  • Donate
    TheWindowsForum.com needs donations to stay online!
    Love TheWindowsForum.com? Then help keep it alive by sending a donation!

Microsoft fixes Windows DirectAccess connectivity issues

WELCOME TO THEWINDOWSFORUM COMMUNITY!

Our community has more than 50.000 registered members, and we'd love to have you as a member. Join us and take part in our unbiased discussions among people of all different backgrounds about Windows OS, Software, Hardware and more.

AFFASocial

Well-Known Member
VIP
Jun 26, 2021
223
143
OS
Windows 10
BR
Yandex.Browser 22.9.5.710

Microsoft fixes Windows DirectAccess connectivity issues​

  • November 14, 2022
  • 10:06 AM
  • 0

Windows

Microsoft has resolved a known issue causing connectivity problems for Windows customers using the DirectAccess service to access their organizations remotely without using a virtual private network (VPN).
According to Redmond, DirectAccess might not reconnect automatically after the impacted device experience connectivity issues.
Scenarios that could lead to this known issue include switching between access points or Wi-Fi networks and temporarily losing network connectivity.
The problems affect enterprise endpoints where admins have deployed Windows updates released since mid-October.
However, this issue shouldn't impact other remote access solutions such as VPN (sometimes called Remote Access Server or RAS) and Always On VPN (AOVPN), the recommended remote connection methods for Windows 10 or later.
Enterprise or home devices that don't use DirectAccess to remotely access enterprise resources are also unaffected.
The list of affected platforms includes both client and server Windows releases:
  • Client: Windows 11, version 22H2; Windows 10, version 22H2; Windows 11, version 21H2; Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2; Windows 10 Enterprise LTSC 2019
  • Server: Windows Server 2022; Windows Server 2019

Fixed via Known Issue Rollback​

Microsoft has addressed this issue via Known Issue Rollback (KIR), a Windows capability that allows reverting buggy Windows non-security fixes rolled out using Windows Update.
Once pushed, KIR-issued fixes usually reach all consumer and non-managed business devices within 24 hours, with affected users advised to restart affected systems to speed up the rollout.
IT admins must install and configure a KIR Group Policy associated with the systems' Windows versions to resolve the known issue on enterprise-managed Windows devices.
You can download the Group Policies by clicking the links below:
The procedure needed to deploy KIR fixes via Group Policies requires opening the Group Policy Editor and navigating to either Local Computer Policy or the Domain policy on your domain controller to select the Windows version you want to target.
You can find detailed information on deploying and configuring KIR Group Policies on Microsoft's support website.
Over the weekend, Redmond also addressed Windows Kerberos authentication issues after installing November 2022 cumulative updates on domain controllers.
 

Online statistics

Members online
2
Guests online
37
Total visitors
39
Top