SixXS::Sunset 2017-06-06

Windows7 Home Premium no browsing
[nl] Shadow Hawkins on Wednesday, 02 December 2009 22:58:18
Hello everyone, maybe you have some ideas, cause i have ran out of them... I can't browse in IE8 or Firefox with IPV6, or use the BT tracker from SixXS BUT everything else works perfectly, i even can ping a hostname (ie. ipv6.google.com) and get a reply back with an IPV6 address. Before anyone asks.... :-) yes i have turned off all stuff like Antispam/Antivirus/Firewall and i followed the Vista guide on the wiki. It even works as a service and connects perfectly at startup. I have an autotest dump here (i tracerouted the last two manually cause 7 is different from XP) and bear with me, some things are in dutch, but the general idea is the same:
Tunnel Information for T24170: PoP Id : nlhaa01 IPv6 Local : 2001:1af8:fe00:1ec::2/64 IPv6 Remote : 2001:1af8:fe00:1ec::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.8) ### 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 Pingen naar 192.168.1.8 met 32 bytes aan gegevens: Antwoord van 192.168.1.8: bytes=32 tijd=2 ms TTL=128 Antwoord van 192.168.1.8: bytes=32 tijd=2 ms TTL=128 Antwoord van 192.168.1.8: bytes=32 tijd=2 ms TTL=128 Ping-statistieken voor 192.168.1.8: Pakketten: verzonden = 3, ontvangen = 3, verloren = 0 (0% verlies). De gemiddelde tijd voor het uitvoeren van n bewerking in milliseconden: Minimum = 2ms, Maximum = 2ms, Gemiddelde = 2ms ###### ####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (94.75.219.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 Pingen naar 94.75.219.73 met 32 bytes aan gegevens: Antwoord van 94.75.219.73: bytes=32 tijd=31 ms TTL=57 Antwoord van 94.75.219.73: bytes=32 tijd=31 ms TTL=57 Antwoord van 94.75.219.73: bytes=32 tijd=31 ms TTL=57 Ping-statistieken voor 94.75.219.73: Pakketten: verzonden = 3, ontvangen = 3, verloren = 0 (0% verlies). De gemiddelde tijd voor het uitvoeren van n bewerking in milliseconden: Minimum = 31ms, Maximum = 31ms, Gemiddelde = 31ms ###### ####### [3/8] Traceroute to the PoP (94.75.219.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 Traceren van de route naar nlhaa01.sixxs.net [94.75.219.73] via maximaal 30 hops: 1 11 ms 2 ms 2 ms 192.168.1.1 2 26 ms 29 ms 27 ms ip1-144-173-82.adsl2.static.versatel.nl [82.173.144.1] 3 29 ms 28 ms 28 ms ge-0-1-0-1305.ncr01asd2.versatel.net [217.16.44.49] 4 31 ms 31 ms 31 ms ge-1-0-0-668.br01sara.versatel.net [212.53.18.26] 5 33 ms 31 ms 33 ms crs-tc2.leaseweb.net [195.69.144.215] 6 31 ms 31 ms 31 ms po80.hv5.evo.leaseweb.net [62.212.80.78] 7 31 ms 31 ms 31 ms nlhaa01.sixxs.net [94.75.219.73] De trace is voltooid. ###### ###### [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 Pingen naar ::1 met 32 bytes aan gegevens: Antwoord van ::1: tijd<1 ms Antwoord van ::1: tijd<1 ms Antwoord van ::1: tijd<1 ms Ping-statistieken voor ::1: Pakketten: verzonden = 3, ontvangen = 3, verloren = 0 (0% verlies). De gemiddelde tijd voor het uitvoeren van n bewerking in milliseconden: Minimum = 0ms, Maximum = 0ms, Gemiddelde = 0ms ###### ###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:1af8:fe00:1ec::2) ### This confirms that your tunnel is configured ### If it doesn't reply then check your interface and routing tables Pingen naar 2001:1af8:fe00:1ec::2 met 32 bytes aan gegevens: Antwoord van 2001:1af8:fe00:1ec::2: tijd<1 ms Antwoord van 2001:1af8:fe00:1ec::2: tijd<1 ms Antwoord van 2001:1af8:fe00:1ec::2: tijd<1 ms Ping-statistieken voor 2001:1af8:fe00:1ec::2: Pakketten: verzonden = 3, ontvangen = 3, verloren = 0 (0% verlies). De gemiddelde tijd voor het uitvoeren van n bewerking in milliseconden: Minimum = 0ms, Maximum = 0ms, Gemiddelde = 0ms ###### ###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:1af8:fe00:1ec::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 Pingen naar 2001:1af8:fe00:1ec::1 met 32 bytes aan gegevens: Antwoord van 2001:1af8:fe00:1ec::1: tijd=32 ms Antwoord van 2001:1af8:fe00:1ec::1: tijd=31 ms Antwoord van 2001:1af8:fe00:1ec::1: tijd=32 ms Ping-statistieken voor 2001:1af8:fe00:1ec::1: Pakketten: verzonden = 3, ontvangen = 3, verloren = 0 (0% verlies). De gemiddelde tijd voor het uitvoeren van n bewerking in milliseconden: Minimum = 31ms, Maximum = 32ms, Gemiddelde = 31ms ###### ###### [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. C:\>tracert -6 noc.sixxs.net Traceren van de route naar noc.sixxs.net [2001:838:1:1:210:dcff:fe20:7c7c] via maximaal 30 hops: 1 33 ms 32 ms 33 ms gw-493.haa-01.nl.sixxs.net [2001:1af8:fe00:1ec:: 1] 2 33 ms 33 ms 34 ms 2001:1af8:1:f006:218:74ff:fe46:3200 3 33 ms 33 ms 36 ms be25.crs.evo.leaseweb.net [2001:1af8::19] 4 36 ms 33 ms 34 ms ams-ix.ipv6.concepts.nl [2001:7f8:1::a501:2871:1 ] 5 36 ms 36 ms 34 ms 2001:838:5:a::2 6 35 ms 35 ms 35 ms noc.sixxs.net [2001:838:1:1:210:dcff:fe20:7c7c] De trace is voltooid. ###### ###### [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 C:\>tracert -6 www.kame.net Traceren van de route naar www.kame.net [2001:200:0:8002:203:47ff:fea5:3085] via maximaal 30 hops: 1 35 ms 32 ms 33 ms gw-493.haa-01.nl.sixxs.net [2001:1af8:fe00:1ec:: 1] 2 32 ms 33 ms 37 ms 2001:1af8:1:f006:218:74ff:fe46:3200 3 34 ms 34 ms 34 ms be25.crs.tc2.leaseweb.net [2001:1af8::3d] 4 33 ms 33 ms 33 ms ams-ix.he.net [2001:7f8:1::a500:6939:1] 5 49 ms 49 ms 50 ms 10gigabitethernet1-4.core1.lon1.he.net [2001:470 :0:3f::1] 6 108 ms 108 ms 110 ms 10gigabitethernet2-3.core1.nyc4.he.net [2001:470 :0:3e::1] 7 175 ms 181 ms 172 ms 10gigabitethernet5-3.core1.lax1.he.net [2001:470 :0:10e::1] 8 182 ms 178 ms 181 ms 10gigabitethernet1-3.core1.pao1.he.net [2001:470 :0:34::1] 9 179 ms 179 ms 179 ms 3ffe:80a::b2 10 304 ms 305 ms 305 ms hitachi1.otemachi.wide.ad.jp [2001:200:0:4401::3 ] 11 304 ms 304 ms 304 ms 2001:200:0:1802:20c:dbff:fe1f:7200 12 303 ms 305 ms 305 ms ve42.foundry4.nezu.wide.ad.jp [2001:200:0:11::66 ] 13 305 ms 305 ms 307 ms ve45.foundry2.yagami.wide.ad.jp [2001:200:0:12:: 74] 14 307 ms 306 ms 306 ms 2001:200:0:4803:212:e2ff:fe28:1ca2 15 305 ms 307 ms 306 ms orange.kame.net [2001:200:0:8002:203:47ff:fea5:3 085] De trace is voltooid. ###### ###### 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.
Name resolving seems to work perfectly in the CMDline. The browsers however dont recognize the (ipv6) webaddresses. Bit if i browse using firefox like http://[2001:4860:a003::68]/ (which is google) i get the page perfectly in the browser. Anyone got more ideas? I'm out of them. Many thanks in advance.
Windows7 Home Premium no browsing
[nl] Shadow Hawkins on Wednesday, 02 December 2009 23:14:34
I forgot to place my IP configuration:
Windows IP-configuratie Hostnaam . . . . . . . . . . . . : L2K-LAPTOP Primair DNS-achtervoegsel . . . . : Knooppunttype . . . . . . . . . . : hybride IP-routering ingeschakeld . . . . : nee WINS-proxy ingeschakeld . . . . . : nee Draadloos LAN-adapter voor Draadloze netwerkverbinding: Verbindingsspec. DNS-achtervoegsel: Beschrijving. . . . . . . . . . . : Atheros AR5B91 Wireless Network Adapter Fysiek adres. . . . . . . . . . . : 00-24-2C-68-A2-22 DHCP ingeschakeld . . . . . . . . : ja Autom. configuratie ingeschakeld : ja Link-local IPv6-adres . . . . . . : fe80::f058:db82:14cc:d3dd%12(voorkeur) IPv4-adres. . . . . . . . . . . . : 192.168.1.8(voorkeur) Subnetmasker. . . . . . . . . . . : 255.255.255.0 Lease verkregen . . . . . . . . . : woensdag 2 december 2009 17:01:37 Lease verlopen. . . . . . . . . . : donderdag 3 december 2009 17:01:38 Standaardgateway. . . . . . . . . : 192.168.1.1 DHCP-server . . . . . . . . . . . : 192.168.1.1 DHCPv6 IAID . . . . . . . . . . . : 218113068 DHCPv6-client DUID. . . . . . . . : 00-01-00-01-12-8F-66-E4-00-23-5A-8C-F4-11 DNS-servers . . . . . . . . . . . : 192.168.1.1 NetBIOS via TCPIP . . . . . . . . : ingeschakeld Ethernet-adapter voor LAN-verbinding: Mediumstatus. . . . . . . . . . . : medium ontkoppeld Verbindingsspec. DNS-achtervoegsel: Beschrijving. . . . . . . . . . . : Broadcom NetLink (TM) Gigabit Ethernet Fysiek adres. . . . . . . . . . . : 00-23-5A-8C-F4-11 DHCP ingeschakeld . . . . . . . . : ja Autom. configuratie ingeschakeld : ja Ethernet-adapter voor sixxs: Verbindingsspec. DNS-achtervoegsel: Beschrijving. . . . . . . . . . . : TAP-Win32 Adapter V9 Fysiek adres. . . . . . . . . . . : 00-FF-7F-A4-67-51 DHCP ingeschakeld . . . . . . . . : ja Autom. configuratie ingeschakeld : ja IPv6-adres. . . . . . . . . . . . : 2001:1af8:fe00:1ec::2(voorkeur) Link-local IPv6-adres . . . . . . : fe80::816a:3a96:3d93:594%13(voorkeur) Standaardgateway. . . . . . . . . : 2001:1af8:fe00:1ec::1 DHCPv6 IAID . . . . . . . . . . . : 486604671 DHCPv6-client DUID. . . . . . . . : 00-01-00-01-12-8F-66-E4-00-23-5A-8C-F4-11 DNS-servers . . . . . . . . . . . : fec0:0:0:ffff::1%1 fec0:0:0:ffff::2%1 fec0:0:0:ffff::3%1 NetBIOS via TCPIP . . . . . . . . : uitgeschakeld
Windows7 Home Premium no browsing
[nl] Shadow Hawkins on Thursday, 03 December 2009 00:41:29
Hello again :-) It gets stranger, it sure has to do with some name resolving issues, maybe some wrong DNS setting. Or the Windows7 GUI (win32api) doesnt resolve. I tried an IPV6 newsserver (newszilla) with an IPV6 usenetclient (Bintube, it doesnt need NT6Tunnel). When i try to connect to newszilla6.xs4all.nl it doesnt connect, when i put the resolved IPV6 address in the newsclients settings, it works like a charm. Again.... Thanks in advance if someone has ideas.
Windows7 Home Premium no browsing
[us] Shadow Hawkins on Thursday, 03 December 2009 03:58:20
http://www.sixxs.net/wiki/Configuring_Windows_Vista Works for Windows 7 as well. The part you are missing is in step 8. netsh int ipv6 add address "Local Area Connection" 2002:81a8:102:: Of course, since you are using a Dutch OS, you will need to change "Local Area Connection" to the appropriate string. I am guessing that would be "Draadloze netwerkverbinding", but I may be off, as my Dutch is weak ;) You should also make certain that your DNS server is not buggy with AAAA lookups, but that is easy: nslookup -type=AAAA www.ipv6.sixxs.net * The response should look something like this: Non-authoritative answer: Name: www.ipv6.m.sixxs.net Address: 2001:838:1:1:210:dcff:fe20:7c7c Aliases: www.ipv6.sixxs.net Good Luck. --_Dave
Windows7 Home Premium no browsing
[nl] Shadow Hawkins on Thursday, 03 December 2009 11:18:33
Thanks, how the **** did I miss that step!!! It works fine now!! /me gets in a corner overthinking his stupidity :-) And you are correct, it was "Draadloze netwerkverbinding" that stands for "Wireless network connection" :-) Again, thanks :-)

Please note Posting is only allowed when you are logged in.
Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker