Yes if you're using Gateway AntiVirus (GAV); which I'm not. As my next e-mail stated, it was a permissions problem with the root D: drive. The WSUS directory is in the root of D: drive and NETWORK SERVICE needs atleast Read/list directory privs.
Andrew
"BigEd" <eamrein[ at ]fujitecamerica.com> wrote in message news:%23EX7Ou9vHHA.4568[ at ]TK2MSFTNGP03.phx.gbl...
[Quoted Text] > Search on Sonicwall with WSUS. There is a some configuration that needs to > be done to support HTTP 1.1 range protocol headers, or something to that > effect. Been awhile... :-} > > "Andrew" <Andrew[ at ]discussions.microsoft.com> wrote in message > news:64ED5751-58E1-4ECF-9187-A03FD83B0B19[ at ]microsoft.com... >> Yes the company has a Sonicwall Pro 2040. Which doesn't block any >> outbound >> traffic or the corresponding returing traffic. >> >> WSUS 2.0 worked fine on my other machine; no changes have been made to >> the >> firewall. >> >> Can you provide any more information? >> >> "BigEd" wrote: >> >>> No proxy server, but maybe a firewall? >>> Sounds like problem supporting http 1.1 protocol... >>> >>> "Andrew" <Andrew[ at ]discussions.microsoft.com> wrote in message >>> news:1BFCAD2F-478C-45D4-9178-12DAF8CA64C8[ at ]microsoft.com... >>> > Ok I've done a clean install of WSUS 3.0 on a Clean install of W2K3 >>> > Standard >>> > x64 SP2 box. >>> > >>> > WSUS Syncronized without any problems with MS, however it will not >>> > download >>> > any of the updates that have been approved for install. I checked the >>> > event >>> > log and find this error: >>> > >>> > EventID: 364, Source: Windows Server Update >>> > >>> > Content file download failed. Reason: Access is denied. (Exception >>> > from >>> > HRESULT: 0x80070005 (E_ACCESSDENIED)) Source File: >>> > /msdownload/update/v3-19990518/cabpool/windowsserver2003-kb929123-x86-enu_1dc5f603959926665ddd3a8a7493ad509078e2ed.exe >>> > Destination File: >>> > d:\WSUS\WsusContent\ED\1DC5F603959926665DDD3A8A7493AD509078E2ED.exe. >>> > >>> > I looked on eventid.net and everyone there is stating it's a >>> > permissions >>> > problem. I've tried the recommended changes to the directory >>> > security, >>> > but >>> > with no luck. I've even gone as far as giving "everyone" full >>> > permissions >>> > to >>> > the WSUS directories. >>> > >>> > Any ideas? FYI there's no proxy server. >>> >>> >>> > >
|