Thus, Win7 limits me by not resolving IPv6 sites and also the PNRP protocol
will not work ...
Is there any tweak to make Win7 resolve sites,
when only having Teredo?
greetings
Roland Schweiger
On XP, I have enabled Terado and have no problems (short of latency)
in accessing IPV6 sites such as ipv6.google.com. I assume that you
have verified that the IPV6 protocol is enabled for Win7.
Ed
There certainly must be ipv6 enabled because the NIC gets link-lokal (fd00:)
and "proper public" ipv6 addresses (2001:).
Also i tried an alternative - the Hexago Gateway6 client with freenet6, it
also installs a pseudo tunneling adapter and all works fine when i use this.
However i assumed Teredo more stable but Win7 (and also Vista) tend to limit
access when only having teredo.
The name server(s) will not resolve sites and when i register my machine
name using the PNRP protocol, it will not work. Win7 will always "prefer"
IPv4 connectivity when only having Teredo but i thoght there might be some
kind of trick to prevent it from doing this.
greetings from Dresden.
Roland Schweiger
Ah, perhaps I see the problem. It is my experience that IPV6 is only
used for IPV6 DNS registered sites from Windows XP (and I believe
Vista), There are lists of such sites. Try them.
I use an add on (showip 0.8.17) to Firefox that show addresses of
Foreign Sites including IPV6 addresses, e.g., ipv6.google.com -
2001:4860:b002::68. If you can see this site, you are using ipv6.
They don't seem to respond if addressed in ipv4. I use satellite
internet so latency often causes timeout.
My great grandfather came from Zwickau, Saxony in the 1860s.
Regards,
Ed Feustel
Well so far my experience is this:
As i don't have native IPv6, i must use either one of the many tunneling
solutions, or Teredo (which is also a tunnel but a kind of MS built-in).
When i use any of the external tunnel solutions in Win7 (i prefer the Hexago
Client6), then all works pretty well, i can resolve, call-up or PING
practically any IPv6 site and i also can use the PNRP protocol to give
myself a name, such as
MyMachineName.pnrp.net
This will then resolve in a cloud with PNRP and does not require any name
servers,
i need this for direct ip to ip telephony when trapped behind an (IPv4) NAT
router,
i also need this to use remote terminal services etc.
As soon as i use Teredo instead, the IPCONFIG /ALL shows me the pseudo
tunnel device of Teredo and it also shows me a public IP that "somehow"
works but not in practical use.
The PNRP seeding stops working and my machine is no longer reachable from
outside.
And i can query IPv6 names but i cannot PING, nor can i reach them.
At the moment it does not really matter and for the time being i will
continue using the Client6,
only problem it does not start automatically at Win7 start.
> My great grandfather came from Zwickau, Saxony in the 1860s.
That is relatively close to Dresden.
Actually i come from Austria, the southern neigbouring country to Germany,
i am from the Capital City Vienna.
But about 10 years ago i came to Dresden and currently live here.
Nice little city ... but much smaller than Vienna. :-)
greetings
Roland Schweiger
ping -6 irc.ipv6.cesnet.cz
tracert -6 irc.ipv6.cesnet.cz
start http://[2a00:1450:8001::68]/
but i can NOT i.e. start http://ipv6.google.com
Any solutions or everyone stuck the same way?
Thx
MP
1. assigning IPV6 address to interface used to connect. In my case it is
WiFi connection with IPV4 10.0.0.5 so I used IPV6 2002:A00:5:: / 48. No GW
2. netsh interface ipv6 add route ::/0 "Wireless Network Connection" <---
the interface used above
3. netsh interface ipv6 add route ::/0 "Local Area Connection* 16" <--- use
ipconfig /all to see which is the Teredo Tunneling Pseudo-Interface:
ipconfig /all
....
Tunnel adapter Local Area Connection* 16:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
...
MP
Hi,
ich schreibe mal deutsch an einen Dresdener; man m�ge mir verzeihen...
ich habe ein gro�es Problem mit ipv6. Ich benutze sabnzbd+, um auf
usenet-Gruppen zuzugreifen. Mit Windows XP und mit Windows 7 geht das
problemlos via gogo6-Tunnel; nur mit Vista geht es nicht. Dabei habe ich
die Vista-Firewall komplett ausgeschaltet. Ich wei� nicht mehr, wo ich
den Fehler suchen soll; und das seit etwa einem halben Jahr.
Ich bin um jeden Ansatzpunkt f�r die Fehlersuche dankbar; vielleicht
wird ja ein �lteres Modell eines Kyocera-Laserdruckers gefragt...
Viele Gr��e.
MP
P.S. English is _lingua franca_ here
"Rimifon" <webm...@fengyun.org> wrote in message
news:op.u9jrm...@zhoufeng.web...
"Miroslav Pragl" wrote:
> I think we try to slolve this problem using native tools, not 3rd. party
> language
>
> MP
>
> P.S. English is _lingua franca_ here
>
> "Rimifon" <webm...@fengyun.org> wrote in message
> news:op.u9jrm...@zhoufeng.web...
> > ֵܰһˣWindowsһBugUbuntuܺãװmiredo֮ʹFirefoxhttp://ipv6.google.com
>
MP
"vasanth" <vas...@discussions.microsoft.com> wrote in message
news:A4453F50-FBDB-4C00...@microsoft.com...