Forum Discussion
Solved
Windows Server 2022 with NIC Teaming does apply Private connection profile
Hi I have a physical server with Windows Server 2022 (21H2) installed and a NIC Teaming (LACP with 2 NICs, LB mode: dynamic) configured. After a restart of the server Windows applies the Private (F...
- Dear all
sorry for my late update on this issue:
I finally managed to solve this by setting the following reg key on our 2022 servers:
Key path: HKLM\SYSTEM\CurrentControlSet\Services\NlaSvc\Parameters
REG_DWORD: AlwaysExpectDomainController = 1
In addition you need to properly configure the DNS suffix on the (lan) interface manually (you can't do this by GPO, afaik).
Unfortunately the reg key is not very well documented (...basically not at all;-). I found some hints on this in some forum articles. It basically tells the NLA service to wait for a DC to respond forever. For domain-joined servers this should always be the case 😉
Best regards,
Phil
Any progress or updates? Please don't forget to mark helpful replies
Hi
I tried to put the DNS Client Service (= Dnscache) as dependency, but that did not resolve the issue.
What you suggested would require to have the DNS Server (=DNS) service installed, which is not the case in my scenario.
I tried to put the DNS Client Service (= Dnscache) as dependency, but that did not resolve the issue.
What you suggested would require to have the DNS Server (=DNS) service installed, which is not the case in my scenario.
Most windows domain controller also run integrated active directory DNS, there may be some other complications with your systems. I'd suggest starting a case here with product support.
Hi! I am Scout and I am facing the issue you face. So, please guide me on how I can install the DNS server and run the device properly.