Quote: Originally Posted by logicearth
If its really that much of a problem why don't you just turn off IPv6?
But now I wonder what problem is this actually causing?
1. Applications are failing to react according to IP address, because the IPv6 address is being presented. Even though the IPv6 address is zero compressed, it is inconsistent in its format, and is not predictable. 192.168.1.x is and I can make several assumptions in my programming, which I cannot in IPv6.
2. I cannot remember 21 IPv6 addresses off the top of my head. I can with the IPv4 because only the last octet changes. The IPv6 addresses have 3 compressed octets, leaving 5. The first fe80 is constant, the other four I ave to try and remember. I could carry around a "translation" card with me everywhere so I can refer to that.
There is more but I won't bore you with the details.
The point of my original post was "What changed to make the IPv6 address be presented instead of IPv4".
You cannot totally turn off IPv6. Yes, I know I can untick it in the connection properties. Indeed, the registry change I presented in my previous response was infact doing that at a lower level. It even says that you would still see the tick on the exact area the you highlighted, but it would not actually be active.
But, again, what I originally wanted to know was, since nothing had changed except the installation of a .NET 4 patch or two on ONE machine, ALL machines EXCEPT the server started presenting IPv6 addresses and I wanted to find out why.
The first step in fixing anything is understanding the problem and what caused the problem. The theory was if I can identify what caused the change to occur I could reverse it and all would be well. At the time I thought that would be a more expedient resolution than re-writing my applications with a lookup table.
I am well aware that evetually IPv6 will replace IPv4 and I have no isse with that. Like I said - All I wanted to know is what changed that made the IPv6 addresses get shown instead IPv4. Things dont magically change by themselves.
The only thing I could identify was the removal of the XP machine, which was replaced with a WIndows 7 machine, because that is when the addresses changed.