Certain updates wont download if using Express installs

Discussion in 'Update Services' started by Maineiac15, Aug 19, 2005.

  1. Maineiac15

    Maineiac15 Guest

    Under Synchronization options if I choose to "download express installation
    files" certain updates fail to download. Example is the "Update for Windows
    XP KB894391".
    In the event log I get this:
    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.
    Source File:
    /msdownload/update/v5/psf/windowsxp-kb894391-x86-enu_8688ce96afb860ad159a0943de9a3929ff8f1196.psf
    Destination File:
    d:\WSUS\WsusContent\96\8688CE96AFB860AD159A0943DE9A3929FF8F1196.psf.

    I'm sure this is something simple but have search all over and cannot find
    what I need to do.
     
    Maineiac15, Aug 19, 2005
    #1
    1. Advertisements

  2. This "Range Protocol Header" issue is well known and has been discussed
    several times.

    If you do a search on this newsgroup for "Range Protocol Header" or "HTTP
    v1.1" you'll probably find several of them.

    This is caused by a deficiency in your proxy/firewall that does not fully
    implement the HTTP v1.1 protocol.

    If you're using a newer Sonicwall product, there may be an advanced
    configuration to enable the Range Protocol Headers. If you're using an older
    Sonicwall product, you might want to look at upgrading to one that fully
    supports the protocol.

    If you're using another product, please share the details of what you're
    using, because almost every instance has been related to the Sonicwall
    product, and we really don't have any useful empirical data about issue with
    other products.

    The possible solutions are:

    (1) Upgrade the proxy/firewall to one that fully supports the protocol.

    (2) Bypass the proxy server entirely.

    (3) Use the Server Diagnostic Tool to place BITS into foreground mode,
    effectively working around the requirement for Range Protocol Headers;
    however, be aware of the potential implications on your network by enabling
    WSUS to download Gigabytes of content in BITS foreground mode.

    To place BITS in foreground mode:
    WSUSDebugTool.exe /Tool:SetBitsForeground
     
    Lawrence Garvin, Aug 19, 2005
    #2
    1. Advertisements

  3. Maineiac15

    Maineiac15 Guest

    Thanks for the reply.

    We have a Raptor firewall. I have talked with Symantec and bypassed the
    proxy all together and this still doesn't work. Raptor logs show "connection
    reset by peer" which is the same thing as before we bypassed the proxy.

    I figured I would check out what SonicWall owners were doing to solve the
    problem but when I do the searches you mentioned I don't find anything
    pertaining to this problem. I'll keep searching but any more ideas would be
    appreciated.
     
    Maineiac15, Aug 30, 2005
    #3
  4. Maineiac15

    Maineiac15 Guest

    I guess this is a dead issue because support is telling me our version of
    Raptor (6.5)is to old and basically EOL when it comes to fixing what seems to
    be a flaw in the product. Looks like the only way to solve this is to
    upgrade to a new firewall.

    Thanks for trying
     
    Maineiac15, Aug 30, 2005
    #4
  5. The SonicWall users basically have two options available to them:

    The newer SonicWall systems have an option to "enable" RPH buried in an
    advanced configuration screen. See the thread "WSUS and SonicWall" posted a
    couple of weeks ago for additional details.

    The older SonicWall system users have no other option than to run BITS in
    foreground mode (thus bypassing the need for RPH). To do this, download and
    install the WSUS Server Diagnostic Tool, and run 'wsusdebugtool
    /tool:setforegroundmode'

    The problem with the Symantec (Raptor) product is that I don't think you can
    'bypass' the proxy as it's integrated into the firewall package. However,
    I've not yet encountered anybody else reporting issues with the Symantec
    Enterprise Firewall (aka Raptor), but that could simply be a function of the
    number of users actually using it.
     
    Lawrence Garvin, Aug 30, 2005
    #5
  6. Oh.. yeah... the v6.5 product probably doesn't even have support for any
    HTTP v1.1 functionality. :)

    Definitely consider upgrading the package to the newest version of Symantec
    Enterprise Firewall.
     
    Lawrence Garvin, Aug 30, 2005
    #6
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.