Hi everyone, Does anyone know if Microsoft is aware of this issue? Perhaps it can be forwarded to someone who can pass it along to the engineers.
Best, -Michael On Mon, Oct 10, 2016 at 11:28 AM, Trevor Warwick <[email protected]> wrote: > I've think I've also seen this. To work around a bug in my Ubiquiti router > at home, I can't use SLAAC, so need to rely on DHCPv6 for address > assignment. This weekend, a recently upgraded Windows 10 Anniversary > machine wasn't successfully getting an IPv6 address. Looking at it with > wireshark,IIRC, the client sent a Solicit, the server sent an Advertise, > but there was no Request from the client after that. > > On 10 October 2016 at 09:14, Harald F. Karlsen <[email protected]> wrote: > >> Hi, >> >> It seems like Microsoft somehow broke DHCPv6 client functionality in the >> Windows 10 anniversary update and now neither stateful nor stateless DHCPv6 >> functionality works unless you manually issue "ipconfig /renew6" (for >> stateful DHCPv6 this will only give you IPv6-connectivity untill the lease >> expires). >> >> This is generally not a big issue for dual-stacked residential customers >> as most CPEs does SLAAC on the LAN-side, but the Win10 clients will not >> recieve DNS from DHCP if the CPE is configured for that. For enterprise >> networks on the other hand this can be a big issue. Especially when running >> FHS and no SLAAC. >> >> Have anyone on the list experienced issues with this yet? If so, have you >> contacted Microsoft and what did they say? I've found reports on this issue >> dating back from early august so it's strange that Microsoft have not yet >> issued a fix for it. >> >> -- >> Harald >> > >
