Server network defaults to Public network after reboot

[Delgado]

Environment is 2 windows 2012 servers (separate individual domain controllers) and this new 2022 server (in its own domain).

 

It's a 2022 server standard edition (with desktop) build on a new Dell server. Fixed IP address.

 

Server network defaults to Public network after reboot instead of Domain Network.

 

This only happens occasionally after a reboot. The IP4 config defaults to a DHCP address! This throws out the stub forward zone records of two other domains on site. So my clients PC's can't get a login.

 

For the test client PC's, which are in the 2022 domain, I'm having to work within the confines of the existing DHCP server leases from one of the 2012 site servers. So although the Clients can resolve the domain controller via the stub zone records of the other servers - it's frustrating when it happens.

 

It's not a consistent error. Fixed by re-configuring a fixed IP again on the server.

 

I wonder if it's related to IP6. Any suggestions most welcome.

 

I'm on a long server migration strategy - to finally switch off one of the 2012 servers.

[mavhc]

Is this a VM, and if not, why not?

[andy_b]

Easiest "fix" for this is to make the NLA service dependant on the DNS service. (That is the Public vs Domain problem). Edited January 30, 2023 by andy_b
Clarity

[Delgado]

Is this a VM, and if not, why not?

 

I'm old school. I wouldn't know a VM if it bit me on my Harris. It's still a test server and not in production yet, though it is on the LAN with some client PC's. But obviously I want to move forward and put it into production if I can iron out the teething problems with it. Everything has gone swimmingly so far.

[Delgado]

Easiest "fix" for this is to make the NLA service dependant on the DNS service.

 

Thanks. I will be googling the meaning of that when back in. I should add that I left the IP6 setting as 'obtain'. I don't know if that is the correct setting - this will have to be the site DHCP server at some point.

Edited January 30, 2023 by Delgado

[mavhc]

You should really make it a VM, future you will thank me later.

 

Why would a static IP change to DHCP? Does it a) think it's a different Ethernet device? or b) is the IP in use? or c) something else?

 

What do the event logs say?

[Delgado]

You should really make it a VM, future you will thank me later.

 

Why would a static IP change to DHCP? Does it a) think it's a different Ethernet device? or b) is the IP in use? or c) something else?

 

What do the event logs say?

 

I haven't checked the event logs. I can see what has occurred when I check the adapter TCP/IP config. I made a reservation on the current DHCP server for it and it is fixed for IP4.

[Davit2005]

Have you looked at doing conditional forwarders on the existing DNS. That is what I did last time I migrated to a new AD domain then created a trust between the 2 domains, assuming you are migrating to a new domain as well as servers.

 

As for the Public, yep I had that problem too once, cannot remember the fix apart from a whole load of profanities which made me feel better at the time.

 

DNS Servers should always be set to fixed IP Address i.e. static set on the DNS server itself in the IPv4 (and/or IPv6) settings. No need to set a static IPv6 unless using IPv6.

Edited January 30, 2023 by Davit2005

[Delgado]

Have you looked at doing conditional forwarders on the existing DNS. That is what I did last time I migrated to a new AD domain then created a trust between the 2 domains, assuming you are migrating to a new domain as well as servers.

 

As for the Public, yep I had that problem too once, cannot remember the fix apart from a whole load of profanities which made me feel better at the time.

 

The simple stub zones on the other servers seemed to be working fine, when it's on the right IP address. I do miss the free use of profanity though and can only silently mouth the words in school.

 

On the domains I'm trying to eventually migrate both the two 2012 domains to two separate 2022 server domains. Ideally with the minimum of disruption.

Edited January 30, 2023 by Delgado

[Delgado]

Easiest "fix" for this is to make the NLA service dependant on the DNS service. (That is the Public vs Domain problem).

Many thanks. Some solutions suggest changing the NLA service to a delayed start. But some still report issues. This looks a pretty solid fix:

 

NLA uses dns to see what kind of network it is. If DNS is not fully functional at the time NLA starts, it cannot determine the domain existence. Simple fix: make nla dependant on DNS server

 

start regedit

navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NlaSvc

Edit 'DependOnService

Add new line with "DNS"

 

I'm still not wild about how vague IP6 is defined for Windows server 2022. I'm willing to do some hex arithmetic if they are.

Edited January 30, 2023 by Delgado

[Davit2005]

It is not recommended to disable IPv6. If you are not using it then jus don't bother setting an IPv6 address, jus let it do it's own thing.

[Delgado]

It is not recommended to disable IPv6. If you are not using it then jus don't bother setting an IPv6 address, jus let it do it's own thing.

 

Fair enough like. It's a bit daft that there are only two choices: 1) Obtain IP6 address (from where ?) 2) Set one.