I've been pulling out my hair for the last two weeks. My old router died so I got a DIR-601. It supports IPv6 so I figured that I would take advantage of it. I had been using a HE Tunnel on my main system. It worked great. I setup my router to use the tunnel and removed the tunnel on my main system. My other computers can get an IP6 address and use it with no problem. It shows up right next to the IP4 address when I do an ipconfig. However on my main system nothing. I just get a link-local address on every. I'm done everything I can think of to get it working. I've reinstalled the adpaters, Reset winsock via netsh, etc. Nothing seems to get it working! I've searched though technet and other forms and tried everything I found on there too. Any advice would be helpful. I'm about to just reinstall the OS.

Hi, thank you for post here. Can you tell me what system did you use? Windows 7? And what the version of system? There is a Group Policy setting that deals with the IPv6 Protocal and how it reacts to firewalls RUN>gpedit.msc Under Computer Configuration go to Adminnistrative Templates>Network>TCPIP Settings>Parameters and you'll see the Window Scalling Heuristic State setting off to the right. Enable it. Try to uninstall the NIC in the Device Manager. Reboot and Windows 7 will reinstall the drivers. And there is a possible that the issue occurs with the configuration of HE Tunnel, you can go to HE tunnel for further help: http://www.tunnelbroker.net/forums/index.php?www Please Note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information. Hope it helps. Regards, Leo HuangPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

I'm using Windows 7. There are no group policies setup on the system. I have already tried to uninstall & reinstall the adapter. I even used another adapter on the system and didn't have any luck. The tunnel works fine as the other systems get an IPv6 address and can use the tunnel. It's only the system that I had the tunnel setup manually on that can not get an IPv6 address. I could specify an address if I wanted to but that kind of defeats the purpose of using autoconfig.

I think I may have stumbled over the same issue. On my system, the Event Log for the DHCP v6 client shows lots of instances of event 1006 (Managed Configuration/Stateful Configuration bits in router advertisements changing value, now both set to true ). I suspect something might be wrong either with the Router Advertisement parser or with initialisation of the IPv6 configuration state machine here, as the RAs that are on the wire certainly have those bits set to zero, and some of the interfaces mentioned in the log messages do not even have IPv6 routers connected to them. The issue seems to persist if it occured once, even if the interface is disconnected and reconnected; a reboot usually solves it if the router(s) are present on the network before Windows 7 starts autoconfiguration. Disconnecting and reconnecting the cable after configuration succeeded once can bring the system back into failure mode. The related thread "Windows 7 RC cannot auto configure IPV6 address " appears to conclude that this is a NIC issue; I'm not sure it is that simple, as I've tried with two different (wired) NICs now (Broadcom and Intel).