So far, I've found three distribution networks, the same ones as from the last post:
1. footprint.net (INCONSISTENT)
2. download.windowsupdate.com.edgesuite.net
3. b1ns.au-msedge.net
As noted, DNS is being used to distribute the load across those networks (and any others).
footprint.net is randomly serving up a bad CAB file or a good CAB file; who knows when that will be fixed.
I haven't tried the other two as much, but aside from research and diagnostics I want to avoid the footprint.net distribution for this file.
In case anyone is interested, one can use a tool like WGET or CURL to force the request for the CAB file to go to one of the other networks.
1. Explicitly specify the Host: header in the request
2. Replace the host in the URL with one of the two other distro network host names
For example, with WGET:
- Code: Select all
wget --server-response --verbose --header="Host: download.windowsupdate.com" "http://b1ns.au-msedge.net/microsoftupdate/v6/wsusscan/wsusscn2.cab"
-OR-
- Code: Select all
wget --server-response --verbose --header="Host: download.windowsupdate.com" "http://download.windowsupdate.com.edgesuite.net/microsoftupdate/v6/wsusscan/wsusscn2.cab"
I have only tried this on Windows machines so far, but WGET and CURL should behave elsewhere, certainly more consistently than the content distribution for wsusscn2.cab. (One could also force the HTTP request down to the IP address level, but I'm not sure of the advantage in this case.)
There is no guarantee this will scale, of course, but waiting for Microsoft to test or fix this issue is an even bigger waste of time.