<div dir="ltr">Hi everyone,<div><br></div><div>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.</div><div class="gmail_extra"><br clear="all"><div><div class="m_-1990999257231785956gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div><font face="arial, helvetica, sans-serif" size="2">Best,</font></div><div><font size="2" face="arial, helvetica, sans-serif">-Michael<br></font></div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><br></div></div></div>
</div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div>
<br><div class="gmail_quote">On Mon, Oct 10, 2016 at 11:28 AM, Trevor Warwick <span dir="ltr"><<a href="mailto:twarwick@gmail.com" target="_blank">twarwick@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">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.</div><div class="m_-1990999257231785956HOEnZb"><div class="m_-1990999257231785956h5"><div class="gmail_extra"><br><div class="gmail_quote">On 10 October 2016 at 09:14, Harald F. Karlsen <span dir="ltr"><<a href="mailto:harald@bgp.no" target="_blank">harald@bgp.no</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
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).<br>
<br>
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.<br>
<br>
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.<span class="m_-1990999257231785956m_4870867264775913897HOEnZb"><font color="#888888"><br>
<br>
-- <br>
Harald<br>
</font></span></blockquote></div><br></div>
</div></div></blockquote></div><br></div></div>