Discussion:
Clients not reporting any more
(too old to reply)
Glenn @ Maranatha
2006-02-09 17:20:34 UTC
Permalink
All clients were reporting correctly and receiving all updates, but since Jan
15 no computers have reported in, they all show as being out of date. They
all have the yellow exclamation. On the client i get the 0x80244018 error, if
you look that up in google it says something about authentication, but all i
can find are errors related to getting updates from windows update.com etc,
nothing about using WSUS.
--
Glenn MCP A+
Network Admin
MBBC
Lawrence Garvin (MVP)
2006-02-10 03:56:30 UTC
Permalink
0x80244018 - SUS E PT HTTP STATUS FORBIDDEN
HTTP Status 403 - request forbidden

This is a proxy server or firewall blocking access to the web server.

Or a misconfigured proxy client otherwise trying to use a known proxy
server.
Post by Glenn @ Maranatha
All clients were reporting correctly and receiving all updates, but since Jan
15 no computers have reported in, they all show as being out of date. They
all have the yellow exclamation. On the client i get the 0x80244018 error, if
you look that up in google it says something about authentication, but all i
can find are errors related to getting updates from windows update.com etc,
nothing about using WSUS.
--
Glenn MCP A+
Network Admin
MBBC
Glenn @ Maranatha
2006-02-10 05:03:28 UTC
Permalink
Both my WSUS and all clients are on the inside of my proxy server. My WSUS is
getting the updates from the windows site ok. It is just that the clients are
not reporting correcly. Is there a way to make the client go straight to the
WSUS server? Here is a snippet from my windowsupdate.log...
(APPS is the name of my WSUS server)

2006-02-09 22:13:22 1156 600 PT +++++++++++ PT: Synchronizing server
updates +++++++++++
2006-02-09 22:13:22 1156 600 PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://apps:8530/ClientWebService/client.asmx
2006-02-09 22:13:22 1156 600 PT Initializing simple targeting cookie,
clientId = 2f8f4dfe-5861-4267-94bf-16fdf19a6989, target group = , DNS name =
ms-679.mbbc.edu
2006-02-09 22:13:22 1156 600 PT Server URL =
http://apps:8530/SimpleAuthWebService/SimpleAuth.asmx
2006-02-09 22:13:22 1156 600 PT WARNING: GetAuthorizationCookie failure,
error = 0x80244018, soap client error = 10, soap error code = 0, HTTP status
code = 403
2006-02-09 22:13:22 1156 600 PT WARNING: Sync of Updates: 0x80244018
2006-02-09 22:13:22 1156 600 Agent * WARNING: Failed to synchronize, error
= 0x80244018
2006-02-09 22:13:22 1156 600 Agent * WARNING: Exit code = 0x80244018
2006-02-09 22:13:22 1156 600 Agent *********
2006-02-09 22:13:22 1156 600 Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2006-02-09 22:13:22 1156 600 Agent *************
2006-02-09 22:13:22 1156 600 Agent WARNING: WU client failed Searching for
update with error 0x80244018
2006-02-09 22:13:22 1156 600 AU >>## RESUMED ## AU: Search for updates
[CallId = {2BB8D88D-D1EA-420B-8EE1-F4FD3A45F9C8}]
2006-02-09 22:13:22 1156 600 AU # WARNING: Search callback failed, result
= 0x80244018
2006-02-09 22:13:22 1156 600 AU #########
2006-02-09 22:13:22 1156 600 AU ## END ## AU: Search for updates [CallId
= {2BB8D88D-D1EA-420B-8EE1-F4FD3A45F9C8}]
2006-02-09 22:13:22 1156 600 AU #############
2006-02-09 22:13:22 1156 600 AU AU setting next detection timeout to
2006-02-10 09:13:22
2006-02-09 22:13:27 1156 600 Report REPORT EVENT:
{BB01A493-A1FA-4D5E-8FBE-1D1A7DE9B6A8} 2006-02-09
22:13:22-0600 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80244018 AutomaticUpdates Failure Software
Synchronization Error: Agent failed detecting with reason: 0x80244018
2006-02-09 22:30:01 1156 6b4 PT Initializing simple targeting cookie,
clientId = 2f8f4dfe-5861-4267-94bf-16fdf19a6989, target group = , DNS name =
ms-679.mbbc.edu
2006-02-09 22:30:01 1156 6b4 PT Server URL =
http://apps:8530/SimpleAuthWebService/SimpleAuth.asmx
2006-02-09 22:30:01 1156 6b4 PT WARNING: GetAuthorizationCookie failure,
error = 0x80244018, soap client error = 10, soap error code = 0, HTTP status
code = 403
2006-02-09 22:30:01 1156 6b4 Report WARNING: Reporter failed to upload
events with hr = 80244018.
2006-02-09 22:52:59 1156 498 PT Initializing simple targeting cookie,
clientId = 2f8f4dfe-5861-4267-94bf-16fdf19a6989, target group = , DNS name =
ms-679.mbbc.edu
2006-02-09 22:52:59 1156 498 PT Server URL =
http://apps:8530/SimpleAuthWebService/SimpleAuth.asmx
2006-02-09 22:52:59 1156 498 PT WARNING: GetAuthorizationCookie failure,
error = 0x80244018, soap client error = 10, soap error code = 0, HTTP status
code = 403
2006-02-09 22:52:59 1156 498 Report WARNING: Reporter failed to upload
events with hr = 80244018.
--
Glenn MCP A+
Network Admin
MBBC
Post by Lawrence Garvin (MVP)
0x80244018 - SUS E PT HTTP STATUS FORBIDDEN
HTTP Status 403 - request forbidden
This is a proxy server or firewall blocking access to the web server.
Or a misconfigured proxy client otherwise trying to use a known proxy
server.
Post by Glenn @ Maranatha
All clients were reporting correctly and receiving all updates, but since Jan
15 no computers have reported in, they all show as being out of date. They
all have the yellow exclamation. On the client i get the 0x80244018 error, if
you look that up in google it says something about authentication, but all i
can find are errors related to getting updates from windows update.com etc,
nothing about using WSUS.
--
Glenn MCP A+
Network Admin
MBBC
Lawrence Garvin
2006-02-12 01:57:40 UTC
Permalink
That depends on how the client is actually configured.

Now, given that you've said "it worked... and then it didn't" (paraphrased),
I'm honor bound to ask the primary question: WHAT CHANGED???

In the meantime, run the Client Diagnostic Tool on this system and post the
results here.
Post by Glenn @ Maranatha
Both my WSUS and all clients are on the inside of my proxy server. My WSUS is
getting the updates from the windows site ok. It is just that the clients are
not reporting correcly. Is there a way to make the client go straight to the
WSUS server? Here is a snippet from my windowsupdate.log...
(APPS is the name of my WSUS server)
2006-02-09 22:13:22 1156 600 PT +++++++++++ PT: Synchronizing server
updates +++++++++++
2006-02-09 22:13:22 1156 600 PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://apps:8530/ClientWebService/client.asmx
2006-02-09 22:13:22 1156 600 PT Initializing simple targeting cookie,
clientId = 2f8f4dfe-5861-4267-94bf-16fdf19a6989, target group = , DNS name =
ms-679.mbbc.edu
2006-02-09 22:13:22 1156 600 PT Server URL =
http://apps:8530/SimpleAuthWebService/SimpleAuth.asmx
2006-02-09 22:13:22 1156 600 PT WARNING: GetAuthorizationCookie failure,
error = 0x80244018, soap client error = 10, soap error code = 0, HTTP status
code = 403
2006-02-09 22:13:22 1156 600 PT WARNING: Sync of Updates: 0x80244018
2006-02-09 22:13:22 1156 600 Agent * WARNING: Failed to synchronize,
error
= 0x80244018
2006-02-09 22:13:22 1156 600 Agent * WARNING: Exit code = 0x80244018
2006-02-09 22:13:22 1156 600 Agent *********
2006-02-09 22:13:22 1156 600 Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2006-02-09 22:13:22 1156 600 Agent *************
2006-02-09 22:13:22 1156 600 Agent WARNING: WU client failed Searching for
update with error 0x80244018
2006-02-09 22:13:22 1156 600 AU >>## RESUMED ## AU: Search for updates
[CallId = {2BB8D88D-D1EA-420B-8EE1-F4FD3A45F9C8}]
2006-02-09 22:13:22 1156 600 AU # WARNING: Search callback failed,
result
= 0x80244018
2006-02-09 22:13:22 1156 600 AU #########
2006-02-09 22:13:22 1156 600 AU ## END ## AU: Search for updates
[CallId
= {2BB8D88D-D1EA-420B-8EE1-F4FD3A45F9C8}]
2006-02-09 22:13:22 1156 600 AU #############
2006-02-09 22:13:22 1156 600 AU AU setting next detection timeout to
2006-02-10 09:13:22
{BB01A493-A1FA-4D5E-8FBE-1D1A7DE9B6A8} 2006-02-09
22:13:22-0600 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80244018
AutomaticUpdates Failure Software
Synchronization Error: Agent failed detecting with reason: 0x80244018
2006-02-09 22:30:01 1156 6b4 PT Initializing simple targeting cookie,
clientId = 2f8f4dfe-5861-4267-94bf-16fdf19a6989, target group = , DNS name =
ms-679.mbbc.edu
2006-02-09 22:30:01 1156 6b4 PT Server URL =
http://apps:8530/SimpleAuthWebService/SimpleAuth.asmx
2006-02-09 22:30:01 1156 6b4 PT WARNING: GetAuthorizationCookie failure,
error = 0x80244018, soap client error = 10, soap error code = 0, HTTP status
code = 403
2006-02-09 22:30:01 1156 6b4 Report WARNING: Reporter failed to upload
events with hr = 80244018.
2006-02-09 22:52:59 1156 498 PT Initializing simple targeting cookie,
clientId = 2f8f4dfe-5861-4267-94bf-16fdf19a6989, target group = , DNS name =
ms-679.mbbc.edu
2006-02-09 22:52:59 1156 498 PT Server URL =
http://apps:8530/SimpleAuthWebService/SimpleAuth.asmx
2006-02-09 22:52:59 1156 498 PT WARNING: GetAuthorizationCookie failure,
error = 0x80244018, soap client error = 10, soap error code = 0, HTTP status
code = 403
2006-02-09 22:52:59 1156 498 Report WARNING: Reporter failed to upload
events with hr = 80244018.
--
Glenn MCP A+
Network Admin
MBBC
Post by Lawrence Garvin (MVP)
0x80244018 - SUS E PT HTTP STATUS FORBIDDEN
HTTP Status 403 - request forbidden
This is a proxy server or firewall blocking access to the web server.
Or a misconfigured proxy client otherwise trying to use a known proxy
server.
Post by Glenn @ Maranatha
All clients were reporting correctly and receiving all updates, but
since
Jan
15 no computers have reported in, they all show as being out of date. They
all have the yellow exclamation. On the client i get the 0x80244018
error,
if
you look that up in google it says something about authentication, but
all
i
can find are errors related to getting updates from windows update.com etc,
nothing about using WSUS.
--
Glenn MCP A+
Network Admin
MBBC
Glenn @ Maranatha
2006-02-13 22:50:35 UTC
Permalink
BTW, I also tried to go directly to the admin page from my computer and it
failed. http://apps:8530/WSUSAdmin, so it seems to me some permissions might
be messed up.

Here is the result for the clientdiag on one computer:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\temp\wsus>clientdiag.exe

WSUS Client Diagnostics Tool

Checking Machine State
Checking for admin rights to run tool . . . . . . . . . PASS
Automatic Updates Service is running. . . . . . . . . . PASS
Background Intelligent Transfer Service is running. . . PASS
Wuaueng.dll version 5.8.0.2469. . . . . . . . . . . . . PASS
This version is WSUS 2.0

Checking AU Settings
AU Option is 4: Scheduled Install . . . . . . . . . . . PASS
Option is from Policy settings

Checking Proxy Configuration
Checking for winhttp local machine Proxy settings . . . PASS
Winhttp local machine access type
<Direct Connection>
Winhttp local machine Proxy. . . . . . . . . . NONE
Winhttp local machine ProxyBypass. . . . . . . NONE
Checking User IE Proxy settings . . . . . . . . . . . . PASS
User IE Proxy
inet.mbbc.edu:8080
User IE ProxyByPass
10.2.*.*;10.1.*.*;*.mbbc.edu;<local>
User IE AutoConfig URL Proxy . . . . . . . . . NONE
User IE AutoDetect
AutoDetect not in use

Checking Connection to WSUS/SUS Server
WUServer = http://apps:8530
WUStatusServer = http://apps:8530
UseWuServer is enabled. . . . . . . . . . . . . . . . . PASS

VerifyWUServerURL() failed with hr=0x80072efd

A connection with the server could not be established


Press Enter to Complete

C:\temp\wsus>
--
Glenn MCP A+
Network Admin
MBBC
Post by Lawrence Garvin
That depends on how the client is actually configured.
Now, given that you've said "it worked... and then it didn't" (paraphrased),
I'm honor bound to ask the primary question: WHAT CHANGED???
In the meantime, run the Client Diagnostic Tool on this system and post the
results here.
Post by Glenn @ Maranatha
Both my WSUS and all clients are on the inside of my proxy server. My WSUS is
getting the updates from the windows site ok. It is just that the clients are
not reporting correcly. Is there a way to make the client go straight to the
WSUS server? Here is a snippet from my windowsupdate.log...
(APPS is the name of my WSUS server)
2006-02-09 22:13:22 1156 600 PT +++++++++++ PT: Synchronizing server
updates +++++++++++
2006-02-09 22:13:22 1156 600 PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://apps:8530/ClientWebService/client.asmx
2006-02-09 22:13:22 1156 600 PT Initializing simple targeting cookie,
clientId = 2f8f4dfe-5861-4267-94bf-16fdf19a6989, target group = , DNS name =
ms-679.mbbc.edu
2006-02-09 22:13:22 1156 600 PT Server URL =
http://apps:8530/SimpleAuthWebService/SimpleAuth.asmx
2006-02-09 22:13:22 1156 600 PT WARNING: GetAuthorizationCookie failure,
error = 0x80244018, soap client error = 10, soap error code = 0, HTTP status
code = 403
2006-02-09 22:13:22 1156 600 PT WARNING: Sync of Updates: 0x80244018
2006-02-09 22:13:22 1156 600 Agent * WARNING: Failed to synchronize,
error
= 0x80244018
2006-02-09 22:13:22 1156 600 Agent * WARNING: Exit code = 0x80244018
2006-02-09 22:13:22 1156 600 Agent *********
2006-02-09 22:13:22 1156 600 Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2006-02-09 22:13:22 1156 600 Agent *************
2006-02-09 22:13:22 1156 600 Agent WARNING: WU client failed Searching for
update with error 0x80244018
2006-02-09 22:13:22 1156 600 AU >>## RESUMED ## AU: Search for updates
[CallId = {2BB8D88D-D1EA-420B-8EE1-F4FD3A45F9C8}]
2006-02-09 22:13:22 1156 600 AU # WARNING: Search callback failed,
result
= 0x80244018
2006-02-09 22:13:22 1156 600 AU #########
2006-02-09 22:13:22 1156 600 AU ## END ## AU: Search for updates
[CallId
= {2BB8D88D-D1EA-420B-8EE1-F4FD3A45F9C8}]
2006-02-09 22:13:22 1156 600 AU #############
2006-02-09 22:13:22 1156 600 AU AU setting next detection timeout to
2006-02-10 09:13:22
{BB01A493-A1FA-4D5E-8FBE-1D1A7DE9B6A8} 2006-02-09
22:13:22-0600 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80244018
AutomaticUpdates Failure Software
Synchronization Error: Agent failed detecting with reason: 0x80244018
2006-02-09 22:30:01 1156 6b4 PT Initializing simple targeting cookie,
clientId = 2f8f4dfe-5861-4267-94bf-16fdf19a6989, target group = , DNS name =
ms-679.mbbc.edu
2006-02-09 22:30:01 1156 6b4 PT Server URL =
http://apps:8530/SimpleAuthWebService/SimpleAuth.asmx
2006-02-09 22:30:01 1156 6b4 PT WARNING: GetAuthorizationCookie failure,
error = 0x80244018, soap client error = 10, soap error code = 0, HTTP status
code = 403
2006-02-09 22:30:01 1156 6b4 Report WARNING: Reporter failed to upload
events with hr = 80244018.
2006-02-09 22:52:59 1156 498 PT Initializing simple targeting cookie,
clientId = 2f8f4dfe-5861-4267-94bf-16fdf19a6989, target group = , DNS name =
ms-679.mbbc.edu
2006-02-09 22:52:59 1156 498 PT Server URL =
http://apps:8530/SimpleAuthWebService/SimpleAuth.asmx
2006-02-09 22:52:59 1156 498 PT WARNING: GetAuthorizationCookie failure,
error = 0x80244018, soap client error = 10, soap error code = 0, HTTP status
code = 403
2006-02-09 22:52:59 1156 498 Report WARNING: Reporter failed to upload
events with hr = 80244018.
--
Glenn MCP A+
Network Admin
MBBC
Post by Lawrence Garvin (MVP)
0x80244018 - SUS E PT HTTP STATUS FORBIDDEN
HTTP Status 403 - request forbidden
This is a proxy server or firewall blocking access to the web server.
Or a misconfigured proxy client otherwise trying to use a known proxy
server.
Post by Glenn @ Maranatha
All clients were reporting correctly and receiving all updates, but
since
Jan
15 no computers have reported in, they all show as being out of date. They
all have the yellow exclamation. On the client i get the 0x80244018
error,
if
you look that up in google it says something about authentication, but
all
i
can find are errors related to getting updates from windows update.com etc,
nothing about using WSUS.
--
Glenn MCP A+
Network Admin
MBBC
Lawrence Garvin (MVP)
2006-02-13 23:19:33 UTC
Permalink
Post by Glenn @ Maranatha
Checking Connection to WSUS/SUS Server
WUServer = http://apps:8530
WUStatusServer = http://apps:8530
UseWuServer is enabled. . . . . . . . . . . . . . . . . PASS
VerifyWUServerURL() failed with hr=0x80072efd
A connection with the server could not be established
The 0x80072efd error is reported by the client when it does not receive a
response code from the web server at the specified URL.

This can be caused because a proxy server is interfering, the proxy client
is misconfigured, DNS is not working correctly, a router or routing table is
interfering if the client/server are on different subnets, or can also be
caused if the destination web server is not running.
Post by Glenn @ Maranatha
BTW, I also tried to go directly to the admin page from my computer and it
failed. http://apps:8530/WSUSAdmin, so it seems to me some permissions might
be messed up.
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\temp\wsus>clientdiag.exe
WSUS Client Diagnostics Tool
Checking Machine State
Checking for admin rights to run tool . . . . . . . . . PASS
Automatic Updates Service is running. . . . . . . . . . PASS
Background Intelligent Transfer Service is running. . . PASS
Wuaueng.dll version 5.8.0.2469. . . . . . . . . . . . . PASS
This version is WSUS 2.0
Checking AU Settings
AU Option is 4: Scheduled Install . . . . . . . . . . . PASS
Option is from Policy settings
Checking Proxy Configuration
Checking for winhttp local machine Proxy settings . . . PASS
Winhttp local machine access type
<Direct Connection>
Winhttp local machine Proxy. . . . . . . . . . NONE
Winhttp local machine ProxyBypass. . . . . . . NONE
Checking User IE Proxy settings . . . . . . . . . . . . PASS
User IE Proxy
inet.mbbc.edu:8080
User IE ProxyByPass
10.2.*.*;10.1.*.*;*.mbbc.edu;<local>
User IE AutoConfig URL Proxy . . . . . . . . . NONE
User IE AutoDetect
AutoDetect not in use
Checking Connection to WSUS/SUS Server
WUServer = http://apps:8530
WUStatusServer = http://apps:8530
UseWuServer is enabled. . . . . . . . . . . . . . . . . PASS
VerifyWUServerURL() failed with hr=0x80072efd
A connection with the server could not be established
Press Enter to Complete
C:\temp\wsus>
--
Glenn MCP A+
Network Admin
MBBC
Post by Lawrence Garvin
That depends on how the client is actually configured.
Now, given that you've said "it worked... and then it didn't"
(paraphrased),
I'm honor bound to ask the primary question: WHAT CHANGED???
In the meantime, run the Client Diagnostic Tool on this system and post the
results here.
Post by Glenn @ Maranatha
Both my WSUS and all clients are on the inside of my proxy server. My
WSUS
is
getting the updates from the windows site ok. It is just that the
clients
are
not reporting correcly. Is there a way to make the client go straight
to
the
WSUS server? Here is a snippet from my windowsupdate.log...
(APPS is the name of my WSUS server)
2006-02-09 22:13:22 1156 600 PT +++++++++++ PT: Synchronizing server
updates +++++++++++
2006-02-09 22:13:22 1156 600 PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://apps:8530/ClientWebService/client.asmx
2006-02-09 22:13:22 1156 600 PT Initializing simple targeting cookie,
clientId = 2f8f4dfe-5861-4267-94bf-16fdf19a6989, target group = , DNS
name
=
ms-679.mbbc.edu
2006-02-09 22:13:22 1156 600 PT Server URL =
http://apps:8530/SimpleAuthWebService/SimpleAuth.asmx
2006-02-09 22:13:22 1156 600 PT WARNING: GetAuthorizationCookie failure,
error = 0x80244018, soap client error = 10, soap error code = 0, HTTP status
code = 403
2006-02-09 22:13:22 1156 600 PT WARNING: Sync of Updates: 0x80244018
2006-02-09 22:13:22 1156 600 Agent * WARNING: Failed to synchronize,
error
= 0x80244018
2006-02-09 22:13:22 1156 600 Agent * WARNING: Exit code = 0x80244018
2006-02-09 22:13:22 1156 600 Agent *********
2006-02-09 22:13:22 1156 600 Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2006-02-09 22:13:22 1156 600 Agent *************
2006-02-09 22:13:22 1156 600 Agent WARNING: WU client failed Searching for
update with error 0x80244018
2006-02-09 22:13:22 1156 600 AU >>## RESUMED ## AU: Search for updates
[CallId = {2BB8D88D-D1EA-420B-8EE1-F4FD3A45F9C8}]
2006-02-09 22:13:22 1156 600 AU # WARNING: Search callback failed,
result
= 0x80244018
2006-02-09 22:13:22 1156 600 AU #########
2006-02-09 22:13:22 1156 600 AU ## END ## AU: Search for updates
[CallId
= {2BB8D88D-D1EA-420B-8EE1-F4FD3A45F9C8}]
2006-02-09 22:13:22 1156 600 AU #############
2006-02-09 22:13:22 1156 600 AU AU setting next detection timeout to
2006-02-10 09:13:22
{BB01A493-A1FA-4D5E-8FBE-1D1A7DE9B6A8} 2006-02-09
22:13:22-0600 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80244018
AutomaticUpdates Failure Software
Synchronization Error: Agent failed detecting with reason: 0x80244018
2006-02-09 22:30:01 1156 6b4 PT Initializing simple targeting cookie,
clientId = 2f8f4dfe-5861-4267-94bf-16fdf19a6989, target group = , DNS
name
=
ms-679.mbbc.edu
2006-02-09 22:30:01 1156 6b4 PT Server URL =
http://apps:8530/SimpleAuthWebService/SimpleAuth.asmx
2006-02-09 22:30:01 1156 6b4 PT WARNING: GetAuthorizationCookie failure,
error = 0x80244018, soap client error = 10, soap error code = 0, HTTP status
code = 403
2006-02-09 22:30:01 1156 6b4 Report WARNING: Reporter failed to upload
events with hr = 80244018.
2006-02-09 22:52:59 1156 498 PT Initializing simple targeting cookie,
clientId = 2f8f4dfe-5861-4267-94bf-16fdf19a6989, target group = , DNS
name
=
ms-679.mbbc.edu
2006-02-09 22:52:59 1156 498 PT Server URL =
http://apps:8530/SimpleAuthWebService/SimpleAuth.asmx
2006-02-09 22:52:59 1156 498 PT WARNING: GetAuthorizationCookie failure,
error = 0x80244018, soap client error = 10, soap error code = 0, HTTP status
code = 403
2006-02-09 22:52:59 1156 498 Report WARNING: Reporter failed to upload
events with hr = 80244018.
--
Glenn MCP A+
Network Admin
MBBC
Post by Lawrence Garvin (MVP)
0x80244018 - SUS E PT HTTP STATUS FORBIDDEN
HTTP Status 403 - request forbidden
This is a proxy server or firewall blocking access to the web server.
Or a misconfigured proxy client otherwise trying to use a known proxy
server.
Post by Glenn @ Maranatha
All clients were reporting correctly and receiving all updates, but
since
Jan
15 no computers have reported in, they all show as being out of
date.
They
all have the yellow exclamation. On the client i get the 0x80244018
error,
if
you look that up in google it says something about authentication, but
all
i
can find are errors related to getting updates from windows
update.com
etc,
nothing about using WSUS.
--
Glenn MCP A+
Network Admin
MBBC
Continue reading on narkive:
Loading...