Windows Update inaccessible

  • Thread starter Thread starter John
  • Start date Start date
J

John

For 24 hours I have not been able to run Windows Update. I get a message
that the page is inaccessible because of network diffivulties.

Is this a general experience or is ther something wrong at my end? [XP Pro +
SP1 worksation]
 
Wesley said:
John;

I just got on, no problem.


In
John said:
For 24 hours I have not been able to run Windows Update. I get a
message that the page is inaccessible because of network
diffivulties.

Is this a general experience or is ther something wrong at my end?
[XP Pro + SP1 worksation]
Click to expand...
Click to expand...

There are reports that some users ARE having a problem connecting. Real problem. But not for all.
Suggest people look in their log file. Then see what *Errors* are listed.

Do you have these errors in your log file: 80072EE7 or 801901F7 ?
 
Maurice;

What log file?
Windows Update.log

Where is it located?
C:\WINDOWS

If someone did have these errors in their log file: 80072EE7 or
801901F7
What would that mean?
==========

Would it be one of these????

0x80072EE2
Problem Description:
Unable to access site ERROR # 0x80072EE2

Resolutions:
Customer had Windows Update IP hard coded in their HOSTS file. Removing
entry from the HOSTS file in C:\Winnt\system32\drivers\etc resolved the
problem. Another solution may be to run DNS/Flush.

Entries for the Windows Update site in the HOSTS file are not recommended as
the IP's for the site change often. Beware of "web accelerator"
applications like TweakMASTER DNS that can add these entries without your
knowledge

Issue Applies To:
Windows 2000
=======================

While the Windows Update Web site is loading, you receive Initialization
error 0x80072EE2
Problem Description
Internet Timeout

Resolutions:
This issue can be resolved by enabling "Use HTTP 1.1 through proxy
connections" in
Internet Options.
To enable "Use HTTP 1.1 through proxy connections"
1. Open Internet Explorer, click "Tools," and then click "Internet Options."
2. Click "Advanced."
3. Click the "Use HTTP 1.1" check box.
4. Click the "Use HTTP 1.1 through proxy connections" check box.
5. Attempt to access the Windows Update site again.

You may need to add the following URLs to your proxy exception list:

With wildcards:
*.Windowsupdate.microsoft.com
*.Windowsupdate.com

Specific URLs:
Windowsupdate.microsoft.com
V4.Windowsupdate.microsoft.com
Download.Windowsupdate.com

Issue Applies To:
Windows XP

--
Hope this helps. Let us know.
Wes

In
Maurice N said:
Wesley said:
John;

I just got on, no problem.


In
John said:
For 24 hours I have not been able to run Windows Update. I get a
message that the page is inaccessible because of network
diffivulties.

Is this a general experience or is ther something wrong at my end?
[XP Pro + SP1 worksation]
Click to expand...
Click to expand...

There are reports that some users ARE having a problem connecting.
Real problem. But not for all.
Suggest people look in their log file. Then see what *Errors* are
listed.

Do you have these errors in your log file: 80072EE7 or 801901F7
?
Click to expand...
 
Wesley said:
Maurice;

What log file?
Windows Update.log
YES

Where is it located?
C:\WINDOWS
YES

If someone did have these errors in their log file: 80072EE7 or
801901F7
What would that mean?
Click to expand...

80072EE7 is a DNS name resolution problem.
This remedy-attempt may be tried:
1. Clear Internet Explorer temporary internet cache.

2. Go to Start > Select RUN > type in
CMD <enter>

type in "ipconfig /flushdns" (without the quotes)
EXIT <enter>
This will flush your local cache of the DNS.

You may try Windows Update again. If it still fails, then wait 24 hours. Hopefully it will then go away.

The 801901F7 means Server too busy.
 
Maurice said:
80072EE7 is a DNS name resolution problem.
This remedy-attempt may be tried:
1. Clear Internet Explorer temporary internet cache.
Click to expand...

Worth noting that MSoft has been suffering attacks from MyDoom and so
on, and some accesses have been blocked - in defence I think. I could
not get through to www.microsoft.com from one ISP for over two weeks,
though I could from another. All one can do is have a daily try
 
Back
Top