Windows 10: Actual windows11 version seems to have a bug IPV6 DHCPV6 / RA failing

My network has a router connected to the internet. Starting at the router there are multiple VLAN's for different purposes. My PC is connected to two of those vlans's one at a time.The PC has multiple network interfaces, which I can enable/disable. Each of those interfaces is connected to another VLAN. Only one of those interfaces is active at a certain moment in time.The interfaces obtain there IPV4 & IPV6 addresses form the DHCP-IPV4-server / DHCP-IPV6 - RA server in the router. At least that should happen ... And that did work ..... up to the moment I migrated to Windows11 64 bit PR

:)

 

Windows 10 Anniversary Update breaks DHCPv6 client

I have an IPv6 enabled LAN. I use Stateless Address Autoconfiguration (M flag on the router set to 0) and Stateful Other configuration (O flag set to 1) so the IPv6 clients generate thier own IPv6 addresses and use DHCPv6 to obtain the DNS server IPv6 addresses.
I have a couple of Windows 2008 R2 DHCP servers with just Global Server Options configured under IPv6. These options are '23 DNS Recursive Name Server IPv6 Address List' and '24 Domain Search List'. These servers are on different networks so I have DHCPv6
forwarding configured on my layer-3 switches to the IPv6 addresses of the two DHCPv6 servers.

This has worked effortlessly with Windows Vista, Windows 7 and Windows 2008/R2 as well as Windows 10 version 1511. The clients see the router advertisements with the M flag set to 0 and the O flag set to 1 and generate their own IPv6 addresses and then
send a DHCPv6 Information Request requesting options 23, 24, 17 & 32. The DHCPv6 server responds with options 23 & 24 and the client gets the IPv6 DNS servers.

I have built a couple of machines with the new Windows 10 Anniversay Update and the DHCPv6 behaviour has changed. The client generates its own stateless IPv6 addresses but no longer sends a DHCPv6 Information Request and instead sends a Solicit like it
would if the M flag was set to 1. Obviously the DHCPv6 server does not respond since it doesn't have a scope configured for the clients prefix.

This is what it shows on the client:

netsh interface ipv6>show dnsservers

Configuration for interface "Ethernet"

DNS servers configured through DHCP: None

Register with which suffix: Primary only

Configuration for interface "WiFi"

DNS servers configured through DHCP: None

Register with which suffix: Primary only

netsh interface ipv6>show interface wifi

Interface WiFi Parameters

----------------------------------------------

IfLuid : wireless_32768

IfIndex : 3

State : connected

Metric : 40

Link MTU : 1500 bytes

Reachable Time : 18500 ms

Base Reachable Time : 30000 ms

Retransmission Interval : 1000 ms

DAD Transmits : 1

Site Prefix Length : 64

Site Id : 1

Forwarding : disabled

Advertising : disabled

Neighbor Discovery : enabled

Neighbor Unreachability Detection : enabled

Router Discovery : enabled

Managed Address Configuration : disabled

Other Stateful Configuration : enabled

Weak Host Sends : disabled

Weak Host Receives : disabled

Use Automatic Metric : enabled

Ignore Default Routes : disabled

Advertised Router Lifetime : 1800 seconds

Advertise Default Route : disabled

Current Hop Limit : 64

Force ARPND Wake up patterns : disabled

Directed MAC Wake up patterns : disabled

ECN capability : application

netsh interface ipv6>

I tried adding a scope to the DHCPv6 server and it does reply and I can see in the WireShark trace that options 23 & 24 are given, however the client does not complete the DHCPv6 process and still shows no IPv6 DNS Servers received via DHCPv6. I can
see that it knows the M & O flags are now both set to 1:

Managed Address Configuration : enabled

Other Stateful Configuration : enabled

I have compared this behaviour to a Windows 7 SP1 host and whether I use Stateless DHCPv6 (M=0, O=1) or Stateful DHCPv6 (M=1, O=1) it works perfectly.

I am guessing that this is a bug in the IPv6 stack in Windows 10 Anniversary Update? I have seen some other people complaining about this issue so has Microsoft acknowledged it and commited to providing a fix?

Andy

 

Windows 10 can not get IPv6 address automatically?

Downgrade did not help, still the same issue is present. Just to let you guys know I´m running default windows security software (defender + windows firewall), no 3rd party firewalls or other installed. Also firewall and any other security program would
not cause the symptoms I have noticed, they would either block IPv6/dhcpv6 completely or allow everything. So the only thing left is the ipconfig or dhcpv6 client software that windows runs, but how can I (typical consumer) make a bug report to Microsoft to
get any fix?

 

Windows 10 can not get IPv6 address automatically?

Hi all,

hopefully someone can help me and figure out what is wrong. I have been trying to search online for help around similar issues but nothing seems to match exactly my problem and there is not many "near" solution to try.

I guess the problem started around august after some sort of update to windows 10.

I am a network professional and been using IPv6 with DHCPv6 for a couple of years without any problems. So keep this in mind before suggesting any "stupid" ideas about check your ISP or router, I know they are working since all my other devices work. Also
I verified via wireshark, that my current Windows 10 computer does not send any DHCPv6 packets until I manually run the command ipconfig /renew6 multiple times. And after I finally get the computer to send the DHCPv6 packets, I get a response from the router
and IPv6 connectivity is restored. The IPv6 works for a half lease time and after that it deprecates because somehow windows fails to renew it on half the lease time. I can again get it to work after manually using ipconfig /renew6 for multiple times until
it runs without any error messages. The errors I get from ipconfig is listed below:

• An error occurred while renewing interface Local Area Connection The parameter is incorrect
• An error occurred while renewing interface Local Area Connection The semaphore timeout period has expired.
• An error occurred while renewing interface Local Area Connection Function failed during execution.

Now I´m not an expert on software, but could it be that the automatic process of renewing IPv6 address also fails to the same errors and somehow it does not try again automatically so eventually I lose IPv6 connectivity completely until I run ipconfig /renew6
manually about 3 times until I get a clean exit and the address is renewed.

What is causing the errors? And are these the reason why windows fails to renew IPv6 address? At the same time IPv4 DHCPv4 is working flawless.

Any help would be greatly appreciated!