Re: Calling on Microsoft's Most Valuable Primates
- From: kungfoo <kungfoo.1uchcj@xxxxxxxxxxxx>
- Date: Thu, 25 Aug 2005 13:14:48 -0500
I am running XP pro and my problem started after I upgraded my home
network and purchased a Linksys 802.llb/g capable router. I am not sure
of your particular situation. However, according to everything I've read
the issue is caused primarily by connectivity problems. The ActiveX
control running on your machine doesn't get a timely response from the
windows update server and just decides to close up shop. If you have
already done all the Microsoft suggested fixes as posted by, Foxhole
and are still unsuccessful then I can suggest the following.
I would suggest you ping update.mirosoft.com but unfortunately they
apear to have their ICMP port disabled. This would give you an idea of
the reliability of the end-to-end Internet path between your machine
and their server. The next best thing it to run the ping utility
against another server on the internet
just to see if there are any dropped packets etc. If that looks good
then run the ping utility with the following options ping [host] -f -l
1480. This sends a packet of size (1480) un-fragmented to the host. If
you get "Packet needs to be fragmented but DF set" then keep bumping
down the number until you get a successful response. This will give you
an idea of whether or not you implemented the fix I suggested properly.
The number should be close to 1480. Between 1470 and 1300 seems to be
about average. If you are finding that it's far less, then that may be
your problem. I think the default for windows is 540. If this is the
case run through my fix again and retest. You can implement both steps
in the fix 1.) and 2.) at the same time. If you find that it is sill
not working then you may have a router on you network that is not
supporting the larger MTU size. Run a trace route to the host you were
pinging and identify the routers on your network. Check their MTU
settings. If, however, you find that you have successful pings with MTU
sizes between 1480-1300 my fix probably won't help.
That's all I have... if it still doesn't work then a call to Microsoft
is probably in order. : )
--
kungfoo
------------------------------------------------------------------------
Posted via http://www.mcse.ms
------------------------------------------------------------------------
View this thread: http://www.mcse.ms/message1789315.html
.
- Follow-Ups:
- Re: Calling on Microsoft's Most Valuable Primates
- From: Florida Gal :)
- Re: Calling on Microsoft's Most Valuable Primates
- References:
- Calling on Microsoft's Most Valuable Primates
- From: ashraf kadry
- Re: Calling on Microsoft's Most Valuable Primates
- From: kungfoo
- Re: Calling on Microsoft's Most Valuable Primates
- From: liddo
- Calling on Microsoft's Most Valuable Primates
- Prev by Date: RE: Windows Update
- Next by Date: Re: error message 0x80248011
- Previous by thread: Re: Calling on Microsoft's Most Valuable Primates
- Next by thread: Re: Calling on Microsoft's Most Valuable Primates
- Index(es):
Relevant Pages
|
Loading