Hi, I just installed the new windows 7 RC and I have a problem with IPv6. My ISP provides IPv6 support (the DSL modem does IPv6 router advertisement) but Windows 7 does not seem to be able to autoconfigure the IPv6 address. It just creates the local link address. I disabled the Randomize Identifiers feature to no avail. I tried connecting to my network through ethernet or wifi and it did not change anything (so it's not a network card driver problem or they both have it). Windows Vista was working before (I uninstalled it so I cannot compare the network exchanges) and my Linux and MacOsX boxes still have IPv6 connectivity so it's not on the dsl router side. I can see the Windows 7 box sending ICMPv6 router sollicitation packets but there is no answer. Any idea? The ethernet adapter is a Marvell Yukon 88E8056 and the ISP is Free in France (they provide IPv6 connectivity). Regards Jean-Franois

I'm using RA to autoconfigure my IPv6 access and it works as expected, but I have seen some issues with the ipconfig /renew6 command so it seems something has changed relating to IPv6. Have you installed any additional firewall that might block icmp messages?

Yes, you were right. I had symantec endpoint protection installed. I had installed its firewall but after the install it did not show up in symantec control panel so I thought it was not installed. It turns out I was wrong. It was installed with its default configuration but there was no way to see it was active and the default config blocks IPv6. Once I removed it everything worked. Jean-Franois

I'm having a similar problem, but I don't have SEP installed. I am using regular old AVG (free), plus windows firewall. Here are my symptoms: I have a Cisco 2511 doing RA. My XP boxes pick up the RAs no problem. The Win7 RC box that I've just built does not show an IPv6 address in ipconfig at all, and ipconfig /renew6 results in an error after a couple of minutes. I tried disabling windows firewall and retrying, no change. I re-enabled windows firewall, and hard-coded an IPv6 address via the network config (it's in a /64) and as soon as I clicked ok, and re-issued "ipconfig" it showed not only my hard-coded IPv6 address, but an autoconfig address as well. So, I removed the hard-coded address, set everything back to auto, and things kept working. To prove my hunch that something is preventing RAs from working right, I did a /release6 and /renew6, and saw the exact same behavior return, where it timed out with an error. Wes

I know that there have been issues with older Cisco versions not responding to router solicitation messages but in your case it seemsWin7 doesn't even see the advertisements. I have a setup with a linux openwrt and that is working fine as long as the openwrt box is working. It seems the openwrt some times doesn't respond to solicitation on its link local which makes the address on windows go stale, but I still have an address showing up in ipconfig. I'm also having problems with ipconfig /renew6 I'm getting all kinds of errors, but less the fewer tunnel protocols I have enabled. With no RA available on the network and a static address configured on LAN I get this: ipconfig /renew6Windows IP ConfigurationAn error occurred while renewing interface LAN : The semaphore timeout period has expired.No operation can be performed on Local Area Connection while it has its media disconnected.An error occurred while renewing interface Loopback Pseudo-Interface 1 : The system cannot find the file specified.An error occurred while renewing interface Local Area Connection* 11 : The system cannot find the file specified.Mikael

There is a Group Policy setting that deals with the IPv6 Protocal and how it reacts to firewallsRUN>gpedit.mscUnder 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.

That didn't have any effect. However, I'm sort of not surprised, because disabling Windows Firewall had no effect either. Any other ideas?

Uninstall the NIC in the Device Manager. Reboot and Windows 7 will reinstall the drivers.

If that doesn't work:Unistall the reinstall IPv6 via the Command Prompt.

well, uninstalling and reinstalling the NIC didn't help, and you can't actually uninstall IPv6, period in Vista/7 (netsh int ipv6 uninistall is only an option on XP), but unchecking the IPv6 box, rebooting, rechecking the IPv6 box, and rebooting again seems to have fixed it for about 2 minutes, but now I'm back to the same problem again. I think we have a bug.

I don't have Windows 7 up and running at the moment.Have you tried using Start>Accessories>Command Prompt(Run as Adminstrator) then typing:ipv6 uninstall? Reboot. Come back and install it the same with the Command Prompt:ipv6 install?

the ipv6 keyword is not recognized. I did a search and there are no files even called ipv6.*

update on this... I remembered that I had a PC with an install of Win 7 beta on it, so I booted that last night, and verified that autoconfig works just fine on that PC (wired connection). On a hunch, I tried the wired connection on this laptop I'm currently troubleshooting, and it works. So, it appears to be something specifically with the wireless NIC. I have a feeling that there's a problem with the driver, because some portion of the time when I wake it back up from hibernation, I can't get the wireless NIC to recognize my network. It's an Intel WLAN 2100 3B and the driver version is 1.2.5.37 (from 2006). This appears to be the latest version of the driver available on Intel's site.