How to report IPv6 bug to Microsoft - Vista and 7 won't "undeprecate" a prefix

[Carl Holzhauer]

It almost sounds like I'm in the minority.

I'm doing RA from a Cisco ASA running 8.3 to roughly fifty Windows 7 and Windows Vista machines and I've never had a problem.

I've turned off privacy extensions, Teredo, 6to4 and ISATAP.

We are running Vista SP2 and Windows 7 SP1, but never had a problem before applying the service packs.


-----Original Message-----
From: ipv6-ops-bounces+cholzhauer=sscorp.com at lists.cluenet.de [mailto:ipv6-ops-bounces+cholzhauer=sscorp.com at lists.cluenet.de] On Behalf Of Bernhard Schmidt
Sent: Thursday, April 07, 2011 11:00 AM
To: ipv6-ops at lists.cluenet.de
Subject: Re: How to report IPv6 bug to Microsoft - Vista and 7 won't "undeprecate" a prefix

On Thu, Apr 07, 2011 at 03:34:36PM +0930, Mark Smith wrote:

Hello,

> A number of our customers are having trouble with IPv6 under Windows 
> Vista and 7 on our IPv6 trial.

I cannot help you with your problem, but I also have some issues with Windows 7 and IPv6. Maybe someone has an idea how to fix this:

We have an internal network with about 200 clients. Mostly Dell Desktops from the past three years with different operating systems (various Linux distributions, Windows XP, Windows 7). A few MacOS boxes as well.
The router is a Cisco 6500 with SXI5, the switching infrastructure are non-IPv6-aware HP Procurve.  We run non-standard timers here (RA interval 10s, RA lifetime 30s, Prefix valid for 86400s, preferred for 1800s).

Every once in a while a Windows 7 box gets broken IPv6. Symptoms are a deprecated address and no default route. It pretty much acts like it does not receive the RAs anymore. But the RAs are there (verified with Wireshark on the affected client and from other clients which work just fine). Most of the times the issue can be fixed by disabling/reenabling the network interface on the client.

Mostly we have seen this issue with clients that have been suspended a few times, but today I had a client that had just rebooted. Basically the expiry timers started running when the box was booted up and never got refreshed.

Anyone got similar experiences?

Bernhard