Updates not downloading

Post by JAStillwell
We just setup WSUS 3.0 on an SBS R2 server. We are not getting any
Content file download failed. Reason: The server does not support the
necessary HTTP protocol. Background Intelligent Transfer Service (BITS)
requires that the server support the Range protocol header.

This is actually a misworded error message.. the "server" referred to in
this message rarely refers to the WSUS Server.

More likely it's being caused by a proxy server, or firewall, in the path
between the WSUS Server and microsoft.com, that does not fully support, or
is not configured to fully support, the HTTP v1.1 protocols -- specifically
the use of the Range Protocol Header.

The most common culprit seen in this scenario are the SonicWall appliances.
There's a buried configuration setting that will enable the protocol
support. A Google Search on this newsgroup
(microsoft.public.windows.server.update_services) for keyword "SonicWall" is
the easiest way to find the necessary remediation.

If not a SonicWall appliance, you might also search on "Range Protocol
Header", which will pull up the other threads related to this issue.

--
Lawrence Garvin, M.S., MCBMSP, MCTS, MCP
Senior Data Architect, APQC, Houston, Texas
Microsoft MVP - Software Distribution (2005-2008)

MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin

JAStillwell

2008-01-06 19:31:01 UTC

Lawrence,

You are right! In the time it took you to answer this question (seemed like
only about 5 minutes...on a Sunday, no less!) I found a reference to the same
information on another blog. I got into the diagnostic portion of the
SonicWALL (http://<SonicWALL IP>/diag.html) and set it to "Enable HTTP
Byte-Range requests with Gateway AV" to correct the issue.

Apparently SonicWALL does not want people to easily reset this setting as it
is in the hidden portion of the SonicWALL config.

Anyway, that fixed the problem! Thanks for your prompt reply!

Jeff

This is actually a misworded error message.. the "server" referred to in
this message rarely refers to the WSUS Server.
More likely it's being caused by a proxy server, or firewall, in the path
between the WSUS Server and microsoft.com, that does not fully support, or
is not configured to fully support, the HTTP v1.1 protocols -- specifically
the use of the Range Protocol Header.
The most common culprit seen in this scenario are the SonicWall appliances.
There's a buried configuration setting that will enable the protocol
support. A Google Search on this newsgroup
(microsoft.public.windows.server.update_services) for keyword "SonicWall" is
the easiest way to find the necessary remediation.
If not a SonicWall appliance, you might also search on "Range Protocol
Header", which will pull up the other threads related to this issue.
--
Lawrence Garvin, M.S., MCBMSP, MCTS, MCP
Senior Data Architect, APQC, Houston, Texas
Microsoft MVP - Software Distribution (2005-2008)
MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin

Winfried Sonntag [MVP]

2008-01-06 19:21:59 UTC

Post by JAStillwell
Can someone explain what we need to do to get WSUS downloading?

This should be help: http://support.microsoft.com/kb/922330

Winfried

--
http://www.microsoft.com/germany/windowsserver2003/technologien/updateservices/default.mspx
http://www.wsuswiki.com/Home

JAStillwell

2008-01-06 19:33:01 UTC

Winifried,

Thanks to you, too! As I just wrote on Lawrence's reply, the SonicWALL
"Enable HTTP Byte-Range requests with Gateway AV" is the culprit.

Thanks for replying so quickly on a Sunday afternoon!

Jeff

Post by JAStillwell
Can someone explain what we need to do to get WSUS downloading?

This should be help: http://support.microsoft.com/kb/922330
Winfried
--
http://www.microsoft.com/germany/windowsserver2003/technologien/updateservices/default.mspx
http://www.wsuswiki.com/Home

Lawrence Garvin [MVP]

2008-01-07 03:51:54 UTC

Post by JAStillwell
Can someone explain what we need to do to get WSUS downloading?

This should be help: http://support.microsoft.com/kb/922330

Hey Winfried.. thanks for the link! I'm glad to see MS finally documented
this in a KB article!

(And, I suppose, were I doing a better job of keeping up with new KB
articles, I would have known this way back when ... it's actually not a
*new* document, given the 922xxx number, or the fact that it reached rev 5.0
last October.)

Winfried Sonntag [MVP]

2008-01-07 08:40:58 UTC

Lawrence Garvin [MVP] schrieb:

Hi Lawrence,

Post by Winfried Sonntag [MVP]
This should be help: http://support.microsoft.com/kb/922330

Hey Winfried.. thanks for the link! I'm glad to see MS finally documented
this in a KB article!

no problem. ;) Its a classic error using wsus. Some things needs time.
We see us in april?

Winfried

--
http://www.microsoft.com/germany/windowsserver2003/technologien/updateservices/default.mspx
http://www.wsuswiki.com/Home

Lawrence Garvin [MVP]

2008-01-09 01:45:21 UTC

Post by Winfried Sonntag [MVP]
This should be help: http://support.microsoft.com/kb/922330

Hey Winfried.. thanks for the link! I'm glad to see MS finally documented
this in a KB article!

no problem. ;) Its a classic error using wsus. Some things needs time.
We see us in april?

I will be there. As soon as the registration site opens up and I get a hotel
confirmation I'm booking my travel.

Winfried Sonntag [MVP]

2008-01-09 19:56:59 UTC

Post by Winfried Sonntag [MVP]
We see us in april?

I will be there. As soon as the registration site opens up and I get a hotel
confirmation I'm booking my travel.

OK, great. ;)

Winfried

--
http://www.microsoft.com/germany/windowsserver2003/technologien/updateservices/default.mspx
http://www.wsuswiki.com/Home

bruheard

2010-02-16 15:16:01 UTC

Solved my issue. Thanks