IPv6 usage with Win2k8 server OS   

Hi,
  I'm trying to use IPv6 support given by default with Windows Server
2008 but i'm getting only LINKLOCAL address with % sign. For Inst:
fe80::78e3:3123:8c5c:246f%11

My question is when i try to ping machine the above IPv6 machine
witout %11 value then it fails to reach the destination. Could anyone
explain why i need to use that as well as which IPv6 address TYPE i
need to use in some places where they ask for IPv6 address(where i
supplied public IPv4 previously)?

Moreover, how to set the static IPv6 address in this OS?

Thanks in advance,
Arjun

date: Tue, 3 Jun 2008 04:14:09 -0700 (PDT)   author:   unknown

RE: IPv6 usage with Win2k8 server OS   

Arjun --

fe80:: address prefix is link-local ipv6 only, and almost always requires an 
interface identifier to be able to ping these addresses. 

Some additional info from the MS IPV6 FAQ:  
http://www.microsoft.com/technet/network/ipv6/ipv6faq.mspx

 The IPv6 protocol for Windows Server 2003 and Windows XP with SP1 or later 
includes an IPv6-capable Ping.exe tool. The new Ping sends ICMPv6 Echo 
Request messages to the specified destination and displays round-trip time 
statistics on the corresponding Echo Reply messages. To ping using an IPv6 
address, the Ping.exe syntax is the following: ping IPv6Address [%ZoneID]

The ZoneID option specifies the scope or zone of the destination for the 
ICMPv6 Echo Request messages. For link-local addresses, the zone identifier 
(ID) is typically equal to the interface index, as displayed in the output of 
the netsh interface ipv6 show interface command. For site-local addresses, 
the zone ID is equal to the site number, as displayed in the output of the 
netsh interface ipv6 show interface level=verbose command. If multiple sites 
are not being used, a zone ID for site-local addresses is not required. You 
can also obtain the zone ID from the display of the Ipconfig command. The 
number after the "%" character in the display of an address indicates the 
zone ID. The zone ID is not needed when the destination is a global address.

For example, to send Echo Request messages to the link-local address 
FE80::260:97FF:FE02:6EA5 using zone ID 4 (the interface index of an installed 
Ethernet adapter), use the following command:

ping fe80::260:97ff:fe02:6ea5%4

Because the zone ID is locally defined, the zone ID of the sending host may 
not be the same as the zone ID of the destination host for the same zone. For 
example, for Host A and Host B connected the same link, Host A's zone ID for 
the link is 4 and Host B's zone ID for the link is 3. When Host A pings Host 
B, the zone ID used in the ping command is 4. When Host B pings Host A, the 
zone ID used in the ping command is 3.


There are also examples of using manually configured addresses for IPv6 here:

http://technet.microsoft.com/en-us/library/bb878102.aspx

I would recommend that you look into one of the "transition" technologies to 
allow for IPv6 connectivity.  One method is to setup an IPv6 host with a 
tunnel (using one of many IPv6 tunnel brokers like he.net or sixxs.net), then 
you can setup that host to provide full IPv6 connectivity for your local lan 
segment.  Some tunnel brokers will even give you a full /48 prefix IPv6 
subnet.  

Good Luck.

--Dave

date: Fri, 6 Jun 2008 05:26:08 -0700   author:   GadgetDave