Sukender wrote:After weeks struggling with the the problem, I just confirm that "Prefer IPv4 over IPv6" fix from Microsoft (mentioned by Bruce,
http://support.microsoft.com/kb/2533454 ) solves the issue on my computer (Win7 x64). I just hope ticket #505 will solve this issue since I will NOT keep my computer prefer IPv4 for long. This would be too bad dropping FAH just for such a blocking bug.
I'm glad that the current work-around works for you. I expect that Ticket #914 will also work for you. I don't think you understand, though.
There are three steps to fixing this problem -- or rather there are three problems of differencing priority. Classifying all three as a "blocking bug" is inappropriate.
1) Use the "Prefer IPv4 over IPv6" fix from Microsoft or the "disable IPV6" as suggested earlier.
2) Use the fix provided in Ticket #914 (This is expected to be fixed in v7.2.0.)
3) Use the fix proposed in Ticket #505.
Item 1 provides a temporary work-around for the problem and is available now.
Item 2 is expected to provide a permanent fix for the "Core won't download (IPV6)" being discussed in this topic. I can't predict when V7.2.0 will be released, but I expect it to be soon. (Development is already working on
Milestone: v7.2.4Item 3 will provide the V7 client with the ability to contact FAH servers which DO NOT have IPV4 addresses. Currently, all FAH servers DO have IPV4 addresses and I am not aware of any near-term plans to utilize servers which cannot use IPV4. Fixing #505 is beyond the scope of the problem you've reported and it cannot be considered as blocking. Thus it has been reclassified from a defect to an enhancement and set to priority 7 (minor). In other words, development does not consider a short-term fix for that ticket as important and although it will be fixed someday, there are many other problems which will be fixed before work on it begins.