Today I first installed a clean Windows 2003 server system as I wanted to fully get and document the process of how it all works.
I was a bit annoyed that at first my network adapter was not working, but soon I realized this would be a good opportunity to really see the IPV6 status on a clean system. What I did was install a Microsoft Loopback adapter and then install the IPV6 protocol. The first is not important to document here, the second might be.
Installing IPV6 on a windows network adapter is quite easy. Just open the network adapter you want to install in Control Panel -> Network Connections and then go to Properties. You'll see a button 'Install...' which is what you choose. Then select 'Protocol' and choose 'Add'. Select 'Microsoft TCP/IP version 6' and choose 'Ok'. That should do the trick and it seems you can only install it for all adapters at the same time, not for one adapter only.
So now I had one Microsoft Loopback Adapter cleanly installed and only the IPV6 protocol installed. Then I checked the configuration of the adapter with the command 'ipconfig /all' that showed me all tcp/ip information available. This is what I got (left out the non IPV6 information (added some information later:
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Loopback Adapter
Physical Address. . . . . . . . . : 02-00-4C-4F-4F-50
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 0.0.0.0
Subnet Mask . . . . . . . . . . . : 0.0.0.0
Looked up on the Internet here and this is a so called 'local link address' and the fe80 is standard Microsoft. The last part is related to the physical adress (see above).
IP Address. . . . . . . . . . . . : fe80::4cff:fe4f:4f50%5
Default Gateway . . . . . . . . . :
DHCP Server . . . . . . . . . . . : 0.0.0.0
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
Tunnel adapter Teredo Tunneling Pseudo-Interface:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : FF-FF-FF-FF-FF-FF-FF-FF
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : fe80::ffff:ffff:fffd%4
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Disabled
Well, I know a bit where the IP address fe80::4cff:fe4f:4f50%5 from, but not fully. Will come back to that later. What amazed me where thd dns server addresses that I got. I also know a bit where the Teredo stuff comes from, but also not fully, so better also check that out later.
After this i installed the real adapter and got this:
Ethernet adapter Local Area Connection 2:
Connection-specific DNS Suffix . : megaheights.net
Description . . . . . . . . . . . : VMware Accelerated AMD PCNet Adapter
Physical Address. . . . . . . . . : 00-0C-29-00-AF-B0
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 172.16.2.51
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : 2001:5c0:1500:8e00:20c:29ff:fe00:afb0
IP Address. . . . . . . . . . . . : 2001:5c0:9eb7:1:20c:29ff:fe00:afb0
IP Address. . . . . . . . . . . . : ::20c:29ff:fe00:afb0
IP Address. . . . . . . . . . . . : 2001:5c0:1508:1200:20c:29ff:fe00:afb0
IP Address. . . . . . . . . . . . : fe80::20c:29ff:fe00:afb0%5
Default Gateway . . . . . . . . . : 172.16.2.254
fe80::219:66ff:fe5b:6eb1%5
fe80::219:66ff:fe5b:708b%5
DHCP Server . . . . . . . . . . . : 172.16.2.2
DNS Servers . . . . . . . . . . . : 172.16.2.2
172.16.2.1
172.16.2.254
fec0:0:0:ffff::1%2
fec0:0:0:ffff::2%2
fec0:0:0:ffff::3%2
The IPV address of the Loopback adapter was then fe80::4cff:fe4f:4f50%4, which means it was still the same except th %5 changed into %4. The dns servers stayed the same.
Actually now I should start looking for what it all means and put it here, but it's quite late, so I'll leave that for a later time.