Windows 2022 Network Services Restart Issue

[discoveranother]

Hello,

 

Installed a Windows Standard 2022 DC Server with Hyperv Manager.

 

Anyway, cut a long story short.

 

All seemed ok until today, oddly, on the Windows 2022 DC, in services.msc both the Network Location Awareness and Network List Service although both are running, when I tried to restart them they both come up with the Error 1061 "The service cannot accept control messages at this time".

 

There was a bit of a panic as it's the first day back for the customer and at first the server was not being picked up, and nslookup was not pointing to the right server.

 

Anyway, after a reboot, nslookup is now ok and all clients connect and pick up GP etc, etc but the Error 1061 still occurs, even though all clients are working fine now and connecting to the server. I am at a miss as to why the Error should occur out of curiosity.

 

Once last thing if I may, the virtual network adapter on the server shows as "network" instead of the domain name. I wasn't sure if this was a Windows 2022 thing with the way virtual network adapters are now setup within Windows 2022 as SET.

 

Thanks all

Edited April 20, 2022 by discoveranother

[discoveranother]

Hello,

 

Installed a Windows Standard 2022 DC Server with Hyperv Manager.

 

Anyway, cut a long story short.

 

All seemed ok until today, oddly, on the Windows 2022 DC, in services.msc both the Network Location Awareness and Network List Service although both are running, when I tried to restart them they both come up with the Error 1061 "The service cannot accept control messages at this time".

 

There was a bit of a panic as it's the first day back for the customer and at first the server was not being picked up, and nslookup was not pointing to the right server.

 

Anyway, after a reboot, nslookup is now ok and all clients connect and pick up GP etc, etc but the Error 1061 still occurs, even though all clients are working fine now and connecting to the server. I am at a miss as to why the Error should occur out of curiosity.

 

Once last thing if I may, the virtual network adapter on the server shows as "network" instead of the domain name. I wasn't sure if this was a Windows 2022 thing with the way virtual network adapters are now setup within Windows 2022 as SET.

 

Thanks all

 

 

Just to add further to clarify. The DC is Windows 2022 and the VM is Windows 2019. The Windows 2019 VM shows the correct domain on the teamed hyperv network adapter but oddly on the Windows 2022 DC the teamed hyperv virtual network adapter shows as "network". I wasn't sure if this is how it now shows on Windows 2022 as the teamed Nics are now configured using powershell with the SET command.

 

DNS records are fine, they show as they should.

 

Adding new clients to the domain works fine.

 

Thanks

[Steve21]

I think you’re mixing up a few things here as you’re not supposed to manually restart NLA etc. what’s the actual issue you’re getting for you to try that?

 

 

But in terms of actually doing what you’re trying both NLA and NLS spawn svchost.exe processes, while they’re running you can’t stop the services, and both services will automatically restart their svchost.exe if you close it after a few seconds

 

So if your every quick in killing both svchost.exe and stopping services it’d do what you want. But It’s not at all designed to do that

 

Steve

[discoveranother]

I think you’re mixing up a few things here as you’re not supposed to manually restart NLA etc. what’s the actual issue you’re getting for you to try that?

 

 

But in terms of actually doing what you’re trying both NLA and NLS spawn svchost.exe processes, while they’re running you can’t stop the services, and both services will automatically restart their svchost.exe if you close it after a few seconds

 

So if your every quick in killing both svchost.exe and stopping services it’d do what you want. But It’s not at all designed to do that

 

Steve

 

Thanks for the reply.

 

Ok. We discovered with some versions of Windows server 2016, 2019 that if using hyper, sometimes the virtual network adapter does not immediately pick up the domain name after reboot but instead just uses 'network'. We discovered this was happening to others as well as a few forums suggested to use a scheduled task, which we always implemented and works perfect. What the scheduled task does is restarts the Network Location Service immediately on booting into Windows, this in turn changes the 'network' to domain name on the adapter. Works a treat.

 

This is what we also found with Windows 2022. However, network location service does not restart it throws up the error. The hyperv virtual network adapter shows as 'network' instead of the domain name. We weren't sure if this is how it is with Windows 2022 (Not a VM). The server also hosts a VM which is 2019. However, the VM virtual network adapter shows the domain name as it should. So is this how 2022 displays the network adapter compared to 2019 ?

[Steve21]

That’s generally a DNS issue as it only checks once for the domain connection and then caches the information until next restart (effectively what you’re overriding by forcing it to restart)

 

You can make a change to registry to make it keep retrying until it finds it though, which would remove the task workarounds (until the long term issue is sorted as to why it’s not detecting domain etc)

 

On one of the machines you get it happening to, add

HKLM\SYSTEM\CurrentControlSet\Services\NlaSvc\Parameters

With a DWORD named AlwaysExpectDomainController and set it to 1

 

Steve

[discoveranother]

That’s generally a DNS issue as it only checks once for the domain connection and then caches the information until next restart (effectively what you’re overriding by forcing it to restart)

 

You can make a change to registry to make it keep retrying until it finds it though, which would remove the task workarounds (until the long term issue is sorted as to why it’s not detecting domain etc)

 

On one of the machines you get it happening to, add

HKLM\SYSTEM\CurrentControlSet\Services\NlaSvc\Parameters

With a DWORD named AlwaysExpectDomainController and set it to 1

 

Steve

 

On the two images below.

 

In 2019 you would get this below :-

 

 

 

In 2022 it's this, same setup but using powershell to set the teamed nics as below :-

 

 

And here are the Nics :-

 

 

The DNS appears fine. No errors anywhere on the server or DNS tests or anything. All working fine.

 

The Nic Teaming on the Windows 2022 was done via powershell. SET is an alternative to the NIC teaming feature that Microsoft gave us way back in 2012. Windows Server 2012 and later required NIC teams to be created at the OS level, but you could bind a Hyper-V virtual switch to the NIC team, just as you can bind a virtual switch to any other physical network adapter. In contrast, SET lets you combine up to eight physical network adapters (the adapters have to be identical) into a Hyper-V virtual network adapter.

 

Switch embedded teams are switch-independent, meaning that the physical switches to which the teamed adapters are connected are unaware of the team's existence.

Edited April 20, 2022 by discoveranother

[Steve21]

That shouldn’t be any different, we use SET in 2019 (was in 2016 server)

 

My point with the DNS side was the only time NLA changes profiles is when it detects the DNS Name response on the NIC and if it’s not a domain one it won’t set the domain profile in NLA (say for example the service starts up too slow)

 

But that’s even if it’s just 1 drop it’ll then cache that response until you restart

 

The reg key just tells it to keep trying until it finds a response as it’s always expecting a domain response from DC

 

Steve

[discoveranother]

That shouldn’t be any different, we use SET in 2019 (was in 2016 server)

 

My point with the DNS side was the only time NLA changes profiles is when it detects the DNS Name response on the NIC and if it’s not a domain one it won’t set the domain profile in NLA (say for example the service starts up too slow)

 

But that’s even if it’s just 1 drop it’ll then cache that response until you restart

 

The reg key just tells it to keep trying until it finds a response as it’s always expecting a domain response from DC

 

Steve

 

Thanks. I'm at a loss even though everything connects fine and checking and double-checking everything on the server and event logs etc shows everything is working.

[LazyD]

https://community.spiceworks.com/topic/2359404-server-2022-hyper-v-can-t-restart-nla-network-list-no-domain-profile?page=1#entry-9472098

[discoveranother]

https://community.spiceworks.com/topic/2359404-server-2022-hyper-v-can-t-restart-nla-network-list-no-domain-profile?page=1#entry-9472098

 

Thank you for your reply and your private message.

 

Looks like editing the registry partially solved the issue for the OP in the thread but didn't solve the NLA Service Restart. But thanks, it's a beginning, I will give that a go.