Forum Discussion

DarienHawkins's avatar
DarienHawkins
Brass Contributor
Apr 27, 2024

Server 2025 Core ADDS DC, Network Profile Showing as "Public" and not as "DomainAuthenticated"

OS: Windows Server 20225 Standard Core (no GUI), build 26085.1 Role: ADDS, DNS ForestMode: Windows2025Forest DomainMode: Windows2025Domain Platform: Hyper-V guest   When standing up a clean Win...
adds
Network Location Awareness
Server
Server Issues
Windows Server 2025
Dread73's avatar
Dread73
Brass Contributor
Feb 22, 2025

It's now the END of February - and still no fix?

Ridiculous

LDR777's avatar
LDR777
Brass Contributor
May 11, 2025

I can confirm the easy fix is to define a local IPV6 address for the adapter. 

For example: fd12:3456:789a:0001:0000:0000:0000:0063 /64

My adapter immediately switched to the 'test.local' domain and persisted after reboot!

  • RaySumperl's avatar
    RaySumperl
    Copper Contributor
    May 12, 2025

    Interesting, my IPv4 address is hardcoded and my IPv6 is address is DHCP and gets an address from my Cisco equipment. Is an IPv6 DHCP address not good enough?

    Ray

    • LDR777's avatar
      LDR777
      Brass Contributor
      May 12, 2025

      Something to try. I haven't tried that in my lab, since I don't normally have an IPV6 DHCP source, but a lack of an IPV6 address will fail the Domain awareness code used in lieu of NLA since it's shut down on a 2025 DC. That code appears to issue ICMP against the IPV6 interface periodicaly, and a failure automatically places the card into public or private per the unrecognized interface policy.

      • RaySumperl's avatar
        RaySumperl
        Copper Contributor
        May 14, 2025

        I setup a 2025 domain controller in my lab this morning, hard coded an IPv4 and an IPv6 address and still the network shows public. I give up!

Resources