SixXS::Sunset 2017-06-06

IPv6 stopped working on Win7x64
[rs] Shadow Hawkins on Tuesday, 01 March 2011 20:20:08
Well, the problems started when I installed CopSSH, but then I have uninstalled it, I had ipv6 for a few days, and then it stopped working :( Here are outputs of the commands, as said on the contacts page: C:\Users\Dancsi> netsh int ipv6 show address Interface 1: Loopback Pseudo-Interface 1 Addr Type DAD State Valid Life Pref. Life Address --------- ----------- ---------- ---------- ------------------------ Other Preferred infinite infinite ::1 Interface 27: IP6Tunnel Addr Type DAD State Valid Life Pref. Life Address --------- ----------- ---------- ---------- ------------------------ Other Deprecated infinite infinite fe80::e0ce:cb33:9932:edd3%27 Interface 11: Local Area Connection Addr Type DAD State Valid Life Pref. Life Address --------- ----------- ---------- ---------- ------------------------ Manual Preferred infinite infinite 2002:81a8:164:: Other Preferred infinite infinite fe80::a55c:dee8:e10f:606d%11 Interface 28: aiccu Addr Type DAD State Valid Life Pref. Life Address --------- ----------- ---------- ---------- ------------------------ Other Preferred infinite infinite fe80::28ad:f9df:48a4:746a%28 Interface 25: VMware Network Adapter VMnet1 Addr Type DAD State Valid Life Pref. Life Address --------- ----------- ---------- ---------- ------------------------ Other Preferred infinite infinite fe80::142d:7826:4263:abc4%25 Interface 26: VMware Network Adapter VMnet8 Addr Type DAD State Valid Life Pref. Life Address --------- ----------- ---------- ---------- ------------------------ Other Preferred infinite infinite fe80::19c7:19c1:a24c:d722%26 Interface 35: VirtualBox Host-Only Network Addr Type DAD State Valid Life Pref. Life Address --------- ----------- ---------- ---------- ------------------------ Manual Preferred infinite infinite 2001:15c0:65ff:558::2 Other Preferred infinite infinite fe80::4c74:102e:7072:6368%35 C:\Users\Dancsi> netsh int ipv6 show route Publish Type Met Prefix Idx Gateway/Interface Name ------- -------- --- ------------------------ --- ------------------------ Yes Manual 256 ::/0 35 2001:15c0:65ff:558::1 Yes Manual 256 ::/0 28 2001:15c0:65ff:558::1 No Manual 256 ::1/128 1 Loopback Pseudo-Interface 1 No Manual 256 2001:15c0:65ff:558::/64 35 VirtualBox Host-Only Network No Manual 256 2001:15c0:65ff:558::/64 28 aiccu No Manual 256 2001:15c0:65ff:558::2/128 35 VirtualBox Host-Only Network No Manual 256 2002:81a8:164::/64 11 Local Area Connection No Manual 256 2002:81a8:164::/128 11 Local Area Connection No Manual 256 fe80::/64 27 IP6Tunnel No Manual 256 fe80::/64 35 VirtualBox Host-Only Network No Manual 256 fe80::/64 11 Local Area Connection No Manual 256 fe80::/64 25 VMware Network Adapter VMnet1 No Manual 256 fe80::/64 26 VMware Network Adapter VMnet8 No Manual 256 fe80::/64 28 aiccu No Manual 256 fe80::142d:7826:4263:abc4/128 25 VMware Network Adapter VMnet1 No Manual 256 fe80::19c7:19c1:a24c:d722/128 26 VMware Network Adapter VMnet8 No Manual 256 fe80::28ad:f9df:48a4:746a/128 28 aiccu No Manual 256 fe80::4c74:102e:7072:6368/128 35 VirtualBox Host-Only Network No Manual 256 fe80::a55c:dee8:e10f:606d/128 11 Local Area Connection No Manual 256 fe80::e0ce:cb33:9932:edd3/128 27 IP6Tunnel No Manual 256 ff00::/8 1 Loopback Pseudo-Interface 1 No Manual 256 ff00::/8 27 IP6Tunnel No Manual 256 ff00::/8 35 VirtualBox Host-Only Network No Manual 256 ff00::/8 11 Local Area Connection No Manual 256 ff00::/8 25 VMware Network Adapter VMnet1 No Manual 256 ff00::/8 26 VMware Network Adapter VMnet8 No Manual 256 ff00::/8 28 aiccu C:\Users\Dancsi> ipconfig /all Windows IP Configuration Host Name . . . . . . . . . . . . : Dancsi-PC Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No Ethernet adapter aiccu: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : TAP-Win32 Adapter V9 Physical Address. . . . . . . . . : 00-FF-5B-32-46-14 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::28ad:f9df:48a4:746a%28(Preferred) Autoconfiguration IPv4 Address. . : 169.254.116.106(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.0.0 Default Gateway . . . . . . . . . : 2001:15c0:65ff:558::1 DHCPv6 IAID . . . . . . . . . . . : 570490715 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-13-9C-A7-C1-00-1F-D0-34-DF-6B DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1 fec0:0:0:ffff::2%1 fec0:0:0:ffff::3%1 NetBIOS over Tcpip. . . . . . . . : Enabled Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : NVIDIA nForce 10/100 Mbps Ethernet Physical Address. . . . . . . . . : 00-1F-D0-34-DF-6B DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IPv6 Address. . . . . . . . . . . : 2002:81a8:164::(Preferred) Link-local IPv6 Address . . . . . : fe80::a55c:dee8:e10f:606d%11(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.1.100(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Lease Obtained. . . . . . . . . . : 1. mart 2011 19:26:09 Lease Expires . . . . . . . . . . : 8. april 2147 2:36:28 Default Gateway . . . . . . . . . : 192.168.1.1 DHCP Server . . . . . . . . . . . : 192.168.1.1 DHCPv6 IAID . . . . . . . . . . . : 234889168 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-13-9C-A7-C1-00-1F-D0-34-DF-6B DNS Servers . . . . . . . . . . . : 89.216.1.40 89.216.1.1 NetBIOS over Tcpip. . . . . . . . : Enabled Ethernet adapter Local Area Connection 4: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Hamachi Network Interface Physical Address. . . . . . . . . : 00-23-C3-37-67-E8 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IPv4 Address. . . . . . . . . . . : 5.55.103.232(Preferred) Subnet Mask . . . . . . . . . . . : 255.0.0.0 Lease Obtained. . . . . . . . . . : 1. mart 2011 19:26:09 Lease Expires . . . . . . . . . . : 29. februar 2012 19:28:16 Default Gateway . . . . . . . . . : 5.0.0.1 DHCP Server . . . . . . . . . . . : 5.0.0.1 NetBIOS over Tcpip. . . . . . . . : Enabled Ethernet adapter VMware Network Adapter VMnet1: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet1 Physical Address. . . . . . . . . : 00-50-56-C0-00-01 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::142d:7826:4263:abc4%25(Preferred) Autoconfiguration IPv4 Address. . : 169.254.171.196(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.0.0 Default Gateway . . . . . . . . . : DHCPv6 IAID . . . . . . . . . . . : 822104150 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-13-9C-A7-C1-00-1F-D0-34-DF-6B DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1 fec0:0:0:ffff::2%1 fec0:0:0:ffff::3%1 NetBIOS over Tcpip. . . . . . . . : Enabled Ethernet adapter VMware Network Adapter VMnet8: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet8 Physical Address. . . . . . . . . : 00-50-56-C0-00-08 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::19c7:19c1:a24c:d722%26(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.52.1(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : DHCPv6 IAID . . . . . . . . . . . : 838881366 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-13-9C-A7-C1-00-1F-D0-34-DF-6B DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1 fec0:0:0:ffff::2%1 fec0:0:0:ffff::3%1 NetBIOS over Tcpip. . . . . . . . : Enabled Ethernet adapter VirtualBox Host-Only Network: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : VirtualBox Host-Only Ethernet Adapter Physical Address. . . . . . . . . : 08-00-27-00-C0-FA DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes IPv6 Address. . . . . . . . . . . : 2001:15c0:65ff:558::2(Preferred) Link-local IPv6 Address . . . . . : fe80::4c74:102e:7072:6368%35(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.56.1(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 2001:15c0:65ff:558::1 DHCPv6 IAID . . . . . . . . . . . : 755499047 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-13-9C-A7-C1-00-1F-D0-34-DF-6B DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1 fec0:0:0:ffff::2%1 fec0:0:0:ffff::3%1 NetBIOS over Tcpip. . . . . . . . : Enabled Tunnel adapter IP6Tunnel: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft Direct Point-to-point Adapater Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Tunnel adapter 6TO4 Adapter: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft 6to4 Adapter Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Tunnel Information for T53597: PoP Id : simbx01 IPv6 Local : 2001:15c0:65ff:558::2/64 IPv6 Remote : 2001:15c0:65ff:558::1/64 Tunnel Type : ayiya Adminstate : enabled Userstate : enabled Name : My First Tunnel ####### ####### AICCU Quick Connectivity Test ####### ####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (192.168.1.100) ### This should return so called 'echo replies' ### If it doesn't then check your firewall settings ### Your local endpoint should always be pingable ### It could also indicate problems with your IPv4 stack Pinging 192.168.1.100 with 32 bytes of data: Reply from 192.168.1.100: bytes=32 time<1ms TTL=128 Reply from 192.168.1.100: bytes=32 time<1ms TTL=128 Reply from 192.168.1.100: bytes=32 time<1ms TTL=128 Ping statistics for 192.168.1.100: Packets: Sent = 3, Received = 3, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms ###### ####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (212.18.63.73) ### These pings should reach the PoP and come back to you ### In case there are problems along the route between your ### host and the PoP this could not return replies ### Check your firewall settings if problems occur Pinging 212.18.63.73 with 32 bytes of data: Reply from 212.18.63.73: bytes=32 time=59ms TTL=57 Reply from 212.18.63.73: bytes=32 time=30ms TTL=57 Reply from 212.18.63.73: bytes=32 time=29ms TTL=57 Ping statistics for 212.18.63.73: Packets: Sent = 3, Received = 3, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 29ms, Maximum = 59ms, Average = 39ms ###### ####### [3/8] Traceroute to the PoP (212.18.63.73) over IPv4 ### This traceroute should reach the PoP ### In case this traceroute fails then you have no connectivity ### to the PoP and this is most probably the problem Tracing route to simbx01.sixxs.net [212.18.63.73] over a maximum of 30 hops: 1 8 ms 14 ms 18 ms 10.33.0.1 2 8 ms 9 ms 8 ms 10.33.0.1 3 20 ms 8 ms 10 ms ns-dj-m-1-ge1-24.sbb.rs [89.216.6.57] 4 10 ms 9 ms 9 ms ns-he-m-1-ge1-0-4.sbb.rs [89.216.6.205] 5 11 ms 13 ms 11 ms bg-yb-m-1-te8-2.sbb.rs [89.216.6.245] 6 16 ms 12 ms 13 ms bg-yb-r-1-te0-2-0-0.sbb.rs [89.216.5.67] 7 36 ms 22 ms 51 ms bpt-b4-link.telia.net [213.248.73.217] 8 31 ms 36 ms 60 ms win-bb2-link.telia.net [80.91.250.66] 9 29 ms 26 ms 32 ms win-b4-link.telia.net [80.91.253.128] 10 25 ms 26 ms 26 ms amis-ic-131652-win-b2.c.telia.net [213.248.90.174] 11 32 ms 37 ms 39 ms maribor3-te-1-3.amis.net [212.18.39.213] 12 29 ms 30 ms 30 ms simbx01.sixxs.net [212.18.63.73] Trace complete. ###### ###### [4/8] Checking if we can ping IPv6 localhost (::1) ### This confirms if your IPv6 is working ### If ::1 doesn't reply then something is wrong with your IPv6 stack Pinging ::1 with 32 bytes of data: Reply from ::1: time<1ms Reply from ::1: time<1ms Reply from ::1: time<1ms Ping statistics for ::1: Packets: Sent = 3, Received = 3, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms ###### ###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:15c0:65ff:558::2) ### This confirms that your tunnel is configured ### If it doesn't reply then check your interface and routing tables Pinging 2001:15c0:65ff:558::2 with 32 bytes of data: Reply from 2001:15c0:65ff:558::2: time<1ms Reply from 2001:15c0:65ff:558::2: time<1ms Reply from 2001:15c0:65ff:558::2: time<1ms Ping statistics for 2001:15c0:65ff:558::2: Packets: Sent = 3, Received = 3, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms ###### ###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:15c0:65ff:558::1) ### This confirms the reachability of the other side of the tunnel ### If it doesn't reply then check your interface and routing tables ### Don't forget to check your firewall (both IPv4 and IPv6) of course ### If the previous test was succesful then this could be both ### a firewalling and a routing/interface problem Pinging 2001:15c0:65ff:558::1 with 32 bytes of data: Reply from 2001:15c0:65ff:558::1: time=39ms Reply from 2001:15c0:65ff:558::1: time=35ms Reply from 2001:15c0:65ff:558::1: time=35ms Ping statistics for 2001:15c0:65ff:558::1: Packets: Sent = 3, Received = 3, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 35ms, Maximum = 39ms, Average = 36ms ###### ###### [7/8] Traceroute6 to the central SixXS machine (noc.sixxs.net) ### This confirms that you can reach the central machine of SixXS ### If that one is reachable you should be able to reach most IPv6 destinations ### Also check http://www.sixxs.net/ipv6calc/ which should show an IPv6 connection ### If your browser supports IPv6 and uses it of course. ###### ###### [8/8] Traceroute6 to (www.kame.net) ### This confirms that you can reach a Japanese IPv6 destination ### If that one is reachable you should be able to reach most IPv6 destinations ### You should also check http://www.kame.net which should display ### a animated kame (turtle), of course only when your browser supports and uses IPv6 ###### ###### ACCU Quick Connectivity Test (done) ### Either the above all works and gives no problems ### or it shows you where what goes wrong ### Check the SixXS FAQ (http://www.sixxs.net/faq/ ### for more information and possible solutions or hints ### Don't forget to check the Forums (http://www.sixxs.net/forum/) ### for a helping hand. ### Passing the output of 'aiccu autotest >aiccu.log' is a good idea. C:\Users\Dancsi>tracert -6 2001:15c0:65ff:558::1 Tracing route to gw-1369.mbx-01.si.sixxs.net [2001:15c0:65ff:558::1] over a maximum of 30 hops: 1 40 ms 40 ms 44 ms gw-1369.mbx-01.si.sixxs.net [2001:15c0:65ff:558::1] Trace complete. C:\Users\Dancsi>tracert -6 ipv6.google.com Tracing route to ipv6.l.google.com [2a00:1450:8007::69] over a maximum of 30 hops: 1 * * * Request timed out. 2 General failure. Trace complete. Also, I have added that registry key to Dnscache/Parameters
IPv6 stopped working on Win7x64
[ch] Jeroen Massar SixXS Staff on Tuesday, 01 March 2011 20:24:27
[..]
Yes Manual 256 ::/0 35 2001:15c0:65ff:558::1
Yes Manual 256 ::/0 28 2001:15c0:65ff:558::1
No Manual 256 ::1/128 1 Loopback Pseudo-Interface 1
No Manual 256 2001:15c0:65ff:558::/64 35 VirtualBox Host-Only Network
No Manual 256 2001:15c0:65ff:558::/64 28 aiccu
No Manual 256 2001:15c0:65ff:558::2/128 35 VirtualBox Host-Only Network
I don't know why you have that, but you have address on your aiccu interface and on this "VirtualBox Host-Only Network" interface. You might want to get rid of the latter as a first step.
IPv6 stopped working on Win7x64
[rs] Shadow Hawkins on Tuesday, 01 March 2011 20:28:06
Thank you very much, I disabled the VirtualBox interface and now it's working :) Do you know how to change its address because I'd still like to use internet in my virtual machines?
IPv6 stopped working on Win7x64
[rs] Shadow Hawkins on Tuesday, 01 March 2011 20:35:15
Ok, nevermind, I did it myself, and for now, everything is working...
IPv6 stopped working on Win7x64
[us] Shadow Hawkins on Thursday, 10 March 2011 01:36:40
Most likely the OP at some point tried a manual address assignment on the VirtualBox interface. When you add an ipv6 prefix::address to an interface Vista/Win7 automatically adds an unpublished prefix::64/ route to that interface. Probably it should not be doing that.

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

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