Strange "Network Connectivity Assitant Service" error on my Domain Controllers

ME 311 Reputation points
2022-03-29T19:52:24.173+00:00

Going through my system logs today I discovered that both my Server 2019 Virtual Domain Controllers seem to have this error firing off every 2 minutes or so:

==

The Network Connectivity Assistant service terminated with the following service-specific error:
The request is not supported.

==

It seems to have started in the middle of the month (16th March), but gives me no more detail than the above to go on. Google doesn't seem to turn up anything revealing. I did not make any config changes on the 16th (last was the installation of the monthly OS patch on the 11th).

I'm not sure how to even begin to track this down - the event itself gives nothing and there does not appear to be another regular event pre-empting it other than that service entering the stopped state. Has anyone any insight into what may be the problem here? These are Hyper-V VMs running Windows Server 2019's usual cast of AD components and basically nothing else.

Windows Server 2019
Windows Server 2019
A Microsoft server operating system that supports enterprise-level management updated to data storage.
3,167 questions
Active Directory
Active Directory
A set of directory-based technologies included in Windows Server.
5,171 questions
Windows Network
Windows Network
Windows: A family of Microsoft operating systems that run across personal computers, tablets, laptops, phones, internet of things devices, self-contained mixed reality headsets, large collaboration screens, and other devices.Network: A group of devices that communicate either wirelessly or via a physical connection.
529 questions
0 comments No comments
{count} votes

4 answers

Sort by: Most helpful
  1. Dave Patrick 418.3K Reputation points MVP
    2022-03-29T19:57:47.95+00:00

    What other roles are installed? Hopefully not RRAS vpn / direct access. Direct access would be a conflicting role, the multi-homing would also cause no end to grief for active directory DNS.

    --please don't forget to upvote and Accept as answer if the reply is helpful--


  2. Dave Patrick 418.3K Reputation points MVP
    2022-03-29T20:39:27.62+00:00

    Ok, what is the startup type? It should be set to Manual startup

    --please don't forget to upvote and Accept as answer if the reply is helpful--


  3. Dave Patrick 418.3K Reputation points MVP
    2022-03-30T13:03:25.883+00:00

    Seems you'll need to get to the bottom of what is triggering it to run. As far as I know it's used for Direct Access (RRAS role). Procmon may help you in this regard.
    https://learn.microsoft.com/en-us/sysinternals/downloads/procmon

    --please don't forget to upvote and Accept as answer if the reply is helpful--


  4. Dave Patrick 418.3K Reputation points MVP
    2022-03-30T14:12:06.34+00:00

    Sounds good then, it's by far the simplest solution, after patching it should only take 30 mins or so to have the new one stood up. Might also take the opportunity to split the file server role off to another virtual machine which makes administration tasks less complex.

    --please don't forget to upvote and Accept as answer if the reply is helpful--