2
I have noticed that a Windows 10 client sometimes does not get an IPv6 address on my network. Looking in to this I have discovered it is limited to resume after suspend. Running wireshark on the client I can see the router solicitation go out but no router advertisement is received, either periodically or in response to the solicitation. While disconnecting from the wireless network and reconnecting does not solve the problem, disabling and re-enabling the wireless NIC does solve the problem and RAs are once again received. While this is a workaround solves the problem it is not a good long term solution.
I have been trying to research this problem, but Windows 10 IPv6 resources seem to be virtually non existent or at best only scratch the surface and I do not know how to further troubleshoot the problem. I should add that my NIC driver is up to date.
How can I find the root cause of this problem to eliminate the issue once and for all?
fileinster
Posted 2016-07-03T09:39:55.820
Reputation: 131
Wild guess: Sounds like a driver error, where after resume the driver doesn't register all MAC address it wants to receive packets for. – Sander Steffann – 2016-07-03T12:03:16.537
That's my gut feeling as well. Any tips on how I should report this to the manufacturer (dell)? – fileinster – 2016-07-03T18:08:37.660
I think creating a support case would be the first step, assuming the PC is still covered under a support contract. In any case please post exact details about the system that you are seeing this on. It might help others with the same problem, and it might even trigger some Dell people into looking into this :) – Sander Steffann – 2016-07-03T22:05:56.730