I've run into something that might be a bug in the SLAAC process. Intial configuration of an address works fine but when the computer resumes from sleep efter the address prefered lifetimte has expiered and the address has been marked depricated it will not leave the depricated state. The life time timers are updated correctly but the address remains depricated and IPv6 access doesn't work, unless forced. Netsh shows address status as follows: Interface 11: LAN Addr Type DAD State Valid Life Pref. Life Address --------- ----------- ---------- ---------- ------------------------ Temporary Deprecated 23h58m25s 3h58m25s 2001:5c0:1101:ff00:1949:dfdd:b2cd:a00c Public Deprecated 23h58m25s 3h58m25s 2001:5c0:1101:ff00:80dd:8c55:a55c:eab0 Other Preferred infinite infinite fe80::80dd:8c55:a55c:eab0%11 The only way to resolve the problem is to disable IPv6 on the interface and then enable it again. Using ipconfig /renew6 will only result in a strange error "An error occurred while renewing interface LAN : The system cannot find the file specified.", this actually true at any time and probably an unrelated error. Unplugging will do nothing either as the interface isn't reset completly it seems. Har anyone any idea how to resolv this problem? Is it incompatibility with the RAs? Can it be a bug? Never saw this problem on Vista.

I think the problem could be because of non-availability of RA's, because of which address is deprecated. See if execution of following netsh commands solves the problem : netsh int ipv6 set int <interface_name> adv=en man=dis other=dis netsh int ipv6 set int <interface_name> adv=dis

What do you mean with non-availability of RAs? I can see tha RAs sniffing on the interface and the timers update but no the status. I've run the the commands and it didn't remove the error in ipconfig /renew6 but I still need to test more what happens if let the address get deprecated and reconnect.

I've run into something that might be a bug in the SLAAC process. Intial configuration of an address works fine but when the computer resumes from sleep efter the address prefered lifetimte has expiered and the address has been marked depricated it will not leave the depricated state. The life time timers are updated correctly but the address remains depricated and IPv6 access doesn't work, unless forced. <snip> The only way to resolve the problem is to disable IPv6 on the interface and then enable it again. Using ipconfig /renew6 will only result in a strange error "An error occurred while renewing interface LAN : The system cannot find the file specified.", this actually true at any time and probably an unrelated error. Unplugging will do nothing either as the interface isn't reset completly it seems. Har anyone any idea how to resolv this problem? Is it incompatibility with the RAs? Can it be a bug? Never saw this problem on Vista. I second this problem. At work I use Vista, no problems. At home the Vista notebook works fine, the Windows 7 one doesn't. My "netsh interface ipv6 show addresses" output: Interface 13: Wireless Network Connection Addr Type DAD State Valid Life Pref. Life Address --------- ----------- ---------- ---------- ------------------------ Temporary Deprecated 23h58m43s 3h58m43s 2001:470:1f15:xxx:195e:fee9:8f19:88be Public Deprecated 23h58m43s 3h58m43s 2001:470:1f15:xxx:7595:1645:6679:bb9a Other Preferred infinite infinite fe80::7595:1645:6679:bb9a%13 After receiveing an RA, the "Valid Life" and "Pref. Life" times get updated. Wireshark on this machine captured the following RA: No. Time Source Destination Protocol Info 4123 1327.080956 fe80::f067:8bff:xxxx:xxxx ff02::1 ICMPv6 Router advertisement Frame 4123 (134 bytes on wire, 134 bytes captured) Ethernet II, Src: Cisco-Li_xx:xx:xx (00:12:17:xx:xx:xx), Dst: IPv6mcast_00:00:00:01 (33:33:00:00:00:01) Internet Protocol Version 6 Internet Control Message Protocol v6 Type: 134 (Router advertisement) Code: 0 Checksum: 0x456e [correct] Cur hop limit: 64 Flags: 0x00 0... .... = Not managed .0.. .... = Not other ..0. .... = Not Home Agent ...0 0... = Router preference: Medium Router lifetime: 1800 Reachable time: 0 Retrans timer: 0 ICMPv6 Option (Prefix information) Type: Prefix information (3) Length: 32 Prefix length: 64 Flags: 0xc0 1... .... = Onlink .1.. .... = Auto ..0. .... = Not router address ...0 .... = Not site prefix Valid lifetime: 86400 Preferred lifetime: 14400 Prefix: 2001:470:1f15:xxxx:: ICMPv6 Option (Recursive DNS Server) Type: Recursive DNS Server (25) Length: 24 Reserved Lifetime: 600 Recursive DNS Servers: fe80::f067:8bff:xxxx:xxxx (fe80::f067:8bff:xxxx:xxxx) ICMPv6 Option (Source link-layer address) Type: Source link-layer address (1) Length: 8 Link-layer address: 00:12:17:xx:xx:xx Any suggestions would be very much apreciated.

I have the exact same problem on Vista. I've configured RAs aggressively at 4 seconds. The "Valid Life" field updates with each RA, but the address still shows deprecated.

Same problem here. Win 7 x64. RAs are received, lifetime is updated, but still deprecated. Problem occours on 3 different computers It would make me very happy if someone could help me to solve this

Here's a thread on another forum: http://www.neowin.net/forum/topic/917904-ipv6-address-becomes-deprecated/page__pid__592983644__st__0&#entry592983644 Also a similar issue mentioned on the ipv6-ops list: http://lists.cluenet.de/pipermail/ipv6-ops/2009-December/002718.html I'm starting to think this is a bug with the Windows IPv6 implementation.

Same problem here on windows 7, SLAAC configured address shows DAD state of deprecated after resuming from suspend, despite valid RAs being received.

I've been able to confirm that this only happens when the address expires while the system is suspended. IOW, I can leave the system running and it processes RAs normally and the address is never deprecated. I can also suspend and resume before the preferred life expires and the system will continue to process RAs normally and update the valid lifetime.

+1 I have this exact problem. My wireless USB port shows "deprecated" for both IPV6 addresses after a suspend. Only a reboot or a removal and reinsertion of the wireless USB causes IPV6 to come back. How do you un-deprecate an address? Or get a new one?

Disable and enable your network adapter may change the state correctly. -- This posting is provided "AS IS" with no warranties, and confers no rights.

I have this exact problem as well. Once resumed from a suspend, my wireless adapter never leaves the Deprecated state netsh interface ipv6>show int 26 Interface Wireless USB Parameters ---------------------------------------------- IfLuid : wireless_5 IfIndex : 26 State : connected Metric : 25 Link MTU : 1500 bytes Reachable Time : 26500 ms Base Reachable Time : 30000 ms Retransmission Interval : 1000 ms DAD Transmits : 1 Site Prefix Length : 64 Site Id : 1 Forwarding : disabled Advertising : disabled Neighbor Discovery : enabled Neighbor Unreachability Detection : enabled Router Discovery : enabled Managed Address Configuration : disabled Other Stateful Configuration : disabled Weak Host Sends : enabled Weak Host Receives : disabled Use Automatic Metric : enabled Ignore Default Routes : disabled Advertised Router Lifetime : 1800 seconds Advertise Default Route : disabled Current Hop Limit : 64 Force ARPND Wake up patterns : disabled Directed MAC Wake up patterns : disabled netsh interface ipv6>show addre 26 Address 2001:470:1f05:347:a488:e027:e545:xxxx Parameters --------------------------------------------------------- Interface Luid : Wireless USB Scope Id : 0.0 Valid Lifetime : 4m2s Preferred Lifetime : 0s DAD State : Deprecated Address Type : Public Address fe80::a488:e027:e545:xxxx%26 Parameters --------------------------------------------------------- Interface Luid : Wireless USB Scope Id : 0.26 Valid Lifetime : infinite Preferred Lifetime : infinite DAD State : Preferred Address Type : Other Works if I disable and re-enable ipv6, but that is not acceptable. if the address expires during the suspend, it never comes back.

Same here. When is MS doing something about this? Or how the ____ can someone file a real bug report?

I am currently experiencing the same behavior. Does someone have an idea when this will be fixed? It is currently blocking some roll-outs.

I don't know if this would work for everyone, but hopefully it'll work as a bandaid for some (as long as you're physically at your computer). As I have the same issue I created a bat file that contains the following two netsh lines: rem ----syntax borrowed from: http://forum.sysinternals.com/command-used-to-disable-network-interface_topic9483.html netsh interface set interface "Local Area Connection" admin=DISABLED netsh interface set interface "Local Area Connection" admin=ENABLED rem --- now that the NIC has been reset, it should grab new ip addresses (ipv4 and ipv6). note: if it's a wireless interface you will need to replace "Local Area Connection" with "Wireless Network Connection" (make sure to include the quotes), assuming they're both built in. If you have multipule of either one (or it's not built in) check what's after the ":" when you do a "netsh ipv6 show addresses" (no quotes). note2: If you run this an get the message: "An interface with this name is not registered with the router." check that you're running the script/commands with full administrator privileges. I've tested it out on my windows 7 laptop twice now, and it does the trick for me (no reboots required, or disconnecting the network cable).

Another thread about this just popped up on the ipv6-ops list: http://lists.cluenet.de/pipermail/ipv6-ops/2011-April/005188.html I think it's obvious now that this is a bug.