I can. So that at least means HE has the route for your /64 pointed through your tunnel. It may also mean that WS2008 is routing packets, but I'm not sure since that NIC is still "inside" your machine. It all depends on the proto stack framework of windows, etc.
I can also ping your tunnel side interface, BTW.
Thank you.
The WS2008 machine is definitely routing the packets, and now the Win 2000 Server machine is also as I just finished setting that one up (including RRAS). I also had to set up a v6v4 tunnel between the WS2008 and Win2000 Server machines (my network is IPv4!

) and now I'm able to ping through with IPv6.
You should be able to ping my Win 2000 Server now, if you would please:
2001:470:1f05:a85::7
Now, though, there's a new wrinkle in this routing scenario. When I go to the following web site and use their IPv4/IPv6 connection Checker, they detect my IPv4 NIC address correctly, but the IPv6 address detected is my tunnel endpoint [2001:470:1f04:a85::2] instead of my NIC address [2001:470:1f05:a85::6]:
http://www.ipv6forum.com/I'm wondering if I should enable some more things on the tunnel. For example, forwarding is already enabled, but maybe I should also set advertise=enabled nud=enabled routerdiscovery=enabled. Or, is this due to something else...? It seems to me that if I get this configured correctly, the NIC address should be the detected source address of the connection.
What do you think?