Prev: Error Code: WindowsUpdate_8020002E
Next: Error 0x800704DD and kb910341
From: sepl on 24 Jan 2009 00:08
Anybody else encountering problems with Windows Update since 22 Jan 2009.

Attempting to perform Windows Updates results in the 0x80072EFF error or the
site just times out.

Trying a tracert to update.microsoft.com times out somewhere after it gets
to the msn.net routers. Here's the output from tracert (origin IP masked):

C:\>tracert update.microsoft.com

Tracing route to update.microsoft.com.nsatc.net [65.55.184.93]
over a maximum of 30 hops:

1 8 ms <10 ms <10 ms 192.168.1.2
2 * 32 ms 59 ms
ABTS-KK-Dynamic-00*.**.***.122.airtelbroadband.i
n [122.***.**.*]
3 30 ms 30 ms 29 ms
ABTS-KK-Static-***.**.**.122.airtelbroadband.in
[122.***.**.***]
4 51 ms 31 ms 33 ms
ABTS-KK-Static-009.32.166.122.airtelbroadband.in
[122.166.32.9]
5 29 ms 30 ms 29 ms 122.175.255.29
6 38 ms 39 ms 39 ms 125.21.167.74
7 277 ms 270 ms 271 ms 59.145.11.170
8 270 ms 269 ms 285 ms ge-1-3-0-0.nyc-64cb-1a.ntwk.msn.net
[207.46.33.2
9]
9 279 ms 278 ms 275 ms ge-4-0-0-0.bl2-64c-1b.ntwk.msn.net
[207.46.41.22
]
10 279 ms 279 ms 279 ms 10.22.112.121
11 276 ms 277 ms 277 ms 10.22.112.70
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

From: MowGreen [MVP] on 24 Jan 2009 16:39
That's not an uncommon tracert result. Since there are 'certain
elements' who would dearly love to bring down the update servers, one
can not tracert to them. My system can still update and tracert to
update.microsoft.com yields the same result as your system does.

0x80072EFF ERROR_INTERNET_CONNECTION_Reset

The error may be caused by network congestion or a network problem. It
may even be related to the worm that's taken control of over 9 million
systems, Conficker.B also known as “Downadup.”
4 or 5 years ago the issue stemmed from script blocking. If there is no
script blocking going on, and this would include the prohibition of
ActiveX running via a router hardware firewall, then I suspect the issue
is network related.

MowGreen [MVP 2003-2009]
===============
*-343-* FDNY
Never Forgotten
===============


sepl wrote:

> Anybody else encountering problems with Windows Update since 22 Jan 2009.
>
> Attempting to perform Windows Updates results in the 0x80072EFF error or the
> site just times out.
>
> Trying a tracert to update.microsoft.com times out somewhere after it gets
> to the msn.net routers. Here's the output from tracert (origin IP masked):
>
> C:\>tracert update.microsoft.com
>
> Tracing route to update.microsoft.com.nsatc.net [65.55.184.93]
> over a maximum of 30 hops:
>
> 1 8 ms <10 ms <10 ms 192.168.1.2
> 2 * 32 ms 59 ms
> ABTS-KK-Dynamic-00*.**.***.122.airtelbroadband.i
> n [122.***.**.*]
> 3 30 ms 30 ms 29 ms
> ABTS-KK-Static-***.**.**.122.airtelbroadband.in
> [122.***.**.***]
> 4 51 ms 31 ms 33 ms
> ABTS-KK-Static-009.32.166.122.airtelbroadband.in
> [122.166.32.9]
> 5 29 ms 30 ms 29 ms 122.175.255.29
> 6 38 ms 39 ms 39 ms 125.21.167.74
> 7 277 ms 270 ms 271 ms 59.145.11.170
> 8 270 ms 269 ms 285 ms ge-1-3-0-0.nyc-64cb-1a.ntwk.msn.net
> [207.46.33.2
> 9]
> 9 279 ms 278 ms 275 ms ge-4-0-0-0.bl2-64c-1b.ntwk.msn.net
> [207.46.41.22
> ]
> 10 279 ms 279 ms 279 ms 10.22.112.121
> 11 276 ms 277 ms 277 ms 10.22.112.70
> 12 * * * Request timed out.
> 13 * * * Request timed out.
> 14 * * * Request timed out.
> 15 * * * Request timed out.
> 16 * * * Request timed out.
> 17 * * * Request timed out.
> 18 * * * Request timed out.
> 19 * * * Request timed out.
> 20 * * * Request timed out.
> 21 * * * Request timed out.
> 22 * * * Request timed out.
> 23 * * * Request timed out.
> 24 * * * Request timed out.
> 25 * * * Request timed out.
> 26 * * * Request timed out.
> 27 * * * Request timed out.
> 28 * * * Request timed out.
> 29 * * * Request timed out.
> 30 * * * Request timed out.
>
> Trace complete.
>
From: sepl on 24 Jan 2009 18:34
Thanks for the reply. However, there is no firewall restriction on ActiveX,
no script blocking at the firewall and update.microsoft.com is in IE's
Trusted Sites list at the Default Level.

I have tried this from three different networks/connections and Windows
Update and tracert consistently fail on all of them, where they were working
fine until a couple or three days ago.

I wonder if this is an India only problem, since several other colleagues in
India on other ISP's and networks have confirmed that they too cannot get
Windows Update to run. As you indicated, network congestion might be a
problem.

I am trying to get a new W2K3 Ent. x64 SP2 box upto the current patch level
for the past 3 days now, with no success.

Are there any alternate Microsoft Windows Update sites or a site where we
can get a list of patches with the download URL's? I can have colleagues
in the USA, where Windows Update seems to be working fine, download the
patches and send them across to us.
..
"MowGreen [MVP]" wrote:

> That's not an uncommon tracert result. Since there are 'certain
> elements' who would dearly love to bring down the update servers, one
> can not tracert to them. My system can still update and tracert to
> update.microsoft.com yields the same result as your system does.
>
> 0x80072EFF ERROR_INTERNET_CONNECTION_Reset
>
> The error may be caused by network congestion or a network problem. It
> may even be related to the worm that's taken control of over 9 million
> systems, Conficker.B also known as “Downadup.”
> 4 or 5 years ago the issue stemmed from script blocking. If there is no
> script blocking going on, and this would include the prohibition of
> ActiveX running via a router hardware firewall, then I suspect the issue
> is network related.
>
> MowGreen [MVP 2003-2009]
> ===============
> *-343-* FDNY
> Never Forgotten
> ===============
>
>
> sepl wrote:
>
> > Anybody else encountering problems with Windows Update since 22 Jan 2009.
> >
> > Attempting to perform Windows Updates results in the 0x80072EFF error or the
> > site just times out.
> >
> > Trying a tracert to update.microsoft.com times out somewhere after it gets
> > to the msn.net routers. Here's the output from tracert (origin IP masked):
> >
> > C:\>tracert update.microsoft.com
> >
> > Tracing route to update.microsoft.com.nsatc.net [65.55.184.93]
> > over a maximum of 30 hops:
> >
> > 1 8 ms <10 ms <10 ms 192.168.1.2
> > 2 * 32 ms 59 ms
> > ABTS-KK-Dynamic-00*.**.***.122.airtelbroadband.i
> > n [122.***.**.*]
> > 3 30 ms 30 ms 29 ms
> > ABTS-KK-Static-***.**.**.122.airtelbroadband.in
> > [122.***.**.***]
> > 4 51 ms 31 ms 33 ms
> > ABTS-KK-Static-009.32.166.122.airtelbroadband.in
> > [122.166.32.9]
> > 5 29 ms 30 ms 29 ms 122.175.255.29
> > 6 38 ms 39 ms 39 ms 125.21.167.74
> > 7 277 ms 270 ms 271 ms 59.145.11.170
> > 8 270 ms 269 ms 285 ms ge-1-3-0-0.nyc-64cb-1a.ntwk.msn.net
> > [207.46.33.2
> > 9]
> > 9 279 ms 278 ms 275 ms ge-4-0-0-0.bl2-64c-1b.ntwk.msn.net
> > [207.46.41.22
> > ]
> > 10 279 ms 279 ms 279 ms 10.22.112.121
> > 11 276 ms 277 ms 277 ms 10.22.112.70
> > 12 * * * Request timed out.
> > 13 * * * Request timed out.
> > 14 * * * Request timed out.
> > 15 * * * Request timed out.
> > 16 * * * Request timed out.
> > 17 * * * Request timed out.
> > 18 * * * Request timed out.
> > 19 * * * Request timed out.
> > 20 * * * Request timed out.
> > 21 * * * Request timed out.
> > 22 * * * Request timed out.
> > 23 * * * Request timed out.
> > 24 * * * Request timed out.
> > 25 * * * Request timed out.
> > 26 * * * Request timed out.
> > 27 * * * Request timed out.
> > 28 * * * Request timed out.
> > 29 * * * Request timed out.
> > 30 * * * Request timed out.
> >
> > Trace complete.
> >
>
From: MowGreen [MVP] on 26 Jan 2009 17:16
First, try another attempt at accessing Windows Update. When that fails,
close IE. Then open the WindowsUpdate.log located in %windir%.
Scroll all the way to the bottom for the most recent entries.
Post at least the last 50 or so lines of the log into your reply, please.
Next, flush the dns cache from a Command Prompt
ipconfig /flushdns

Close Command Prompt.
Delete the temporary Internet Files from within Control Panel > Internet
Options.

Reboot the system and try to access Windows Updates once more.
All update content for each month is listed here:

Description of Software Update Services and Windows Server Update
Services changes in content for 2009
http://support.microsoft.com/kb/894199

2008 Description of Software Update Services and Windows Server Update
Services changes in content for 2007
http://support.microsoft.com/kb/961825

There are links under the content that will lead you to where you can
download the content from.
EX: Tuesday, January 13, 2009
New security content:

* MS09-001: Security Update for Windows (KB958687)
If you click the forwarding link you'll be taken to the Security
bulletin for that update -
http://www.microsoft.com/technet/security/bulletin/ms09-001.mspx
Just click the link for Windows Server 2003 x64 Edition and Windows
Server 2003 x64 Edition Service Pack 2 to be taken to the download page.

Most updates are available at the Microsoft Update Catalog, too:
http://catalog.update.microsoft.com/v7/site/Home.aspx

HTH,

MowGreen [MVP 2003-2009]
===============
*-343-* FDNY
Never Forgotten
===============



sepl wrote:
> Thanks for the reply. However, there is no firewall restriction on ActiveX,
> no script blocking at the firewall and update.microsoft.com is in IE's
> Trusted Sites list at the Default Level.
>
> I have tried this from three different networks/connections and Windows
> Update and tracert consistently fail on all of them, where they were working
> fine until a couple or three days ago.
>
> I wonder if this is an India only problem, since several other colleagues in
> India on other ISP's and networks have confirmed that they too cannot get
> Windows Update to run. As you indicated, network congestion might be a
> problem.
>
> I am trying to get a new W2K3 Ent. x64 SP2 box upto the current patch level
> for the past 3 days now, with no success.
>
> Are there any alternate Microsoft Windows Update sites or a site where we
> can get a list of patches with the download URL's? I can have colleagues
> in the USA, where Windows Update seems to be working fine, download the
> patches and send them across to us.
> .
> "MowGreen [MVP]" wrote:
>
>
>>That's not an uncommon tracert result. Since there are 'certain
>>elements' who would dearly love to bring down the update servers, one
>>can not tracert to them. My system can still update and tracert to
>>update.microsoft.com yields the same result as your system does.
>>
>>0x80072EFF ERROR_INTERNET_CONNECTION_Reset
>>
>>The error may be caused by network congestion or a network problem. It
>>may even be related to the worm that's taken control of over 9 million
>>systems, Conficker.B also known as “Downadup.”
>>4 or 5 years ago the issue stemmed from script blocking. If there is no
>>script blocking going on, and this would include the prohibition of
>>ActiveX running via a router hardware firewall, then I suspect the issue
>>is network related.
>>
>>MowGreen [MVP 2003-2009]
>>===============
>> *-343-* FDNY
>>Never Forgotten
>>===============
>>
>>
>>sepl wrote:
>>
>>
>>>Anybody else encountering problems with Windows Update since 22 Jan 2009.
>>>
>>>Attempting to perform Windows Updates results in the 0x80072EFF error or the
>>>site just times out.
>>>
>>>Trying a tracert to update.microsoft.com times out somewhere after it gets
>>>to the msn.net routers. Here's the output from tracert (origin IP masked):
>>>
>>>C:\>tracert update.microsoft.com
>>>
>>>Tracing route to update.microsoft.com.nsatc.net [65.55.184.93]
>>>over a maximum of 30 hops:
>>>
>>> 1 8 ms <10 ms <10 ms 192.168.1.2
>>> 2 * 32 ms 59 ms
>>>ABTS-KK-Dynamic-00*.**.***.122.airtelbroadband.i
>>>n [122.***.**.*]
>>> 3 30 ms 30 ms 29 ms
>>>ABTS-KK-Static-***.**.**.122.airtelbroadband.in
>>> [122.***.**.***]
>>> 4 51 ms 31 ms 33 ms
>>>ABTS-KK-Static-009.32.166.122.airtelbroadband.in
>>> [122.166.32.9]
>>> 5 29 ms 30 ms 29 ms 122.175.255.29
>>> 6 38 ms 39 ms 39 ms 125.21.167.74
>>> 7 277 ms 270 ms 271 ms 59.145.11.170
>>> 8 270 ms 269 ms 285 ms ge-1-3-0-0.nyc-64cb-1a.ntwk.msn.net
>>>[207.46.33.2
>>>9]
>>> 9 279 ms 278 ms 275 ms ge-4-0-0-0.bl2-64c-1b.ntwk.msn.net
>>>[207.46.41.22
>>>]
>>> 10 279 ms 279 ms 279 ms 10.22.112.121
>>> 11 276 ms 277 ms 277 ms 10.22.112.70
>>> 12 * * * Request timed out.
>>> 13 * * * Request timed out.
>>> 14 * * * Request timed out.
>>> 15 * * * Request timed out.
>>> 16 * * * Request timed out.
>>> 17 * * * Request timed out.
>>> 18 * * * Request timed out.
>>> 19 * * * Request timed out.
>>> 20 * * * Request timed out.
>>> 21 * * * Request timed out.
>>> 22 * * * Request timed out.
>>> 23 * * * Request timed out.
>>> 24 * * * Request timed out.
>>> 25 * * * Request timed out.
>>> 26 * * * Request timed out.
>>> 27 * * * Request timed out.
>>> 28 * * * Request timed out.
>>> 29 * * * Request timed out.
>>> 30 * * * Request timed out.
>>>
>>>Trace complete.
>>>
>>
From: sepl on 27 Jan 2009 01:48
Thanks for the help. Tried as suggested. Now, I get Error Number: 0x80072EE2.

As requested here are the last 50 lines of the WindowsUpdate.log file:

2009-01-27 09:38:59+0530 840 3b4 SendRequest failed with hr = 80072ee2.
Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
2009-01-27 09:38:59+0530 840 3b4 WinHttp: SendRequestUsingProxy failed for
<http://www.download.windowsupdate.com/msdownload/update/software/dflt/2008/07/1403130_cbc59647efb607ffeefbd18fab291344865a617b.cab>. error 0x80072ee2
2009-01-27 09:38:59+0530 840 3b4 WinHttp:
SendRequestToServerForFileInformation MakeRequest failed. error 0x80072ee2
2009-01-27 09:38:59+0530 840 3b4 WinHttp:
SendRequestToServerForFileInformation failed with 0x80072ee2
2009-01-27 09:38:59+0530 840 3b4 WinHttp: ShouldFileBeDownloaded failed
with 0x80072ee2
2009-01-27 09:40:59+0530 840 3b4 Send failed with hr = 80072ee2.
2009-01-27 09:40:59+0530 840 3b4 SendRequest failed with hr = 80072ee2.
Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
2009-01-27 09:40:59+0530 840 3b4 WinHttp: SendRequestUsingProxy failed for
<http://www.download.windowsupdate.com/msdownload/update/software/dflt/2008/07/1403130_cbc59647efb607ffeefbd18fab291344865a617b.cab>. error 0x80072ee2
2009-01-27 09:40:59+0530 840 3b4 WinHttp:
SendRequestToServerForFileInformation MakeRequest failed. error 0x80072ee2
2009-01-27 09:40:59+0530 840 3b4 WinHttp:
SendRequestToServerForFileInformation failed with 0x80072ee2
2009-01-27 09:40:59+0530 840 3b4 WinHttp: ShouldFileBeDownloaded failed
with 0x80072ee2
2009-01-27 09:43:00+0530 840 3b4 Send failed with hr = 80072ee2.
2009-01-27 09:43:00+0530 840 3b4 SendRequest failed with hr = 80072ee2.
Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
2009-01-27 09:43:00+0530 840 3b4 WinHttp: SendRequestUsingProxy failed for
<http://www.download.windowsupdate.com/msdownload/update/software/dflt/2008/07/1403130_cbc59647efb607ffeefbd18fab291344865a617b.cab>. error 0x80072ee2
2009-01-27 09:43:00+0530 840 3b4 WinHttp:
SendRequestToServerForFileInformation MakeRequest failed. error 0x80072ee2
2009-01-27 09:43:00+0530 840 3b4 WinHttp:
SendRequestToServerForFileInformation failed with 0x80072ee2
2009-01-27 09:43:00+0530 840 3b4 WinHttp: ShouldFileBeDownloaded failed
with 0x80072ee2
2009-01-27 09:45:00+0530 840 3b4 Send failed with hr = 80072ee2.
2009-01-27 09:45:00+0530 840 3b4 SendRequest failed with hr = 80072ee2.
Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
2009-01-27 09:45:00+0530 840 3b4 WinHttp: SendRequestUsingProxy failed for
<http://www.download.windowsupdate.com/msdownload/update/software/dflt/2008/07/1403130_cbc59647efb607ffeefbd18fab291344865a617b.cab>. error 0x80072ee2
2009-01-27 09:45:00+0530 840 3b4 WinHttp:
SendRequestToServerForFileInformation MakeRequest failed. error 0x80072ee2
2009-01-27 09:45:00+0530 840 3b4 WinHttp:
SendRequestToServerForFileInformation failed with 0x80072ee2
2009-01-27 09:45:00+0530 840 3b4 WinHttp: ShouldFileBeDownloaded failed
with 0x80072ee2
2009-01-27 09:45:00+0530 840 3b4 ECP: Failed to download cab file from
http://www.download.windowsupdate.com/msdownload/update/software/dflt/2008/07/1403130_cbc59647efb607ffeefbd18fab291344865a617b.cab with error 0x80072ee2
2009-01-27 09:45:00+0530 840 3b4 ECP: This roundtrip contained some
optimized updates which failed. New Update count = 23, Old Count = 30
2009-01-27 09:45:01+0530 840 3b4 Sync of Updates: 0x8024402f
2009-01-27 09:45:01+0530 840 3b4 WU client failed Searching for update with
error 0x8024402f
2009-01-27 09:45:01+0530 840 36c Search Callback Failed, hr is 0x8024402f
2009-01-27 09:45:01+0530 840 36c Setting next AU detection timeout to
2009-01-27 09:15:01
2009-01-27 09:45:01+0530 840 36c Unable to detect updates for more than 48
hours
2009-01-27 09:45:01+0530 840 36c Setting AU scheduled install time to
2009-01-27 09:30:00
2009-01-27 09:45:01+0530 840 36c WU client calls back to search call
AutomaticUpdates with code Call failed and error 0x8024402f
2009-01-27 09:45:01+0530 840 36c WU client completed and deleted call
{B7DA535A-6528-4610-A62E-E0EDE6B3A3B2}
2009-01-27 09:45:01+0530 840 3b4 REPORT EVENT:
{20403249-852B-4056-BB26-FA5326791FF6} 2009-01-27
09:36:50+0530 1 148 101 {D67661EB-2423-451D-BF5D-13199E37DF28} 0 80072ee2 SelfUpdate Failure Software
Synchronization Error: Agent failed detecting with reason: 0x80072ee2
2009-01-27 09:45:01+0530 840 3b4 CEventCacheFile::Init failed = 80070003.
2009-01-27 09:45:01+0530 840 3b4 Successfully initialized event uploader
for server 9482f4b4-e343-43b6-b170-9a65bc822c77.
2009-01-27 09:45:01+0530 840 3b4 CEventCacheFile::Init failed = 80070003.
2009-01-27 09:45:01+0530 840 3b4 CEventCacheFile::Init failed = 80070003.
2009-01-27 09:45:01+0530 840 3b4 Created new event cache file at
C:\WINDOWS\SoftwareDistribution\EventCache\{04653FED-8F22-4A15-94BE-47161932B826}.bin for writing.
2009-01-27 09:45:06+0530 840 3b4 REPORT EVENT:
{4B409098-200A-442D-B3CE-6B027C0DB870} 2009-01-27
09:45:01+0530 1 148 101 {00000000-0000-0000-0000-000000000000} 0 8024402f AutomaticUpdates Failure Software
Synchronization Error: Agent failed detecting with reason: 0x8024402f
2009-01-27 09:45:06+0530 840 3b4 REPORT EVENT:
{519AA1CB-1A40-427C-A94C-A3E72FE89740} 2009-01-27
09:45:01+0530 1 149 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Failure Software
Synchronization Unable to Connect: Windows is unable to connect to the
automatic updates service and therefore cannot download and install updates
according to the set schedule. Windows will continue to try to establish a
connection.
2009-01-27 09:45:06+0530 840 3b4 Successfully initialized event uploader
for server (null).
2009-01-27 09:46:46:546 2268 8d4 Misc =========== Logging initialized
(build: 7.2.6001.788, tz: +0530) ===========
2009-01-27 09:46:46:546 2268 8d4 Misc = Process: C:\Program Files
(x86)\Internet Explorer\iexplore.exe
2009-01-27 09:46:46:546 2268 8d4 Misc = Module:
C:\WINDOWS\SysWOW64\wuweb.dll
2009-01-27 09:46:46:546 2268 8d4 WUWeb FATAL: CreateObject for
Microsoft.Update.AgentInfo failed: error 0x800401f3
2009-01-27 09:46:46+0530 840 3c0 WU client succeeds
CClientCallRecorder::EnumerateService
2009-01-27 09:47:39:125 2268 8d4 Misc Validating signature for
C:\WINDOWS\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\muv3wuredir.cab:
2009-01-27 09:47:39:265 2268 8d4 Misc Microsoft signed: Yes
2009-01-27 09:49:25:140 2612 a30 Misc =========== Logging initialized
(build: 7.2.6001.788, tz: +0530) ===========
2009-01-27 09:49:25:140 2612 a30 Misc = Process: C:\Program Files
(x86)\Internet Explorer\IEXPLORE.EXE
2009-01-27 09:49:25:140 2612 a30 Misc = Module:
C:\WINDOWS\SysWOW64\wuweb.dll
2009-01-27 09:49:25:140 2612 a30 WUWeb FATAL: CreateObject for
Microsoft.Update.AgentInfo failed: error 0x800401f3
2009-01-27 09:49:25+0530 840 384 WU client succeeds
CClientCallRecorder::EnumerateService
2009-01-27 09:49:36:328 2612 a30 Misc Validating signature for
C:\WINDOWS\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\muv3wuredir.cab:
2009-01-27 09:49:36:390 2612 a30 Misc Microsoft signed: Yes


"MowGreen [MVP]" wrote:

> First, try another attempt at accessing Windows Update. When that fails,
> close IE. Then open the WindowsUpdate.log located in %windir%.
> Scroll all the way to the bottom for the most recent entries.
> Post at least the last 50 or so lines of the log into your reply, please.
> Next, flush the dns cache from a Command Prompt
> ipconfig /flushdns
>
> Close Command Prompt.
> Delete the temporary Internet Files from within Control Panel > Internet
> Options.
>
> Reboot the system and try to access Windows Updates once more.
> All update content for each month is listed here:
>
> Description of Software Update Services and Windows Server Update
> Services changes in content for 2009
> http://support.microsoft.com/kb/894199
>
> 2008 Description of Software Update Services and Windows Server Update
> Services changes in content for 2007
> http://support.microsoft.com/kb/961825
>
> There are links under the content that will lead you to where you can
> download the content from.
> EX: Tuesday, January 13, 2009
> New security content:
>
> * MS09-001: Security Update for Windows (KB958687)
> If you click the forwarding link you'll be taken to the Security
> bulletin for that update -
> http://www.microsoft.com/technet/security/bulletin/ms09-001.mspx
> Just click the link for Windows Server 2003 x64 Edition and Windows
> Server 2003 x64 Edition Service Pack 2 to be taken to the download page.
>
> Most updates are available at the Microsoft Update Catalog, too:
> http://catalog.update.microsoft.com/v7/site/Home.aspx
>
> HTH,
>
> MowGreen [MVP 2003-2009]
> ===============
> *-343-* FDNY
> Never Forgotten
> ===============
>
>
>
> sepl wrote:
> > Thanks for the reply. However, there is no firewall restriction on ActiveX,
> > no script blocking at the firewall and update.microsoft.com is in IE's
> > Trusted Sites list at the Default Level.
> >
> > I have tried this from three different networks/connections and Windows
> > Update and tracert consistently fail on all of them, where they were working
> > fine until a couple or three days ago.
> >
> > I wonder if this is an India only problem, since several other colleagues in
> > India on other ISP's and networks have confirmed that they too cannot get
> > Windows Update to run. As you indicated, network congestion might be a
> > problem.
> >
> > I am trying to get a new W2K3 Ent. x64 SP2 box upto the current patch level
> > for the past 3 days now, with no success.
> >
> > Are there any alternate Microsoft Windows Update sites or a site where we
> > can get a list of patches with the download URL's? I can have colleagues
> > in the USA, where Windows Update seems to be working fine, download the
> > patches and send them across to us.
> > .
> > "MowGreen [MVP]" wrote:
> >
> >
> >>That's not an uncommon tracert result. Since there are 'certain
> >>elements' who would dearly love to bring down the update servers, one
> >>can not tracert to them. My system can still update and tracert to
> >>update.microsoft.com yields the same result as your system does.
> >>
> >>0x80072EFF ERROR_INTERNET_CONNECTION_Reset
> >>
> >>The error may be caused by network congestion or a network problem. It
> >>may even be related to the worm that's taken control of over 9 million
> >>systems, Conficker.B also known as “Downadup.”
> >>4 or 5 years ago the issue stemmed from script blocking. If there is no
> >>script blocking going on, and this would include the prohibition of
> >>ActiveX running via a router hardware firewall, then I suspect the issue
> >>is network related.
> >>
> >>MowGreen [MVP 2003-2009]
> >>===============
> >> *-343-* FDNY
> >>Never Forgotten
> >>===============
> >>
> >>
> >>sepl wrote:
> >>
> >>
> >>>Anybody else encountering problems with Windows Update since 22 Jan 2009.
> >>>
> >>>Attempting to perform Windows Updates results in the 0x80072EFF error or the
> >>>site just times out.
> >>>
> >>>Trying a tracert to update.microsoft.com times out somewhere after it gets
> >>>to the msn.net routers. Here's the output from tracert (origin IP masked):
> >>>
> >>>C:\>tracert update.microsoft.com
> >>>
> >>>Tracing route to update.microsoft.com.nsatc.net [65.55.184.93]
> >>>over a maximum of 30 hops:
> >>>
> >>> 1 8 ms <10 ms <10 ms 192.168.1.2
> >>> 2 * 32 ms 59 ms
> >>>ABTS-KK-Dynamic-00*.**.***.122.airtelbroadband.i
> >>>n [122.***.**.*]
> >>> 3 30 ms 30 ms 29 ms
> >>>ABTS-KK-Static-***.**.**.122.airtelbroadband.in
> >>> [122.***.**.***]
> >>> 4 51 ms 31 ms 33 ms
> >>>ABTS-KK-Static-009.32.166.122.airtelbroadband.in
> >>> [122.166.32.9]
> >>> 5 29 ms 30 ms 29 ms 122.175.255.29
> >>> 6 38 ms 39 ms 39 ms 125.21.167.74
> >>> 7 277 ms 270 ms 271 ms 59.145.11.170
> >>> 8 270 ms 269 ms 285 ms ge-1-3-0-0.nyc-64cb-1a.ntwk.msn.net
> >>>[207.46.33.2
> >>>9]
> >>> 9 279 ms 278 ms 275 ms ge-4-0-0-0.bl2-64c-1b.ntwk.msn.net
> >>>[207.46.41.22
> >>>]
> >>> 10 279 ms 279 ms 279 ms 10.22.112.121
> >>> 11 276 ms 277 ms 277 ms 10.22.112.70
> >>> 12 * * * Request timed out.
> >>> 13 * * * Request timed out.
> >>> 14 * * * Request timed out.
> >>> 15 * * * Request timed out.
> >>> 16 * * * Request timed out.
> >>> 17 * * * Request timed out.
> >>> 18 * * * Request timed out.
> >>> 19 * * * Request timed out.
> >>> 20 * * * Request timed out.
> >>> 21 * * * Request timed out.
> >>> 22 * * * Request timed out.
> >>> 23 * * * Request timed out.
> >>> 24 * * * Request timed out.
> >>> 25 * * * Request timed out.
> >>> 26 * * * Request timed out.
> >>> 27 * * * Request timed out.
> >>> 28 * * * Request timed out.
> >>> 29 * * * Request timed out.
> >>> 30 * * * Request timed out.
> >>>
> >>>Trace complete.
> >>>
> >>
>
 |  Next  |  Last
Pages: 1 2
Prev: Error Code: WindowsUpdate_8020002E
Next: Error 0x800704DD and kb910341