Vista Not Playing Well With IPv6 232
netbuzz writes in to note that some early adopters of Microsoft Vista are reporting problems with Vista's implementation of IPv6. An example:"'We are seeing a number of applications that are IP-based that do not like the addressing scheme of IPv6,' says one user. 'We will send a print job to an IP-based printer, and the print job becomes corrupted. We're seeing this with Window's Vista machines. When IPv6 is installed, this happens without fail. As soon as we remove IPv6, all of our printer functions return to normal.'"
Re:Simple solution. (Score:5, Interesting)
Anyway, why is this screwing anything up? My understanding on Linux/OSX is that enabling IPv6 doesn't change anything about the way IPv4 applications function, despite using a different addressing sceme. Why would this be any different for Vista? This is indicative of a layering problem...
I am NOT surprised, given that... (Score:3, Interesting)
It may just be my long memory seeing repetitive mistakes by the software giant, but it seems like ALL of M$ network implementations seem to suffer in the early going until they manage to buy cheat or steal for good code to solve their own implementation messes...
Thoughts anyone?
Re:Obligatory (Score:4, Interesting)
Re:Very funny, but... (Score:5, Interesting)
Blame Vista, or applications? (Score:5, Interesting)
So I have to wonder, is this really an issue with Vista's IPV6, is it an issue with the driver writers, or is it a minor issue with Vista's implementation of the layer that supports IP printers?
The article seems to indicate "we turned off IPV6 and then it started working". Well that tells us a little, but it's hardly time to start blaming the IPV6 stack. There's quite a few different components that could be responsible. I had problems with Firefox on Ubuntu on my network, and was able to track it down to a faulty implementation of DNS on my DSL modem only under IPV6.
Order of magnitude more orders of magnitude (Score:4, Interesting)
Note to authors: If you don't understand what words mean, don't use them.
Re:And this is news because? (Score:4, Interesting)
I dunno. How about, it's news because it indicates that Microsoft's product testing is less than industrial strength?
Oh, is that all? (Score:4, Interesting)
We found this on Beta and tried to talk to MS, after being passed from piller to post and jerked round (we frankly have real work to get on with) we gave up. We tested with the full release, and, well, until we have time its just barred from the business.
Re:Microsoft's IPv6 stack (Score:3, Interesting)
I dare to ask, "who the hell cares"? (Score:3, Interesting)
Will it really be important some day for every physical item in my possession to have a unique address and an RFID tag?
Do sysadmins at big corporations really WANT every one of their machines to have an address that is uniquely addressable from anywhere on the Internet? Will this help to solve issues such as VPN'ing behind a firewall, etc.?
An honest question.
Let's clear a few things up (ok, a rant) (Score:2, Interesting)
It seems like there are a few things that are causing confusion. Also, I want to rant about ipv6 adoption.
First of all, this looks like it's probably the printer's (or printer driver's) fault and not Microsoft's.
Second, about ipv6 in general...
It hurts me a bit to see people saying "Just disable ipv6 whenever you install vista." I think MS is doing a great thing by enabling ipv6 by default. If the instructions to support desk people, or some "best practice" becomes to disable ipv6 right away, ipv6 will take *another* 10 years to enter the mainstream.
This is pretty bad considering that ipv4 addresses are running out in the next 5 years.
It is exactly these kind of firmware/driver bugs (not having ipv6 support in a network appliance should now be considered a bug) that need to be flushed out before the internet is thrust into ipv6 adoption when the address space runs out.
IPv6 *does* solve problems, and it *will* be the primary mode of accessing the internet for consumers. Shaking out bugs by actually using ipv6 is necessary.
So, MS should *not* be berated because of this. This particular instance is not their fault, and they're doing the right thing by putting ipv6 up front in vista.
Lastly, I'd like to say that deploying ipv6 in the home is actually ridiculously easy. I have a tunnel through hurricane electric [tunnelbroker.net]. Stateless autoconfig, which happens with ipv6 by default, assigns addresses without a dhcp server, and allows things to run right away.
IPv6 and OS support is not the problem. Application and network hardware vendors *have* to get with the program and start to support ipv6 in a very real way.