Why AICCU Windows console needs an aiccu.conf on C:\WINDOWS? It might be interesting if it came together with the exe on a zip at least. Anyway, I've got it from this ticket, and just added login and password. Then using test and autotest, both gives the same result: C:\Documents and Settings\esimioni>aiccu-2008-03-15-windows-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/5.1.2600-SP3" sock_getline() : "200 Client Identity accepted" sock_printf() : "get unixtime" sock_getline() : "200 1227278443" sock_printf() : "username EAS2-SIXXS" sock_getline() : "200 Choose your authentication challenge please" sock_printf() : "challenge md5" sock_getline() : "200 03958d00028533f51b46edfe31c7d00c" sock_printf() : "authenticate md5 1f7bbef6b0bee3906af4d61edf150f87" sock_getline() : "200 Succesfully logged in using md5 as EAS2-SIXXS (Eduardo Augusto Simioni) from 2001:960:800::2" sock_printf() : "tunnel show T18094" sock_getline() : "201 Showing tunnel information for T18094" sock_getline() : "TunnelId: T18094" sock_getline() : "Type: ayiya" sock_getline() : "IPv6 Endpoint: 2001:1418:100:2af::2" sock_getline() : "IPv6 POP: 2001:1418:100:2af::1" sock_getline() : "IPv6 PrefixLength: 64" sock_getline() : "Tunnel MTU: 1280" sock_getline() : "Tunnel Name: My First Tunnel" sock_getline() : "POP Id: ittrn01" sock_getline() : "IPv4 Endpoint: ayiya" sock_getline() : "IPv4 POP: 213.254.12.34" sock_getline() : "UserState: enabled" sock_getline() : "AdminState: enabled" sock_getline() : "Password: *******" sock_getline() : "Heartbeat_Interval: 60" sock_getline() : "202 Done" Succesfully retrieved tunnel information for T18094 sock_printf() : "QUIT Tschau!" Tunnel Information for T18094: PoP Id : ittrn01 IPv6 Local : 2001:1418:100:2af::2/64 IPv6 Remote : 2001:1418:100:2af::1/64 Tunnel Type : ayiya Adminstate : enabled Userstate : enabled Name : My First Tunnel Flag: HAS_IFHEAD not present Flag: NEED_IFHEAD not present [warning] Couldn't open registry key: SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000\Comp onentId (t2/2 vs 0/1736 vs 1) Renaming adapter 'aiccu' to 'sixxs' and using it [tun-start] Trying \\.\Global\{AD0485E8-C609-4969-B29E-25B1154128CC}.tap [error] [tun-start] Problem while enumerating key SYSTEM\CurrentControlSet\Control\Network\{4D36E972-E325-11CE-BFC1-08002BE10 318} [error] [tun-start] No working Tap device found! [error] Tunnel Setup Failed

Please disregard the other post about the autotest result. I had the GUI open, didn't realised it needed to connect itself during test. Anyway, here's the result: C:\Documents and Settings\esimioni>aiccu-2008-03-15-windows-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/5.1.2600-SP3" sock_getline() : "200 Client Identity accepted" sock_printf() : "get unixtime" sock_getline() : "200 1227282190" sock_printf() : "username EAS2-SIXXS" sock_getline() : "200 Choose your authentication challenge please" sock_printf() : "challenge md5" sock_getline() : "200 8bcb212b2449980dbabf95117d99d1c5" sock_printf() : "authenticate md5 dbfdb1feabeb0b1ccf9a2fb4b3850673" sock_getline() : "200 Succesfully logged in using md5 as EAS2-SIXXS (Eduardo Augusto Simioni) from 2001:7b8:3:4f:202:b3ff:fe4 6:bec" sock_printf() : "tunnel show T18094" sock_getline() : "201 Showing tunnel information for T18094" sock_getline() : "TunnelId: T18094" sock_getline() : "Type: ayiya" sock_getline() : "IPv6 Endpoint: 2001:1418:100:2af::2" sock_getline() : "IPv6 POP: 2001:1418:100:2af::1" sock_getline() : "IPv6 PrefixLength: 64" sock_getline() : "Tunnel MTU: 1280" sock_getline() : "Tunnel Name: My First Tunnel" sock_getline() : "POP Id: ittrn01" sock_getline() : "IPv4 Endpoint: ayiya" sock_getline() : "IPv4 POP: 213.254.12.34" sock_getline() : "UserState: enabled" sock_getline() : "AdminState: enabled" sock_getline() : "Password: ************" sock_getline() : "Heartbeat_Interval: 60" sock_getline() : "202 Done" Succesfully retrieved tunnel information for T18094 sock_printf() : "QUIT This is not our farewell" Tunnel Information for T18094: PoP Id : ittrn01 IPv6 Local : 2001:1418:100:2af::2/64 IPv6 Remote : 2001:1418:100:2af::1/64 Tunnel Type : ayiya Adminstate : enabled Userstate : enabled Name : My First Tunnel Flag: HAS_IFHEAD not present Flag: NEED_IFHEAD not present [warning] Couldn't open registry key: SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0000\Comp onentId (t2/2 vs 0/1736 vs 1) Found interface named 'sixxs', with guid {AD0485E8-C609-4969-B29E-25B1154128CC}, using it [tun-start] Trying \\.\Global\{AD0485E8-C609-4969-B29E-25B1154128CC}.tap Flag: HAS_IFHEAD not present Flag: NEED_IFHEAD not present [AYIYA-start] : Anything in Anything (draft-02) [AYIYA-tun->tundev] : (Socket to TUN) started heartbeat_socket() - IPv4 : 10.0.10.185 ####### ####### AICCU Quick Connectivity Test ####### ####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (10.0.10.185) ### 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 10.0.10.185 with 32 bytes of data: Reply from 10.0.10.185: bytes=32 time<1ms TTL=128 Reply from 10.0.10.185: bytes=32 time<1ms TTL=128 Reply from 10.0.10.185: bytes=32 time<1ms TTL=128 Ping statistics for 10.0.10.185: 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 (213.254.12.34) ### 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 213.254.12.34 with 32 bytes of data: Reply from 213.254.12.34: bytes=32 time=102ms TTL=53 Reply from 213.254.12.34: bytes=32 time=78ms TTL=53 Reply from 213.254.12.34: bytes=32 time=110ms TTL=53 Ping statistics for 213.254.12.34: Packets: Sent = 3, Received = 3, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 78ms, Maximum = 110ms, Average = 96ms ###### ####### [3/8] Traceroute to the PoP (213.254.12.34) 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 frejus.itgate.net [213.254.12.34] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 10.0.10.10 2 1 ms 1 ms 1 ms 192.168.1.1 3 102 ms 107 ms 83 ms 213.205.24.14 4 154 ms 70 ms 69 ms 213.205.28.66 5 77 ms 70 ms 72 ms 213.205.56.117 6 76 ms * 86 ms 213.205.25.153 7 83 ms 81 ms 50 ms sl-bb20-mil.sprintlink.net [213.200.68.182] 8 75 ms 64 ms 68 ms sl-gw10-mil-14-0-0.sprintlink.net [217.147.128.37] 9 84 ms * 128 ms 217.147.129.54 10 66 ms 74 ms 81 ms if-0-3.scrappy-monster.core.trn.itgate.net [213.254.31.245] 11 113 ms 111 ms * if-0-0.charleston.cbq.trn.itgate.net [213.254.0.13] 12 104 ms 116 ms 106 ms frejus.itgate.net [213.254.12.34] 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:1418:100:2af::2) ### This confirms that your tunnel is configured ### If it doesn't reply then check your interface and routing tables Pinging 2001:1418:100:2af::2 with 32 bytes of data: Reply from 2001:1418:100:2af::2: time<1ms Reply from 2001:1418:100:2af::2: time<1ms Reply from 2001:1418:100:2af::2: time<1ms Ping statistics for 2001:1418:100:2af::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:1418:100:2af::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:1418:100:2af::1 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Ping statistics for 2001:1418:100:2af::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 connection ### If your browser supports IPv6 and uses it of course. Tracing route to noc.sixxs.net [2001:838:1:1:210:dcff:fe20:7c7c] from 2001:1418:100:2af::2 over a maximum of 30 hops: 1 * * * Request timed out. 2 * * * Request timed out. 3 * * * Request timed out. 4 * * * Request timed out. 5 * * * Request timed out. 6 * * * Request timed out. 7 * * * Request timed out. 8 * * * Request timed out. 9 * * * Request timed out. 10 * * * Request timed out. 11 * * * Request timed out. 12 * * * Request timed out. 13 * * * Request timed out. 14 * * * Request timed out. 15 * * * Request timed out. 16 * * * Request timed out. 17 * * * Request timed out. 18 * * * Request timed out. 19 * * * Request timed out. 20 * * * Request timed out. 21 * * * Request timed out. 22 * * * Request timed out. 23 * * * Request timed out. 24 * * * Request timed out. 25 * * * Request timed out. 26 * * * Request timed out. 27 * * * Request timed out. 28 * * * Request timed out. 29 * * * Request timed out. 30 * * * Request timed out. Trace complete. ###### ###### [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 Tracing route to www.kame.net [2001:200:0:8002:203:47ff:fea5:3085] from 2001:1418:100:2af::2 over a maximum of 30 hops: 1 * * * Request timed out. 2 * * * Request timed out. 3 * * * Request timed out. 4 * * * Request timed out. 5 * * * Request timed out. 6 * * * Request timed out. 7 * * * Request timed out. 8 * * * Request timed out. 9 * * * Request timed out. 10 * * * Request timed out. 11 * * * Request timed out. 12 * * * Request timed out. 13 * * * Request timed out. 14 * * * Request timed out. 15 * * * Request timed out. 16 * * * Request timed out. 17 * * * Request timed out. 18 * * * Request timed out. 19 * * * Request timed out. 20 * * * Request timed out. 21 * * * Request timed out. 22 * * * Request timed out. 23 * * * Request timed out. 24 * * * Request timed out. 25 * * * Request timed out. 26 * * * Request timed out. 27 * * * Request timed out. 28 * * * Request timed out. 29 * * * Request timed out. 30 * * * Request timed out. Trace complete. ###### ###### 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. And ok, it's the router or firewall configuration. But I don't have access to neither of them. Is it a port that need to be open? What exactly should be open? From all five cases listed here, which is the most probable one on this case?

Microsofts Firewall which comes included with the OS. Indeed, that is far from a perfect solution, but it does properly do IPv6. For every other product, you will have to test this out.