8024402C and 80072ee7

In a msg in this NG dated Jul 2 2006 10:21 AM and entitled "Windows
update doesn't; 8024402C and 80072ee7", I asked about why Windows
Update wouldn't work on one of my PCs. I had tried everything I could
find in this NG and at Microsoft, to no avail; the Windows update log
shows a long series of 80072ee7 errors, followed by a 0x8024402C error.

This is not a firewall error, as I have tried it with the firewall
turned off. Nor is it a problem with my ISP, since I have tried it
with two different ISPs (comcast and my olde dial-up ISP). And the
other PCs on my home network update just fine.

I've spent hours trying various things, to no avail. My only guess at
this point is that I have some malware, although all my scans have come
up clean (Avast, Spybot, Ad-Aware). If you have suggestions for other
scanners to try, please do. In fact, if you have _any_ suggestions,
_please_ do!

This affects Windows Update, Windows Defender, and possibly CygWin
update (at least that wasn't working last night).

What alternatives do I have for updating these programs? Is it
possible to download the update packages to one of my other PCs, and
then copy it over to this one and run the update?

/s/
Desperate
(aka Mike Maxwell)

wrote:

> In a msg in this NG dated Jul 2 2006 10:21 AM and entitled "Windows
> update doesn't; 8024402C and 80072ee7", I asked about why Windows
> Update wouldn't work on one of my PCs. I had tried everything I could
> find in this NG and at Microsoft, to no avail; the Windows update log
> shows a long series of 80072ee7 errors, followed by a 0x8024402C
> error.
> [snip]
> This affects Windows Update, Windows Defender, and possibly CygWin
> update (at least that wasn't working last night).

See http://support.microsoft.com/kb/836941

Try also "Dial-a-fix" from http://wiki.djlizard.net/Dial-a-fix to repair
Windows Update and network settings.

Try opening a command prompt window and typing the command:

netsh winsock reset

--
Robin Walker [MVP Networking]

Thanks for your reply, but I'm still stuck:

Robin Walker [MVP] wrote:
> See http://support.microsoft.com/kb/836941
I had already tried this. I should probably run through the list
again, just to make sure.

> Try also "Dial-a-fix" from http://wiki.djlizard.net/Dial-a-fix to repair
> Windows Update and network settings.
Ran it with the "Fix Windows update" box checked (and all the boxes
that that automagically checks), still not working.

> Try opening a command prompt window and typing the command:
>
> netsh winsock reset
Did this, rebooted as directed. Still not working.

I also went to Symantec and ran their virus scan through the ActiveX
interface, came up clean.

Based on advice in another thread, I did this:
---------------------------
>nslookup download.windowsupdate.com
*** Can't find server name for address 192.168.2.1: Non-existent domain
*** Default servers are not available
Server: UnKnown
Address: 192.168.2.1

Non-authoritative answer:
Name: a258.g.akamai.net
Addresses: 204.2.192.41, 204.2.192.47
Aliases: download.windowsupdate.com, main.dl.wu.akadns.net
dom.dl.wu.akadns.net, dl.wu.ms.edgesuite.net
---------------------------
I'm not sure how to interpret this. Looks like it failed to find the
DNS server where it expected. 192.168.2.1 is the IP address of my
router--why would it expect my router to be acting as a DNS server? I
do have TCP/IP set up to "Obtain DNS server address automatically", as
directed by my ISP = Comcast. But then it comes up with what looks (to
me, anyway!) like correct but "non-authoratitive" addresses for aliases
anyway. Is there any way to verify the 204 IP addresses? I can ping
them fine.

Mike Maxwell

wrote:

>> nslookup download.windowsupdate.com
> *** Can't find server name for address 192.168.2.1: Non-existent
> domain
> *** Default servers are not available
> Server: UnKnown
> Address: 192.168.2.1
>
> Non-authoritative answer:
> Name: a258.g.akamai.net
> Addresses: 204.2.192.41, 204.2.192.47
> Aliases: download.windowsupdate.com, main.dl.wu.akadns.net
> dom.dl.wu.akadns.net, dl.wu.ms.edgesuite.net
> ---------------------------
> I'm not sure how to interpret this. Looks like it failed to find the
> DNS server where it expected. 192.168.2.1 is the IP address of my
> router--why would it expect my router to be acting as a DNS server? I
> do have TCP/IP set up to "Obtain DNS server address automatically", as
> directed by my ISP = Comcast. But then it comes up with what looks
> (to me, anyway!) like correct but "non-authoratitive" addresses for
> aliases anyway. Is there any way to verify the 204 IP addresses? I
> can ping them fine.

Your router 192.168.2.1 has declared itself to be your DNS server when it
responded to your PC's DHCP request. So your router will proxy all DNS
requests from your PC. The rest of the messages are then all normal. The
replies are "non-authoritative" because they do not come from the primary
DNS servers for the domains of the IP addresses in question. All normal.

I don't think that any of this is related to your Windows Update problem.

--
Robin Walker [MVP Networking]

Robin Walker [MVP] wrote:
....
> Your router 192.168.2.1 has declared itself to be your DNS server when it
> responded to your PC's DHCP request. So your router will proxy all DNS
> requests from your PC.

When you say my "router will proxy all DNS requests from your PC",
that is not the same as saying that my router is a proxy server, is it?


> The rest of the messages are then all normal. The
> replies are "non-authoritative" because they do not come from the primary
> DNS servers for the domains of the IP addresses in question. All normal.
>
> I don't think that any of this is related to your Windows Update problem.

OK, so where do I go from here?

Mike Maxwell

wrote:

> When you say my "router will proxy all DNS requests from your PC",
> that is not the same as saying that my router is a proxy server, is
> it?

It looks as if the router is a proxy for DNS requests, but not for anything
else. Since the other PCs on your LAN are behaving normally, this is not a
problem.

> OK, so where do I go from here?

Can you open a command prompt window, type the command

ipconfig /all

and copy/paste the results back here?

--
Robin Walker [MVP Networking]

Robin Walker [MVP] wrote:
> Can you open a command prompt window, type the command
>
> ipconfig /all
>
> and copy/paste the results back here?


Here goes:
--------------------------------
>ipconfig/all

Windows IP Configuration

Host Name . . . . . . . . . . . . : MUINANE
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Mixed
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : ChezNous

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Realtek RTL8139/810x Family
Fast Eth
ernet NIC
Physical Address. . . . . . . . . : 00-13-D3-9E-36-8F

Ethernet adapter Wireless Network Connection:

Connection-specific DNS Suffix . : ChezNous
Description . . . . . . . . . . . : IEEE 802.11g Wireless
Cardbus/PCI Ad
apter
Physical Address. . . . . . . . . : 00-40-F4-F3-AB-BE
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.2.4
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1
DHCP Server . . . . . . . . . . . : 192.168.2.1
DNS Servers . . . . . . . . . . . : 192.168.2.1
Lease Obtained. . . . . . . . . . : Saturday, July 08, 2006
4:04:04 PM
Lease Expires . . . . . . . . . . : Monday, January 18, 2038
11:14:07 PM
--------------------------------
BTW, I turned off my wireless network and tried to use the dial-up
again, still no luck. But I tried nslookup there, and it gave a result
more like what I expected:
--------------
>nslookup download.windowsupdate.com
Server: ns4.starnetusa.net
Address: 66.19.192.200

Non-authoritative answer:
Name: download.windowsupdate.com.c.footprint.net
Addresses: 209.3.40.190, 63.236.48.222
Aliases: download.windowsupdate.com, main.dl.wu.akadns.net
dom.dl.wu.akadns.net, download.windowsupdate.com.fp.nsatc.net
--------------
But as you say, that doesn't seem to be the problem.

Thanks for your help!

Mike Maxwell

wrote:

> DNS Suffix Search List. . . . . . : ChezNous
>
> Ethernet adapter Wireless Network Connection:
>
> Connection-specific DNS Suffix . : ChezNous

Could you try deleting these "ChezNous" configurations from your network
configuration.

Also, use Dial-a-Fix 0.60 beta to "Flush Software Distribution"

--
Robin Walker [MVP Networking]

Robin Walker [MVP] wrote:
> wrote:
>
> > DNS Suffix Search List. . . . . . : ChezNous
> >
> > Ethernet adapter Wireless Network Connection:
> >
> > Connection-specific DNS Suffix . : ChezNous
>
> Could you try deleting these "ChezNous" configurations from your network
> configuration.

Uh...not sure how to do this. Nothing obvious in the router interface.


I brought up the network config for TCP/IP for the wireless on my PC,
but nothing obvious there, either. On the "Advanced" settings for
TCP/IP properties, on the DNS tab, there is a radio button that allows
you to choose between "Append primary and connection specific DNS
suffixes" and "Append these DNS suffixes (in order)." The former was
checked (along with its check button for "Append parent suffixes of the
primary DNS suffix"), but if I switch the radio button to the latter,
it requires me to list at least one DNS suffix.

I tried disabling my wireless and using the dial-up, in which case
ipconfig/all shows a blank in the "DNS Suffix Search List" and in the
"Connection-specific DNS Suffix". But of course the update doesn't
work there either... (I just now verified that, with no firewall
turned on.) Here's the result from ipconfig/all with the dial-up:
--------------------------
>ipconfig/all

Windows IP Configuration

Host Name . . . . . . . . . . . . : MUINANE
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Mixed
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Realtek RTL8139/810x Family
Fast Eth
ernet NIC
Physical Address. . . . . . . . . : 00-13-D3-9E-36-8F

PPP adapter NetHere:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 66.217.131.111
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 66.217.131.111
DNS Servers . . . . . . . . . . . : 66.19.192.200
216.126.128.40
NetBIOS over Tcpip. . . . . . . . : Disabled
--------------------------
Again, let me thank you for your rapid responses, and taking the time.
I do hope you have a life...

Mike Maxwell

Robin Walker [MVP] wrote:
> wrote:
>
> > DNS Suffix Search List. . . . . . : ChezNous
> >
> > Ethernet adapter Wireless Network Connection:
> >
> > Connection-specific DNS Suffix . : ChezNous
>
> Could you try deleting these "ChezNous" configurations from your network
> configuration.

Since I haven't figured out how to do this for my wireless, and since
the corresponding entries for my dial-up cnxn are blank, I tried:

> Also, use Dial-a-Fix 0.60 beta to "Flush Software Distribution"

(Or rather, I did the steps manually, saving the old
\windows\SoftwareDistribution to another location rather than deleting
it--on the assumption that the information in there might be useful.
If that was the wrong thing to do, let me know.)

Still no luck (using the dial-up with no firewall).

Mike Maxwell