Re: DHCPv6 client in Windows 10 broken after anniversary update

Harald F. Karlsen wrote: > If looks like this was finally resolved in the 2017 March cumulative > update for Windows. I have verified it on Windows 10 Home and Pro, but I > also got one report claiming it was not resolved in Windows 10 > Enterprise, can someone confirm this? if this is the case,

Re: DHCPv6 client in Windows 10 broken after anniversary update

On 10.10.2016 10:14, Harald F. Karlsen 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

Re: DHCPv6 client in Windows 10 broken after anniversary update

I just saw the following post on the Microsoft Technet forum: https://social.technet.microsoft.com/Forums/windows/en-US/b16e7d78-e390-4ada-a24b-3ccba60fa571/no-ipv6-dns-statelessdhcp-since-windows-10-anniversary-update?forum=win10itpronetworking=required On november 23rd Microsoft wrote: > I

Re: DHCPv6 client in Windows 10 broken after anniversary update

Has this been confirmed? What is next? On Fri, Oct 14, 2016 at 5:59 AM, Harald F. Karlsen wrote: > On 11.10.2016 18:37, Marcus Keane wrote: > >> We've raised it with the product group and we are investigating further. >> > Great! Also feel free to keep us updated on any findings

Re: DHCPv6 client in Windows 10 broken after anniversary update

On 11.10.2016 18:37, Marcus Keane wrote: We've raised it with the product group and we are investigating further. Great! Also feel free to keep us updated on any findings here on the list (especially the ship vehicle and date for the fix). -- Harald

RE: DHCPv6 client in Windows 10 broken after anniversary update

Hi Harald, We've raised it with the product group and we are investigating further. Regards, Marcus -Original Message- From: ipv6-ops-bounces+mkeane=microsoft@lists.cluenet.de [mailto:ipv6-ops-bounces+mkeane=microsoft@lists.cluenet.de] On Behalf Of Harald F. Karlsen Sent: 10

Re: DHCPv6 client in Windows 10 broken after anniversary update

On 10.10.2016 15:29, Mikael Abrahamsson wrote: So I did some more investigation. I had missed that I needed to use /renew6 and /release6 before. Now I have 10 minute lease time. 5 minutes into the lease time, I can /renew6 the lease successfully and get 10 more minutes leasetime. around

Re: DHCPv6 client in Windows 10 broken after anniversary update

So I did some more investigation. I had missed that I needed to use /renew6 and /release6 before. Now I have 10 minute lease time. 5 minutes into the lease time, I can /renew6 the lease successfully and get 10 more minutes leasetime. around 2-3 minutes before the lease-time expires I see

Re: DHCPv6 client in Windows 10 broken after anniversary update

Hi, same here on a Windows 10 Pro 1607 with stateful DHCPv6. Only takes addresses when being forced by /renew6 but seems to forget them soon too. I first suspected a problem with the DHCPv6 server dhcpy6d but when I read you mails this seems to be a more global problem. Regards -- Henri Wahl

Re: DHCPv6 client in Windows 10 broken after anniversary update

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 wrote: > I've think I've also seen this. To work around a bug

Re: DHCPv6 client in Windows 10 broken after anniversary update

On 10.10.2016 10:47, Thomas Schäfer wrote: A Question: Have you a pure Windows? I have seen, there is third party network management software on my device. (Fujitsu Plugfree Network). I experience the issue on three different devices I tested on (one of which is a completely original

Re: DHCPv6 client in Windows 10 broken after anniversary update

Am 10.10.2016 um 10:14 schrieb Harald F. Karlsen: Hi, 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