Vista - Cannot ping with IPv6

Hi,

I'm running Windows Vista Ultimate with IPv6 and Teredo installed and
enabled, but it seems I

am unable to ping any hosts on the local network (which consists of one
other XP SP3 machine)

or internet. Both computers are connected to a standard router (Dell
TrueMobile 2300, which is

IPv4 only I believe). Still, an IPv4 router should not matter considering
Teredo should be

enabled on both computers.

Running ipconfig returns the following:

Vista
----------------------------------------------------------------

Ethernet adapter Loopback:

Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::504b:717d:6870:54b6%12
Autoconfiguration IPv4 Address. . : 169.254.84.182
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
IPv6 Address. . . . . . . . . . . : 2001:0:d5c7:a2ca:0:f2f6:adfd:5d0
IPv6 Address. . . . . . . . . . . : 2001:0:d5c7:a2ca:0:f2f6:adfd:5d0e
Link-local IPv6 Address . . . . . : fe80::5efe:169.254.84.182%9
Link-local IPv6 Address . . . . . : fe80::5efe:192.168.2.4%9
Link-local IPv6 Address . . . . . : fe80::5efe:192.168.2.6%9
Link-local IPv6 Address . . . . . : fe80::ffff:ffff:fffd%9
Link-local IPv6 Address . . . . . : fe80::504b:717d:6870:54b6%9
Link-local IPv6 Address . . . . . : fe80::80da:92d4:339a:6712%9
IPv4 Address. . . . . . . . . . . : 192.168.2.6
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1

Tunnel adapter Local Area Connection* 6:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Tunnel adapter Local Area Connection* 9:

Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::5efe:192.168.2.6%11
Default Gateway . . . . . . . . . :

Tunnel adapter Local Area Connection* 11:

Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::5efe:169.254.84.182%14
Default Gateway . . . . . . . . . :
----------------------------------------------------------------

XP SP3
----------------------------------------------------------------
Ethernet adapter Wireless Network Connection:

Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 192.168.2.4
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : fe80::ffff:ffff:fffd%4
Default Gateway . . . . . . . . . :

Tunnel adapter Automatic Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : fe80::5efe:192.168.2.4%2
Default Gateway . . . . . . . . . :
----------------------------------------------------------------

Here is what some of the ping commands returned. (I do not have much of an
understanding of

IPv6, so I may be giving a bad address to ping some of the time.)

Vista pinging XP
----------------------------------------------------------------
PS C:\Users\Alex> ping fe80::ffff:ffff:fffd%4

Pinging fe80::ffff:ffff:fffd%4 with 32 bytes of data:

PING: transmit failed, error code 1231.
PING: transmit failed, error code 1231.
PING: transmit failed, error code 1231.
PING: transmit failed, error code 1231.

Ping statistics for fe80::ffff:ffff:fffd%4:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
----------------------------------------------------------------
PS C:\Users\Alex> ping fe80::ffff:ffff:fffd

Pinging fe80::ffff:ffff:fffd from fe80::ffff:ffff:fffd%9 with 32 bytes of
data:

Reply from fe80::ffff:ffff:fffd: time<1ms
Reply from fe80::ffff:ffff:fffd: time<1ms
Reply from fe80::ffff:ffff:fffd: time<1ms
Reply from fe80::ffff:ffff:fffd: time<1ms

Ping statistics for fe80::ffff:ffff:fffd:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
----------------------------------------------------------------
PS C:\Users\Alex> ping fe80::5efe:192.168.2.4%2

Pinging fe80::5efe:192.168.2.4%2 with 32 bytes of data:

PING: transmit failed, error code 1231.
PING: transmit failed, error code 1231.
PING: transmit failed, error code 1231.
PING: transmit failed, error code 1231.

Ping statistics for fe80::5efe:192.168.2.4%2:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
----------------------------------------------------------------
PS C:\Users\Alex> ping fe80::5efe:192.168.2.4

Pinging fe80::5efe:192.168.2.4 from fe80::5efe:192.168.2.4%9 with 32 bytes
of data:

Reply from fe80::5efe:192.168.2.4: time<1ms
Reply from fe80::5efe:192.168.2.4: time<1ms
Reply from fe80::5efe:192.168.2.4: time<1ms
Reply from fe80::5efe:192.168.2.4: time<1ms

Ping statistics for fe80::5efe:192.168.2.4:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
----------------------------------------------------------------


XP pinging Vista
----------------------------------------------------------------
PS C:\Documents and Settings\Alex> ping 2001:0:d5c7:a2ca:0:f2f6:adfd:5d0

Pinging 2001:0:d5c7:a2ca:0:f2f6:adfd:5d0 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 2001:0:d5c7:a2ca:0:f2f6:adfd:5d0:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
----------------------------------------------------------------
(same for 2001:0:d5c7:a2ca:0:f2f6:adfd:5d0e)
----------------------------------------------------------------
PS C:\Documents and Settings\Alex> ping fe80::5efe:169.254.84.182%9

Pinging fe80::5efe:169.254.84.182%9 with 32 bytes of data:

IP parameter problem.
IP parameter problem.
IP parameter problem.
IP parameter problem.

Ping statistics for fe80::5efe:169.254.84.182%9:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
----------------------------------------------------------------
PS C:\Documents and Settings\Alex> ping fe80::5efe:169.254.84.182

Pinging fe80::5efe:169.254.84.182 with 32 bytes of data:

Destination net unreachable.
Destination net unreachable.
Destination net unreachable.
Destination net unreachable.

Ping statistics for fe80::5efe:169.254.84.182:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
----------------------------------------------------------------

Pings to all other addresses with/without zone IDs have similar results.

A ping to any of the sites listed on http://www.ipv6.org/v6-www.html from
Vista returns:

Ping request could not find host www.6bone.net. Please check the name and
try again.

And on XP something like:

----------------------------------------------------------------
Pinging www.kame.net [2001:200:0:8002:203:47ff:fea5:3085] with 32 bytes of
data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 2001:200:0:8002:203:47ff:fea5:3085:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
----------------------------------------------------------------

No surprise, I also can't view any of the sites from IE7/Firefox.
I'll be glad to provide any other info that is needed to diagnose the problem.

Thanks.

Full ipconfig (ipconfig /all), in case it helps:


Windows IP Configuration

Host Name . . . . . . . . . . . . : Alex-PC
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Loopback:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Loopback Adapter
Physical Address. . . . . . . . . : 02-00-4C-4F-4F-50
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::504b:717d:6870:54b6%12(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.84.182(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 251789388
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 . . . . . . . . . . . : Intel(R) 82566DC Gigabit Platform LAN
Connect
Physical Address. . . . . . . . . : 00-19-D1-1B-87-C8
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . :
2001:0:d5c7:a2ca:0:f2f6:adfd:5d0(Preferred)
IPv6 Address. . . . . . . . . . . :
2001:0:d5c7:a2ca:0:f2f6:adfd:5d0e(Preferred)
Link-local IPv6 Address . . . . . : fe80::5efe:169.254.84.182%9(Preferred)
Link-local IPv6 Address . . . . . : fe80::5efe:192.168.2.4%9(Preferred)
Link-local IPv6 Address . . . . . : fe80::5efe:192.168.2.6%9(Preferred)
Link-local IPv6 Address . . . . . : fe80::ffff:ffff:fffd%9(Preferred)
Link-local IPv6 Address . . . . . : fe80::504b:717d:6870:54b6%9(Preferred)
Link-local IPv6 Address . . . . . : fe80::80da:92d4:339a:6712%9(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.2.6(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : 27 May 2008 11:58:36
Lease Expires . . . . . . . . . . : 28 May 2008 11:58:35
Default Gateway . . . . . . . . . : 192.168.2.1
DHCP Server . . . . . . . . . . . : 192.168.2.1
DHCPv6 IAID . . . . . . . . . . . : 201333201
DNS Servers . . . . . . . . . . . : 192.168.2.1
194.168.8.100
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Local Area Connection* 6:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 02-00-54-55-4E-01
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 9:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . :
isatap.{ADA0A0F3-9A15-4250-A068-68A6E8DD077C}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::5efe:192.168.2.6%11(Preferred)
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 192.168.2.1
194.168.8.100
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Local Area Connection* 11:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . :
isatap.{9DBFFEF8-52AE-4017-A826-0AA1CF9A3483}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::5efe:169.254.84.182%14(Preferred)
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Disabled

Ok, I've resolve everything on Vista now. I can access several IPv6 websites
(not sure why only a few, but I'm assuming it's simply because of the Teredo
server). On XP I'm having the same problems: Request timed out.

Hi Alex,

So what was your solution?

Aaron


"Alex" wrote:

Firstly I ran (in PowerShell):
netsh interface ipv6 teredo show state

This gave me information on the state of Teredo (which was inactive because
of an error). I re-enabled Teredo using the disable/set commands with the
entrepriseclient option, followed by:
netsh interface ipv6 reset

After a restart (not sure this was necessary) everything seemed to work
fairly well. I could ping IPv6 servers and view IPv6 websites (only some
however, but I believe this limitation is due to the MS Teredo server).

I later found out that it is impossible to get it working on XP with my
network configuration, since my router has a symmetric NAT and the version of
Teredo for XP does not support symmetric NATs (Vista has partial support for
symmetric NATs).

Not sure how common this problem is, but I only found it documented
(inconclusively) on one web page after much searching. Hopefully this
solution will help some of you trying to get IPv6 working on Vista...

Hi All,

IPV6 clients do not connect to ipv6 server under link local NAT Setup,
unless the interface ids (also known as zone id) of the clients and
server are same.

To give more clarity let me put it in an example,

A NAT Server and a client under it

if the NAT client link local address is fe80::ec84:1634:d659:2aba%4
and Server link local address is fe80::211:5bff:fec2:82dc%10


then the client and server cannot communicate with each other since the
interface id is 4 and 10 respectively.

only when the interface ids are same, the machines can ping each
other.

one work around is that client pinging the server with client interface
id
ex: ping fe80::211:5bff:fec2:82dc%4 instead of
fe80::211:5bff:fec2:82dc%10


else client has to disable and enable its network interface 6 times to
equal the interface id of server.


--
lg101
------------------------------------------------------------------------
lg101's Profile: http://forums.techarena.in/member.php?userid=51277
View this thread: http://forums.techarena.in/showthread.php?t=976064

http://forums.techarena.in