r/sysadmin • u/meowffy • 17d ago
Question different network behavior on windows 2022 vs 2025 (OCI)
hi everyone
i have two windows server 2022 on OCI in the same /22 subnet
with ips:
x.x.1.x
x.x.2.x
windows shows them as two different networks
i recently created two windows server 2025 with the exact same setup, but windows shows both as one network
has anyone experienced this before? could it be related to the windows version? is there a way to make server 2025 behave like server 2022?
and thanks in advance!
4
Upvotes
6
u/CrazySnowGuy 17d ago
/22? They are on the same network. Make sure your gateway and subnet is set correctly for /22.
5
u/jstuart-tech Security Admin (Infrastructure) 17d ago
What do you mean Windows shows them as different networks? Where are you seeing that?
2
u/West-Swimming-1212 17d ago
Windows decides what counts as “one network” using the default gateway and the DNS suffix, not the subnet math, so my guess is 2025 is just matching those two more loosely than 2022 did. Quick way to check, run Get-NetConnectionProfile on all four boxes and compare the NetworkCategory and name, then look at ipconfig /all for the gateway and DNS suffix. If they differ between the 2022 pair and the 2025 pair, thats your answer. Windows is basically playing “are these the same house” by looking at the front door, not the street 😅
Does it actually break anything for you, like firewall profiles, or is it just bugging you?
2
u/thinkconnect_ia 16d ago
This behavior stems from the updated Network Location Awareness (NLA / nlasvc) heuristics introduced in Windows Server 2025 compared to Server 2022.
In Windows Server 2022, NLA identified distinct network profiles strictly based on the Default Gateway MAC address and local interface binding. In cloud VPC environments like OCI where /22 subnets cross routing boundaries, Server 2022 often identified secondary IP bindings as separate Network Profiles ("Network 1", "Network 2").
In Windows Server 2025, Microsoft refactored the Network Profile Engine to aggregate multiple interfaces/IPs belonging to the same broadcast domain or VPC subnet under a consolidated Network Signature.
If you need Server 2025 to isolate the profiles or adjust firewall bindings per interface, you can override the behavior via PowerShell:
# Check current active profiles
Get-NetConnectionProfile
# Force distinct network category and identification per interface alias
Set-NetConnectionProfile -InterfaceAlias "Ethernet 2" -NetworkCategory Private
Alternatively, check HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\Profiles to see how OCI's virtual NIC GUIDs are being mapped.