"Brad Arnold" <> wrote in message
news:a0dd823d-36e9-481c-8296-...
>>>>> [Subject: Error 0x80244018]
http://msdn2.microsoft.com/en-us/library/aa387293.aspx
(Live Search for
0x80244018 update site:microsoft.com
)
<quote>
WU_E_PT_HTTP_STATUS_FORBIDDEN 0x80244018
Same as HTTP status 403 – server understood the request, but declines to fulfill it.
</quote>
> Re the free support, this is a business computer. Microsoft transfered
> me to a support person who then told me it was 295.00 to fix this.
> It's an old pc we're using for Remote Desktop purposes...Before I
> spend 3 bills on support I'll spend 425 on a brand new PC...
Try some diagnosis? ; )
Try using Fiddler2 to find out what the request was and where it was going.
Another HTTP 403 symptom was recently diagnosed as being a problem
with proxy being specified inappropriately. However, the same symptom
could occur if you are getting a bad lookup for the server you are connecting to.
E.g. DNS is out of date, server has been taken out of service, etc.
Provided the protocol isn't https an alternative to using Fiddler would be to take
a packet trace, e.g. using netcap and then formatting the .cap file with Ethereal.
Depending on when the request is being issued in the connection sequence
and how it is being handled it could also be a symptom of a problem with
a caching server. Long ago a common suggestion which was made for
a related symptom was to try using https: as the protocol from the start.
since HTTPS would defeat the use of caching. Things have changed a lot
since then (e.g. that was WUv4) but it would be something simple to test.
For more general diagnosis you could try running ProcMon
to supplement the messages in the logs.
Also, it's possible that the error code is bogus but related to BITS
as the article mentions. In that case since you have XP Pro you could
try using bitsadmin /util to both check the proxy settings in more detail
and check or even reinitialize the BITS service.
>
> Thanks!
Good luck
Robert Aldwinckle
---