nanog mailing list archives
Re: WIndows Updates Fail Via IPv6
From: "Morgan A. Miskell" <morgan.miskell () caro net>
Date: Mon, 12 Nov 2018 11:30:56 -0500
Not to beat a dead horse, but could the problem be so simple? I have tons of dual-stacked machines that have updated forever without issue, so I assume they update via IPV4.
That being said, I've not packet sniffed any of the update stuff in a while but if the DNS is any indication then dual-stacked machines can update via IPV4 while IPV6 ONLY machines will likely fail since the DNS shows IPV4 only....
host windowsupdate.microsoft.comwindowsupdate.microsoft.com is an alias for windowsupdate.redir.update.microsoft.com.nsatc.net. windowsupdate.redir.update.microsoft.com.nsatc.net is an alias for redir.update.microsoft.com.nsatc.net.
redir.update.microsoft.com.nsatc.net has address 157.56.77.153 On 11/11/2018 01:35 PM, Jared Mauch wrote:
On Nov 11, 2018, at 8:45 AM, Mark Tinka <mark.tinka () seacom mu> wrote: On 11/Nov/18 14:02, Chris Knipe wrote:Also no problems here with IPv6 and Windows Updates...The issue is affecting (and has affected) quite a few folk: https://social.technet.microsoft.com/Forums/windowsserver/en-US/a9b1b537-ad27-4718-821b-57ef33174974/windows-update-fails-if-ipv6-is-enabled?forum=w8itpronetworking https://social.technet.microsoft.com/Forums/office/en-US/16e7aa06-9b90-48f8-8370-76c2329b93a8/windows-update-ipv6?forum=ws2016 https://answers.microsoft.com/en-us/windows/forum/all/windows-8-pro-windows-update-fails-if-ipv6-is/7ebdac22-6675-402b-ad43-e3fa8450659d It occurs to me that this, could, perhaps be CDN specific. I'm currently not in Johannesburg, but last time I checked, the majority of Windows updates were being handled by Akamai. Perhaps this is where the issue could be, although we have got local IPv6 peering with Akamai and don't generally have issues with it. I'll dig deeper into how Akamai may be involved when I get back home.Let me know if you see anything related to Akamai. Looking at these threads I don’t see anything really obvious and some are much older posts. - Jared
-- Morgan A. Miskell CaroNet Data Centers 704-643-8330 x206 ---------------------------------------------------------------------------- The information contained in this e-mail is confidential and is intended only for the named recipient(s). If you are not the intended recipient you must not copy, distribute, or take any action or reliance on it. If you have received this e-mail in error, please notify the sender. Any unauthorized disclosure of the information contained in this e-mail is strictly prohibited. ----------------------------------------------------------------------------
Current thread:
- WIndows Updates Fail Via IPv6 Mark Tinka (Nov 11)
- Re: WIndows Updates Fail Via IPv6 Daniel Corbe (Nov 11)
- Re: WIndows Updates Fail Via IPv6 Chris Knipe (Nov 11)
- Re: WIndows Updates Fail Via IPv6 Mark Tinka (Nov 11)
- Re: WIndows Updates Fail Via IPv6 Jared Mauch (Nov 11)
- Re: WIndows Updates Fail Via IPv6 Mark Tinka (Nov 12)
- Re: WIndows Updates Fail Via IPv6 Morgan A. Miskell (Nov 12)
- Re: WIndows Updates Fail Via IPv6 Chris Knipe (Nov 11)
- Re: WIndows Updates Fail Via IPv6 Daniel Corbe (Nov 11)
- Re: WIndows Updates Fail Via IPv6 Mark Tinka (Nov 12)
- Re: WIndows Updates Fail Via IPv6 Mikael Abrahamsson (Nov 12)
- Re: WIndows Updates Fail Via IPv6 Mark Tinka (Nov 13)
- Re: WIndows Updates Fail Via IPv6 John Von Essen (Nov 12)
- Re: WIndows Updates Fail Via IPv6 Mark Andrews (Nov 12)
- Re: WIndows Updates Fail Via IPv6 Bjørn Mork (Nov 13)
- Re: WIndows Updates Fail Via IPv6 Mark Tinka (Nov 12)
- <Possible follow-ups>
- Re: WIndows Updates Fail Via IPv6 Willy MANGA (Nov 11)