OK, here's the very latest: Z:\>netsh int ipv6 sh route Publish Type Met Prefix Idx Gateway/Interface Name ------- -------- --- ------------------------ --- ------------------------ Yes Manual 256 ::/0 16 2001:4978:f:21d::1 No Manual 256 ::1/128 1 Loopback Pseudo-Interface 1 No Manual 256 2001:4978:f:21d::/64 16 aiccu No Manual 256 2001:4978:f:21d::2/128 16 aiccu No Manual 256 fdfe:182a:bdca:470f::/64 11 Local Area Connection 2 No Manual 256 fdfe:182a:bdca:470f::a00/128 11 Local Area Connection 2 No Manual 256 fe80::/64 16 aiccu No Manual 256 fe80::/64 11 Local Area Connection 2 No Manual 256 fe80::6164:9e73:407c:e6bd/128 11 Local Area Connectio n 2 No Manual 256 fe80::f113:9f2e:69a8:f5c7/128 16 aiccu No Manual 256 ff00::/8 1 Loopback Pseudo-Interface 1 No Manual 256 ff00::/8 16 aiccu No Manual 256 ff00::/8 11 Local Area Connection 2 Z:\>netsh int ipv6 sh ad Interface 1: Loopback Pseudo-Interface 1 Addr Type DAD State Valid Life Pref. Life Address --------- ----------- ---------- ---------- ------------------------ Other Preferred infinite infinite ::1 Interface 11: Local Area Connection 2 Addr Type DAD State Valid Life Pref. Life Address --------- ----------- ---------- ---------- ------------------------ Manual Preferred infinite infinite fdfe:182a:bdca:470f::a00 Other Preferred infinite infinite fe80::6164:9e73:407c:e6bd%11 Interface 16: aiccu Addr Type DAD State Valid Life Pref. Life Address --------- ----------- ---------- ---------- ------------------------ Manual Preferred infinite infinite 2001:4978:f:21d::2 Other Preferred infinite infinite fe80::f113:9f2e:69a8:f5c7%16 Z:\>ipconfig /all Windows IP Configuration Host Name . . . . . . . . . . . . : bknoblauch Primary Dns Suffix . . . . . . . : sscorp.com Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : sscorp.com Ethernet adapter aiccu: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : TAP-Win32 Adapter V9 Physical Address. . . . . . . . . : 00-FF-86-7E-64-13 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IPv6 Address. . . . . . . . . . . : 2001:4978:f:21d::2(Preferred) Link-local IPv6 Address . . . . . : fe80::f113:9f2e:69a8:f5c7%16(Preferred) Autoconfiguration IPv4 Address. . : 169.254.245.199(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.0.0 Default Gateway . . . . . . . . . : 2001:4978:f:21d::1 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 2: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Realtek RTL8168B/8111B Family PCI-E Gigab it Ethernet NIC (NDIS 6.0) Physical Address. . . . . . . . . : 00-1A-4D-5F-03-47 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes IPv6 Address. . . . . . . . . . . : fdfe:182a:bdca:470f::a00(Preferred) Link-local IPv6 Address . . . . . : fe80::6164:9e73:407c:e6bd%11(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.100.65(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.254.0 Default Gateway . . . . . . . . . : 192.168.100.1 DNS Servers . . . . . . . . . . . : 192.168.102.10 192.168.102.14 NetBIOS over Tcpip. . . . . . . . : Enabled Z:\>aiccu-console.exe autotest sock_getline() : "200 SixXS TIC Service on noc.sixxs.net ready (http://www.sixxs .net)" sock_printf() : "client TIC/draft-00 AICCU/2008.03.15-console-win32 WinNT/6.0.6 001-SP1" sock_getline() : "200 Client Identity accepted" sock_printf() : "get unixtime" sock_getline() : "200 1228421618" sock_printf() : "username BKU3-SIXXS" sock_getline() : "200 Choose your authentication challenge please" sock_printf() : "challenge md5" sock_getline() : "200 76382caaa854c64c1e4c7796d5d37e20" sock_printf() : "authenticate md5 e4d357f27788ed98edeba2615eb396f2" sock_getline() : "200 Succesfully logged in using md5 as BKU3-SIXXS (Brian Knobl auch) from 2001:7b8:3:4f:202:b3ff:fe46:bec" sock_printf() : "tunnel show T18391" sock_getline() : "201 Showing tunnel information for T18391" sock_getline() : "TunnelId: T18391" sock_getline() : "Type: ayiya" sock_getline() : "IPv6 Endpoint: 2001:4978:f:21d::2" sock_getline() : "IPv6 POP: 2001:4978:f:21d::1" sock_getline() : "IPv6 PrefixLength: 64" sock_getline() : "Tunnel MTU: 1280" sock_getline() : "Tunnel Name: My First Tunnel" sock_getline() : "POP Id: uschi02" sock_getline() : "IPv4 Endpoint: ayiya" sock_getline() : "IPv4 POP: 216.14.98.22" sock_getline() : "UserState: enabled" sock_getline() : "AdminState: enabled" sock_getline() : "Password: xxxx" sock_getline() : "Heartbeat_Interval: 60" sock_getline() : "202 Done" Succesfully retrieved tunnel information for T18391 sock_printf() : "QUIT Running Down That Hill" Tunnel Information for T18391: PoP Id : uschi02 IPv6 Local : 2001:4978:f:21d::2/64 IPv6 Remote : 2001:4978:f:21d::1/64 Tunnel Type : ayiya Adminstate : enabled Userstate : enabled Name : My First Tunnel Flag: HAS_IFHEAD not present Flag: NEED_IFHEAD not present [warning] Error opening registry key: SYSTEM\CurrentControlSet\Control\Class\{4D 36E972-E325-11CE-BFC1-08002BE10318}\Properties (t1) Found interface named 'aiccu', with guid {867E6413-7769-4136-B6DC-DEFFE09CBE97}, using it [tun-start] Trying \\.\Global\{867E6413-7769-4136-B6DC-DEFFE09CBE97}.tap Flag: HAS_IFHEAD not present Flag: NEED_IFHEAD not present [AYIYA-start] : Anything in Anything (draft-02) heartbeat_socket() - IPv4 : 192.168.100.65 [AYIYA-tun->tundev] : (Socket to TUN) started ####### ####### AICCU Quick Connectivity Test ####### ####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (192.168.100.65) ### 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.100.65 with 32 bytes of data: Reply from 192.168.100.65: bytes=32 time<1ms TTL=128 Reply from 192.168.100.65: bytes=32 time<1ms TTL=128 Reply from 192.168.100.65: bytes=32 time<1ms TTL=128 Ping statistics for 192.168.100.65: 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 (216.14.98.22) ### 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 216.14.98.22 with 32 bytes of data: Reply from 216.14.98.22: bytes=32 time=18ms TTL=53 Reply from 216.14.98.22: bytes=32 time=18ms TTL=53 Reply from 216.14.98.22: bytes=32 time=30ms TTL=53 Ping statistics for 216.14.98.22: Packets: Sent = 3, Received = 3, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 18ms, Maximum = 30ms, Average = 22ms ###### ####### [3/8] Traceroute to the PoP (216.14.98.22) 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 sixxs.cx01.chi.bb.your.org [216.14.98.22] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 12.199.185.1 2 9 ms 8 ms 24 ms 12.88.183.17 3 17 ms 24 ms 30 ms cr81.dtrmi.ip.att.net [12.122.102.14] 4 19 ms 61 ms 47 ms cr1.cgcil.ip.att.net [12.123.139.157] 5 19 ms 17 ms 19 ms tbr1.cgcil.ip.att.net [12.122.17.138] 6 21 ms 35 ms 52 ms ggr6.cgcil.ip.att.net [12.122.87.245] 7 31 ms 37 ms 19 ms 192.205.35.138 8 41 ms 17 ms 16 ms your.org.ge2-5.br02.chc01.pccwbtn.net [63.218.5. 38] 9 16 ms 16 ms 21 ms sixxs.cx01.chi.bb.your.org [216.14.98.22] 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 from ::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:4978:f:21d::2) ### This confirms that your tunnel is configured ### If it doesn't reply then check your interface and routing tables Pinging 2001:4978:f:21d::2 from 2001:4978:f:21d::2 with 32 bytes of data: Reply from 2001:4978:f:21d::2: time<1ms Reply from 2001:4978:f:21d::2: time<1ms Reply from 2001:4978:f:21d::2: time<1ms Ping statistics for 2001:4978:f:21d::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:4978:f:21d::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:4978:f:21d::1 from 2001:4978:f:21d::2 with 32 bytes of data: Destination host unreachable. Destination host unreachable. Destination host unreachable. Ping statistics for 2001:4978:f:21d::1: Packets: Sent = 3, Received = 0, Lost = 3 (100% loss), ###### ###### [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 connecti on ### If your browser supports IPv6 and uses it of course. 'tracert6' is not recognized as an internal or external command, operable program or batch file. ###### ###### [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 'tracert6' is not recognized as an internal or external command, operable program or batch file. ###### ###### 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.