Slashdot Mirror
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.'"
Disable this whole "internet" thing altogether. It's been full of security problems for Windows ever since someone dreamed it up.
My turnips listen for the soft cry of your love
"2^32 unique addresses ought to be enough for anybody."
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...
MS has a blog for this sort of thing. Sean Siler promised to answer questions and provide help on issues pertaining to this via an email list I'm on. http://blogs.technet.com/ipv6/ ... Anyhow, those parties with IPv6 issues, I bet ya a HUGE portion of them are using NAT...
Infiltrated dot Net
I think you responded to the wrong story, but you're amazingly on topic anyway.
Vista adoption is going to increase - it's a sad fact, and I can't see anyone denying it. Therefore IPv6 is going to experience stunted uptake from this blow.
The one benefit I can see is that anybody who really does see worthwhile benefits in adopting IPv6 will say "bugger M$, there are hundreds of Open Source solutions that support this without issue out of the box". Maybe this could have a positive impact on OSS uptake in the long-term.
Meta will eat itself
I think they should scoop the one out of BSD UNIX.
Hell, it worked for them pretty good LAST time..
Do daemons dream of electric sleep()?
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
Right. Can you do me a favour and "easily remove" kernel modules from any OS please. Meanwhile, removing the IPv6 stack from Windows is trivial -- just a few clicks of the mouse, and you're there.
I'm not a Windows apologist by any stretch of the imagination, but this blatant misinformation needs to be corrected.
The entire IP stack of Vista/Longhorn has been reimplemented. IPv6 is kind of an "add-on" to the networking code in XP, but in Vista, IPv4 and IPv6 are implemented in a unified stack.
Just sayin', the behavior is going to be different, and having some bugs to shake out is really no surprise.
Well, apparently, you only have to fool the majority of people for a little while.
IPv6 FAQ
c es\Tcpip6\Parameters\DisabledComponents
Q. How do I disable IPv6 in Windows Vista and Windows Server 2008?
A. Unlike Windows XP and Windows Server 2003, IPv6 in Windows Vista and Windows Server 2008 cannot be uninstalled. However, you can disable IPv6 in Windows Vista and Windows Server 2008 by doing one of the following:
- In the Network Connections folder, obtain properties on all of your connections and adapters and clear the check box next to the Internet Protocol version 6 (TCP/IPv6) component in the list under This connection uses the following items.
This method disables IPv6 on your LAN interfaces and connections, but does not disable IPv6 on tunnel interfaces or the IPv6 loopback interface.
- Add the following registry value (DWORD type) set to 0xFF:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servi
This method disables IPv6 on all your LAN interfaces, connections, and tunnel interfaces but does not disable the IPv6 loopback interface. You must restart the computer for this registry value to take effect.
For additional information about the DisabledComponents registry value, see Configuring IPv6 with Windows Vista.
If you disable IPv6, you will not be able to use Windows Meeting Space or any application that relies on the Windows Peer-to-Peer Networking platform or the Teredo transition technology.
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
Or, if you're not an idiot, you just add "blacklist ipv6" to /etc/modprobe.d/blacklist.
Microsoft's IPv6 stack is extremely secure, more so than the Linux one. It achieves this by simply not talking to anything.
How many people can read hex if only you and dead people can read hex?