Windows Server 2008 updates error 80072EFD

First off, I have uninstalled all anti-malware and firewal software, enable
windows firewall, checked proxy settings, entered the windows update sites to
the trusted sites. We have 3 2008 servers all experiencing this same
problem. Our client systems (Vista and XP) can update fine. We do not use
WSUS and have verified Group Policies. Have verified that the neccessary
ports are enabled on our router and firewall.

So basicly I have done what every article on the internet says to do about
this error code while using windows updates and none work. I am on edge
about this.

Time to do some diagnosis? You could try using an HTTP tracer
such as Fiddler2 but that will cause some new symptoms about
certificates due to its proxy.

You already imply that there are portions of your network path
where a blockage may occur, e.g. in your router and firewall.
So, what diagnostics can you use in them to help refine your
symptom description?...


http://support.microsoft.com/kb/838177

(Live Search for
0x80072EFD server update proxy firewall site:support.microsoft.com language:en

Otherwise do a full packet trace and protocol analysis.
FWIW I would use netcap and Ethereal for that.

Besides what you suggested, Robert, I can't see the original post and
replies to see what else was suggested. However I do know that this error is
based on something blocking Windows Updates site URLs or the traffic.Maybe
this article will help.
http://windowshelp.microsoft.com/Win...71033.mspxAlso, I see that the original poster, Jeff, mentioned he uninstalled AV,antispyware and a firewall solution, but enabled the Windows Firewall. Why?Disable the Windows Firewall. Curious, what other type of firewall wasinstalled that was uninstalled? If ZoneAlarm, it leaves DLL and SYS filesthat are still invoked at startup and run in the background preventingcommunications.Jeff also mentioned the following:"Have verified that the neccessary ports are enabled on our router andfirewall."What ports are they? What type of firewall/router is it? The only real portsthat Windows Update uses are 80 & 443.Also, look also in the registry for the HKLM and HKCU Run key to see what isstarting up that may also be blocking communications

I kept getting this same error on my server 2008 servers when I first
installed the 2008 OS.

To fix it I went into internet explorer/tools/internet
options/connections/lan settings and unchecked Automatically detect settings.

I also added http://download.windowsupdate.com to the safe sites.

This server wasnt on the domain yet, and behind ISA2006, a webfilter, and a
bandwidth shaping box.

This has been solved for server 2008 R2. Do this:
Start>All Programs>Windows Update
When the update window opens, look under the "Check for Updates" button and click on "Check online for updates from Windows Update"
Then you will be prompted to actually install windows update and that works. Once that is installed, windows udpate worked fine for me. I believe this is because it our company purchased the OS from Dell along with a PowerEdge, rather than an actual version of 2008 sr2 64bit yopu would purchase separately from a store or non-OEM reseller.

Anyway, hope this helps.

Then I got error 80200010 and had to clear BITS like this in a dos prompt or bat file:

net stop bits
net stop wuauserv
Ipconfig /flushdns
cd "Documents and Settings\All Users\Application Data\Microsoft\Network\Downloader"
del qmgr0.dat
del qmgr1.dat
net start bits
net start wuauserv


And it worked so far

Time to do some diagnosis? You could try using an HTTP tracer such as Fiddler2 but that will cause some new symptoms about certificates due to its proxy. You already imply that there are portions of your network path where a blockage may occur, e.g. in your router and firewall. So, what diagnostics can you use in them to help refine your symptom description?

Messenger,

I implied no such thing. Why did you bother posting at all? You are not helpful. The problem is with BITS (Background intelligent Transfer Service) in Windows. ITS A WINDOWS PROBLEM!