Timeline for Windows 10 is not using my IPv6 address by default
Current License: CC BY-SA 3.0
18 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 15, 2018 at 6:31 | answer | added | ab. | timeline score: 3 | |
| Dec 12, 2016 at 16:36 | comment | added | TJJ | Windows 10 took a stupid step towards IPv6. You cannot run updates on an IPv6-only network. This was working perfectly under Windows 7. But Windows 10 can only reach the update server by IPv4. | |
| Jan 17, 2016 at 12:41 | comment | added | Lee Ballard | @Daniel B Which FAQ are you referring too? Running latest versions of chrome on Windows 7 and Windows 8.1 machines in the same network with the same latency and they work fine. | |
| Jan 17, 2016 at 12:29 | comment | added | Daniel B | As you can clearly see, your connection’s latency with IPv6 is much higher. The FAQ page explains how this affects IPv6 usability with modern browsers. Is it the same on your other computers? | |
| Jan 17, 2016 at 12:23 | history | edited | Lee Ballard | CC BY-SA 3.0 |
added 732 characters in body
|
| Nov 17, 2015 at 14:34 | comment | added | doenoe | @Lee Did you try disabling IPv4 in the network center for the used NIC? | |
| Nov 17, 2015 at 14:28 | comment | added | Lektonic | @Lee Perhaps it is a DNS configuration problem? | |
| Nov 17, 2015 at 13:52 | history | edited | Lee Ballard | CC BY-SA 3.0 |
added 145 characters in body
|
| Nov 6, 2015 at 14:39 | comment | added | Lee Ballard | @Ramhound the problem is the behavior is not the same. I have 1 windows 10 machine and it's the only one with a problem. I just updated my question to say that upgrading my router made the issue go away, but that says to me there is something new in Win 10 that makes it more picky about IPv6. | |
| Nov 6, 2015 at 14:24 | comment | added | Ramhound | @Lee - If you are getting the same behavior, on both machines, that tells me its a server configuration problem. Windows has supported IPv6 out of the box since Windows 7 I believe. | |
| Nov 6, 2015 at 14:21 | history | edited | Lee Ballard | CC BY-SA 3.0 |
added 373 characters in body
|
| Oct 17, 2015 at 1:26 | history | edited | Lee Ballard | CC BY-SA 3.0 |
added 429 characters in body
|
| Oct 17, 2015 at 1:24 | comment | added | Lee Ballard | I see the same thing on the windows 10 machine that does not work and the windows 8.1 machine that does work | |
| Oct 17, 2015 at 1:17 | comment | added | Lee Ballard | This issue is when I go to web that supports IPv6 and IPv4 with the same hostname (www.sixxs.net, www.kame.net) I land on the IPv4 site and not the IPv6 site like is supposed to happen. | |
| Oct 9, 2015 at 19:52 | comment | added | EBGreen | I think it is prefixpolicies not prefixpolicy | |
| Oct 9, 2015 at 19:27 | comment | added | grawity_u1686 |
I'm curious what is the output of netsh interface ipv6 show prefixpolicy?
|
|
| Oct 9, 2015 at 19:19 | comment | added | EBGreen | I'm curious what issue this is causing for you? | |
| Oct 9, 2015 at 19:16 | history | asked | Lee Ballard | CC BY-SA 3.0 |