Read this first (was: 8024402C and 80072ee7)

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Robin Walker [MVP] wrote:
Can you try opening a command prompt window and typing the following
commands:

route print

tracert download.windowsupdate.com

and copy&paste the results back?

Turned out my bad 'route print' and 'tracert' results were caused by my
firewall. I turned the firewall (Comodo) off and turned my WinXP
firewall on (I didn't figure I should be out there without any firewall
at all), and this time (using cable ISP), I got significantly different
results:
------------------------
route print
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 13 d3 9e 36 8f ...... Realtek RTL8139/810x Family Fast
Ethernet NIC -
Packet Scheduler Miniport
0x3 ...00 40 f4 f3 ab be ...... IEEE 802.11g Wireless Cardbus/PCI
Adapter - Pack
et Scheduler Miniport
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface
Metric
0.0.0.0 0.0.0.0 192.168.2.1 192.168.2.4
40
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
1
192.168.2.0 255.255.255.0 192.168.2.4 192.168.2.4
40
192.168.2.4 255.255.255.255 127.0.0.1 127.0.0.1
40
192.168.2.255 255.255.255.255 192.168.2.4 192.168.2.4
40
224.0.0.0 240.0.0.0 192.168.2.4 192.168.2.4
40
255.255.255.255 255.255.255.255 192.168.2.4 2
1
255.255.255.255 255.255.255.255 192.168.2.4 192.168.2.4
1
Default Gateway: 192.168.2.1
===========================================================================
Persistent Routes:
None

tracert download.windowsupdate.com

Tracing route to download.windowsupdate.com.c.footprint.net
[208.172.64.222]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.2.1
2 * * * Request timed out.
3 12 ms 8 ms 9 ms
ge-1-22-ur01.hyattsville.md.bad.comcast.net [68.
87.136.113]
4 8 ms 9 ms 10 ms te-9-3-ur02.lanham.md.bad.comcast.net
[68.87.129
..46]
5 9 ms 9 ms 9 ms te-9-1-ur01.lanham.md.bad.comcast.net
[68.87.129
..61]
6 9 ms 9 ms 12 ms te-9-1-ur01.bowie.md.bad.comcast.net
[68.87.128.
177]
7 11 ms 15 ms 15 ms
te-8-2-ar01.capitolhghts.md.bad.comcast.net [68.
87.128.182]
8 15 ms 11 ms 11 ms
POS-2-3-cr01.ritchieroad.md.pvcomcast.net [68.87
..16.165]
9 14 ms 10 ms 11 ms 12.118.122.5
10 12 ms 12 ms 11 ms tbr2-p011701.wswdc.ip.att.net
[12.123.8.30]
11 12 ms 12 ms 11 ms 12.123.8.109
12 10 ms 11 ms 32 ms dcr2-so-4-0-0.Washington.savvis.net
[206.24.238.
161]
13 74 ms 10 ms 12 ms bcs2-as0-0.Washington.savvis.net
[204.70.192.166
]
14 11 ms 12 ms 11 ms bcs1-so-7-0-0.Washington.savvis.net
[204.70.192.
33]
15 25 ms 26 ms 23 ms dcr1-so-3-0-0.Atlanta.savvis.net
[204.70.192.53]

16 24 ms 23 ms 23 ms acr1-so-4-0-0.Atlanta.savvis.net
[208.172.67.245
]
17 28 ms 24 ms 25 ms 208.172.64.222

Trace complete.
---------------------------

But Windows Update still gives me the same 8024402C and 80072ee7 errors
(I just checked again).

Mike Maxwell

.

Relevant Pages

  • Re: Web server behind Symantec Enterprise Firewall
    ... I've published a virtual IP at the Firewall to which i route the http ... NAT rule AccesoServer was chosen, but client transparency is ... Since the web server is on the LAN, you shouldn't have to add any route ...
    (comp.security.firewalls)
  • Re: Urgent RRAS wont work Help!
    ... plus it worked before without a route on the FW. ... > Where you need the extra routing is on the firewall. ... > port access rights to clients on the 184.155.0.0 network. ...
    (microsoft.public.win2000.ras_routing)
  • Re: Web server behind Symantec Enterprise Firewall
    ... It seems it does not matter wich interfaces i set at the rule, ... tries to route it trought the same interface. ... firewall to the internal sever?... ... > on the firewall to point to the web server. ...
    (comp.security.firewalls)
  • Re: Urgent RRAS wont work Help!
    ... Where you need the extra routing is on the firewall. ... route but whatever config I use it won't route. ... The clients on the ... network have the default gateway set as 184.155.0.80 via DHCP. ...
    (microsoft.public.win2000.ras_routing)
  • Re: strange problem connecting 2 linux boxes
    ... > problem is because of a firewall. ... >> WRONG ROUTE TO IP ADDRESS ... The firewall host here could ping a host ... No ifconfig or route output from 192.168.0.1 ... ...
    (comp.os.linux.networking)