Windows 10: Windows 10 no IPv6 address on boot

Hello everyone. I have found on my home and office ipv6 SLAAC enabled networks, Windows 10 computers frequently fails to self-configure IPv6 addresses when boot up. Toggling wifi off/on via the lower right wifi icon does not solve the problem. However, if I go into Control Panel/Network and sharing center, manually disable and re-enable the wifi adaptor, the machines gets IPv6 address properly.


This is happening at least on my 2018 HP Spectre x360 13, Surface Pro 7, Surface Go, and Surface Go 2, all with Intel wireless adapters.


Is this a known issue? Is there any fix?

:)

 

Windows 10 can not get IPv6 address automatically?

I used to have similar problem on a Windows 10 reside inside a VM, and each time the dhcp lease expired it didn't repair to a new one, and I have to perform renew6 manually.

After checking again the date/time of the VM, it turned out differs with the DHCP server's, so after fixing the time the DHCPv6 client behaviour back to normal. Here's my suggestion:

• please make sure the node which will receive IPv6 global address via DHCPv6 has the same timezone / time with the DHCP server
• another solution is using different method, namely Stateless Address Auto Configuration (SLAAC) with RDNSS (to obtain DNS information), but you have to install 3rd party software rdnssd_win32, since Microsoft didn't plan to implement it

Best Regards.

 

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!

 

Windows losing IPv6 address after ~10 minutes

When I initially connect to my home network my windows PC is assigned an IPv6 address - however after a few minutes it loses this address! I seem to have similar behaviour on multiple hosts using both wireless and wired connections.

My router is an Asus RT-AC87U.

How could it be losing the IPv6 address? How can I mintor / diagnose this issue?

Update:
Based on @grawity's suggestion below I ran wireshark on this. Sure enough I see a Router Solicitation message and a Router Advertisment message with a Router lifetime of 600 seconds. After 600 seconds my computer drops its Ipv6 address.

What is supposed to happen? Should my host send another Router Solicitation message? Or should the router periodically resend the Router Advertisment message?

Update 2:

• RFC 4862 says that Router Adverticement messages should be sent periodically.