Windows XP and Server 2003 share the same network stack (or at least major portions of it) which has some experimental IPv6 support, but not enough to use in production. Certainly not as a server. A few of the limitations:
- no DNS resolving over IPv6
- no IPv6 firewall
- not all applications use IPv6
- you can't configure addresses manually (important for servers)
- no DHCPv6 support
- No good IPv6 support in IIS
Especially because of the missing DNS resolving over IPv6 you will not be able to run a IPv6-only Windows XP or Server 2003 machine. I have run Windows XP in an 'almost-IPv6-only' environment. If you provide a local DNS resolver that speaks IPv4 then you can get basic web browsing to work.
But as far as I am concerned it's not worth the trouble...
Ya, you are right. Even i had figured it out. Anyway thanks a lot. It is very difficult to find any sort of formal documentation on IPV6 on Win XP. – code rider – 2011-09-06T11:46:10.147
1Windows XP and 2003 allow manual IPv6 address and route configuration via
netsh interface ipv6
starting with XPSP2 (andipv6
in earlier versions). I even have XP configured as an IPv6 router to Tunnelbroker. DNS servers can be added as well, but I haven't tested IPv6-only resolving. – user1686 – 2011-09-25T23:22:28.053