Vista Not Playing Well With IPv6
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.'"
What if you're trying to migrate to IPv6 but still have "classic" IPv4 devices on the network?
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...
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?
...Open Source isn't the only answer -- but it's almost always a better value than the alternatives...
The really cool thing with that is, there are so many adresses that networms cannot jump to machines via the usage of random ip adresses and you cannot scan entire subnets anymore. It's like to try fishing in an ocean with a gun. Maybe you'll never hit any crature in the big water.
I've got Vista, an IP based printer, and even IPV6 via a tunnel broker. I've had no problems with printing or any other network applications.
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.
AccountKiller
Note to authors: If you don't understand what words mean, don't use them.
[100% ISO 646 Compliant]
SVM, ERGO MONSTRO.
I dunno. How about, it's news because it indicates that Microsoft's product testing is less than industrial strength?
You can't see ANYTHING from a car, You've got to get out of the goddamned contraption and walk...Edward Abbey
Vista crashes our main network switches here. We did not have a requirement for Vista, so we've banished it until we do an upgrade on firmware project, which will be done on a if/when required by the business (HP pro curve switches).
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.
We`re all equal