Problem in network Windows 11 24h2

I can confirm, that nothing worked so far on MSI Z390 Ace motherboard. I tried everything.

Hello,

I'm at home without being in a Windows Domain. I just have a DHCP and DNS server which run on a now unsupported Windows Server version.

The DHCP server serves parameter option 015 with value "home.local".

Since the upgrade of my laptop with 24H2, all internal DNS queries fail now.

I have the feeling that is it related to IPv6.

My DNS and DHCP server has the IPv4 address 192.168.68.5

After a IPCONFIG /RENEW here are the settings installed:

(some useless lines removed)

Wireless LAN adapter Wi-Fi:

Connection-specific DNS Suffix . : home.local
Description . . . . . . . . . . . : Intel(R) Wi-Fi 6 AX201 160MHz
Physical Address. . . . . . . . . : D4-54-xx-xx-xx-xx
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2a02:a03f:6b56:f000:1b88:4717:c3fe:8ec9(Preferred)
Temporary IPv6 Address. . . . . . : 2a02:a03f:6b56:f000:54b6:66d1:abe8:ffa2(Preferred)
Link-local IPv6 Address . . . . . : fe80::91d8:f6b5:89d9:b168%12(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.68.85(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Thursday, 5 December 2024 10:18:29
Lease Expires . . . . . . . . . . : Friday, 6 December 2024 10:28:29
Default Gateway . . . . . . . . . : fe80::3a35:fbff:fe31:81ee%12
192.168.68.1
DHCP Server . . . . . . . . . . . : 192.168.68.5
DHCPv6 IAID . . . . . . . . . . . : 164910219
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-29-50-9F-B5-7C-8A-E1-BE-3C-D8
DNS Servers . . . . . . . . . . . : fe80::3a35:fbff:fe31:81ee%12
192.168.68.5
192.168.68.1
fdaa:fbbc:bfdd:eef0:ff:f1d0::
NetBIOS over Tcpip. . . . . . . . : Enabled
Connection-specific DNS Suffix Search List :
home

When I type:

nslookup

Default Server: UnKnown
Address: fe80::3a35:fbff:fe31:81ee

it shows me that I am querying some local IPv6 DNS server, instead of the one supplied in option #6 of the DHCP setting.

My server is named "s" (with FQDN "s.home.local")

... continuing the nslookup queries ...

C:\Users\fred>nslookup
Default Server: UnKnown
Address: fe80::3a35:fbff:fe31:81ee

> s
Server: UnKnown
Address: fe80::3a35:fbff:fe31:81ee

*** UnKnown can't find s: Non-existent domain
> s.local
Server: UnKnown
Address: fe80::3a35:fbff:fe31:81ee

*** UnKnown can't find s.local: Non-existent domain
> s.home.local
Server: UnKnown
Address: fe80::3a35:fbff:fe31:81ee

*** UnKnown can't find s.home.local: Non-existent domain
> lserver 192.168.68.5
Default Server: [192.168.68.5]
Address: 192.168.68.5

> s
Server: [192.168.68.5]
Address: 192.168.68.5

Name: s.home.local
Address: 192.168.68.5

> s.local
Server: [192.168.68.5]
Address: 192.168.68.5

*** [192.168.68.5] can't find s.local: Non-existent domain
> s.home.local
Server: [192.168.68.5]
Address: 192.168.68.5

Name: s.home.local
Address: 192.168.68.5

How can I avoid this interference with IPv6, that overrides the answers of my DHCP server ?

This behaviour is new since the installation of 24H2.

Thanks,

Frédéric, from Belgium

Both systems are not using Wi-Fi; they are both directly hooked to the router. I have internet access but no networking.

We have a fleet of Windows 11 24H2 that can now get an IP address from our office DHCP server, only after removing DHCP Option 121. They were having trouble obtaining the IP address from their home routers, the solution for most of them was to ensure they enabled WPA/WPA2 Personal or better, on their WiFi routers.

WPA/WPA2-PSK (TKIP/AES): Some devices offer—and even recommend—this mixed-mode option. It enables both WPA and WPA2, using both TKIP and AES. While this ensures maximum compatibility with older devices, it also exposes your network to potential breaches through the less secure WPA and TKIP protocols.

Excuse my Spanish.

Otra cosa que descubrí con Win 11 24H2 es que ya no se conectará a las redes wifi WPA. Parece que Microsoft está aplicando la seguridad WIFI personal WPA / WPA2. verifique su enrutador y asegúrese de que WPA / WPA2 personal esté configurado como predeterminado. Buena suerte. Rob