So, I solve my issue. The Windows Firewall Public profile was set to "Block all connections" This effectively breaks DHCPv6 and even causes the dreaded "Public (Unauthenticated)" issue. Once I changed the public profile to just "Block" everything started working. The Predefined Core Network firewall rules are 100% needed for Windows 7 to function with IPv6.

So, I have my network router configure to give out stateless IPv6 address and have the O flag set so that client can get an IPv6 DNS server via DHCPv6. What I notice that that some Windows 7 clients (from the same image in the same OU) get the DNS from the DHCPv6 server while other don't when I do an ipconfig /all. All the system can still resolve AAAA records and seem to be using IPv6 addresses as a default, but I find this odd. As anyone else come across the issue or know how to resolve it?

Im glad to hear your issue has been resolved. Hope your experience will help other community members facing similar problems. Regards, Leo Huang TechNet Subscriber Support If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.Leo Huang TechNet Community Support

1. What gives ipconfig /release6 and ipconfig /renew6? In addition to this, delete DNS cache. 2. I would reserve IPnv6 addresses in DHCP (based on MAC) Regards Milos