Domain joined Windows Server 2019 - not connected to domain network

Question

I have two Windows Server 2019 machines in my infrastructure which are connected on 'Guest or Public networks' and I have been unable to switch to domain network.

I have tried many solutions gathered around the Internet but none has been successful so far :

Restart NLA service
Replace NIC
Check DNS (properly registered)

I also notice that Powershell command 'Get-NetConnectionProfile' returns nothing. I guess there is no profile identified. The problem is that the machines are unable to get Windows Update packages from our WSUS machine.

What else can I do?

When you say that you checked DNS, what exactly did you check? — joeqwerty, Jan 27 '21 at 13:40
I have three DNS servers which are all registered in these two machines. I can nslookup each of them seamlessly. — Charlypop, Jan 27 '21 at 14:19

score 0 · Answer 1 · answered Jan 27 '21 at 15:10

0

The NCP (Network Connection Profile) can be set "the hard way" through in registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\Profiles

When you expand the Profiles key, you will see sub-keys with different GUIDs. Those are the networks you have "joined" till date and the key Description contains the networks name. Mostly DNS names, if suffixes were distributed through DHCP.

I you found "your" profile, change the DWORD value of Category accordingly:

0 (for "Public")
1 (for "Private")
2 (for "Domain")

answered Jan 27 '21 at 15:10

bjoster

4,423
5
22
32

I have just checked but that key is not populated in my case. – Charlypop Jan 27 '21 at 15:24
Then your NCP is not populated and the NLA is defunc'd. Check if NLA, Listener and Logon Serives are up and running and that no errors are beeing logged. – bjoster Jan 27 '21 at 15:33
1

Ok I will check these and let you know. Thank you for your time. – Charlypop Jan 27 '21 at 16:48

Domain joined Windows Server 2019 - not connected to domain network

1 Answers1