SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #984277
Ticket Status: User

PoP: simbx01 - Amis (Maribor)

windows connectivity problems
[hu] Shadow Hawkins on Tuesday, 24 February 2009 23:42:38
I have read and followed the "Reporting Problems" section on the Contact page and am providing the following details for this report based on the list of items stated there: Not sure if it's a SIXXS problem but I am experiencing connectivity problems lately. Whenever I try to ping any IPv6 address, the first ping goes through, and subsequent requests fail on all Windows boxes. Seems that Windows removes the default route after the first ping response arrives, so subsequent packets fail. Restarting RADVD on the router brings back the missing route but any communication causes an error. Pinging ipv6.l.google.com [2001:4860:0:1001::68] from 2001:15c0:6654::1 with 32 bytes of data: Reply from 2001:4860:0:1001::68: time=92ms PING: transmit failed, error code 1214. PING: transmit failed, error code 1214. PING: transmit failed, error code 1214. The same request from Linux boxes seem to go through any time: root@OpenWrt:~# ping6 ipv6.google.com PING ipv6.l.google.com (2001:4860:0:1001::68): 56 data bytes 64 bytes from 2001:4860:0:1001::68: icmp6_seq=0 ttl=56 time=95.1 ms 64 bytes from 2001:4860:0:1001::68: icmp6_seq=1 ttl=56 time=89.9 ms 64 bytes from 2001:4860:0:1001::68: icmp6_seq=2 ttl=56 time=87.0 ms No config changes have been made to my infrastructure. Are you aware of any Windows updates that might have impacted IPv6 connectivity? I am using AICCU on a ASUS WL500gP router configured for AYIYA
State change: user Locked
[ch] Jeroen Massar SixXS Staff on Wednesday, 25 February 2009 08:43:44
Message is Locked
The state of this ticket has been changed to user
windows connectivity problems
[ch] Jeroen Massar SixXS Staff on Wednesday, 25 February 2009 08:48:52
Sounds like a local error to me. What version of Windows? ERROR_INVALID_NETNAME (1214 / 0x4BE) The format of the specified network name is invalid. Also check the Hotfixes list. You might want to try a 'netsh int ipv6 reset' which might clean up some issues.

Please note Posting is only allowed when you are logged in.

Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker