At Erion we have been using IPv6 for many years. This includes using Vista with IPv6 since the early betas of Vista. We have had very few problems. Non of the problems we have experienced have been related to faults in the IPv6 stack.
The article doesn't provide enough detail to be able to analyse the alleged problems with Vista and IPv6. However, I suspect that they are not really problems with Vista or IPv6. As another comment has observed the author is 24 orders-of-magnitude out in the difference between the number of IPv4 addresses and the number of IPv6 addresses. This does not instill confidence in the accuracy of the rest of the article.
Regarding the printer problems, it is extremely unlikely that these are caused by IPv6. As any IT administrator knows there are many reasons why printing can go wrong. If the corruption was caused by IPv6 then it wouldn't just affect printing, it would affect all other network services too.
The ICMP issue described in the article does not make sense. ICMPv6 is IPv6's version of ICMP. It carries out the functions that ICMP carries out in IPv4 plus many new functions only found in IPv6. Applications interface to ICMP (and IP) using the socket API. The way in which applications use the socket API is largely the same for IPv4 and IPv6. Not only this but the socket API is almost identical across all operating systems supporting IPv6, not just Vista. This means that ICMP errors are exposed to applications through the socket API. It is hard to understand what the author means here.
I hope my comments above make it clear why I suspect that the conclusions drawn in the article are wrong.
At Erion we have a lot of experience of implementing IPv6. We have found that IPv6 is reliable and stable across many platforms. Indeed, it is in widespread use around the world. We have found that problems with IPv6 are more often to do with misconfiguration of naming services, routing and transition mechanisms than anything to do with IPv6 itself. We always recommend that anyone interested in implementing IPv6 undertakes IPv6 training. For further information see http://www.ipv6training.com/ and http://www.ipv6consultancy.com./ On the subject of IPv6 and Vista I gave a recent presentation at SambaXP on this subject. You can find that at http://www.ipv6consultancy.com/ipv6blog/?p=8.
Personally, I am very pleased that Vista and Windows Server 2008 (Longhorn) support IPv6 as their default stack. We have many clients who are keen to implement IPv6 but have held back due to the limitations in IPv6 support in Windows operating systems. I suspect that the release of Windows Server 2008 will increase the usage of IPv6 in two very different ways. Firstly, organisations who are not interested in IPv6 will implement it as a side-effect of implementing Windows Server 2008. Secondly, organisations who are keen to use IPv6 but have been held back by the lack of IPv6 support in AD will be able to move ahead with IPv6 AD support in Windows Server 2008.
Slashdot Mirror
Personally, I am very pleased that Vista and Windows Server 2008 (Longhorn) support IPv6 as their default stack. We have many clients who are keen to implement IPv6 but have held back due to the limitations in IPv6 support in Windows operating systems. I suspect that the release of Windows Server 2008 will increase the usage of IPv6 in two very different ways. Firstly, organisations who are not interested in IPv6 will implement it as a side-effect of implementing Windows Server 2008. Secondly, organisations who are keen to use IPv6 but have been held back by the lack of IPv6 support in AD will be able to move ahead with IPv6 AD support in Windows Server 2008.