none
WSUS Clients not reporting

    Frage

  • Hi I recently installed WSUS. After setting up the GPO to receive automatic updates, I got this message on the client machine in the WindowsUpdate log.

    I was hoping someone could help me out as to why the client failed to connect?

    Also, there are 60 out of about 200 computers that are reporting fine.

    2013-06-09    00:16:54:333    1492    eb0    Agent    ** START **  Agent: Finding updates [CallerId = ]
    2013-06-09    00:16:54:333    1492    eb0    Agent    *********
    2013-06-09    00:16:54:333    1492    eb0    Agent      * Online = Yes; Ignore download priority = No
    2013-06-09    00:16:54:333    1492    eb0    Agent      * Criteria = "IsInstalled = 0 and IsHidden = 0"
    2013-06-09    00:16:54:333    1492    eb0    Agent      * ServiceID = {00000000-0000-0000-0000-000000000000} Third party service
    2013-06-09    00:16:54:333    1492    eb0    Agent      * Search Scope = {Machine}
    2013-06-09    00:16:54:552    3908    d00    COMAPI    <<-- SUBMITTED -- COMAPI: Search [ClientId = <NULL>]
    2013-06-09    00:17:02:896    1492    eb0    PT    +++++++++++  PT: Synchronizing server updates  +++++++++++
    2013-06-09    00:17:02:896    1492    eb0    PT      + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://ELMFS1/ClientWebService/client.asmx
    2013-06-09    00:17:02:989    1492    eb0    PT    WARNING: Cached cookie has expired or new PID is available
    2013-06-09    00:17:02:989    1492    eb0    PT    Initializing simple targeting cookie, clientId = be185879-df4b-4595-8555-80a1bc59bb15, target group = , DNS name = wselmwood030.brydsongroup.com
    2013-06-09    00:17:02:989    1492    eb0    PT      Server URL = http://ELMFS1/SimpleAuthWebService/SimpleAuth.asmx
    2013-06-09    00:17:03:036    1492    eb0    PT    WARNING: GetAuthorizationCookie failure, error = 0x8024402B, soap client error = 10, soap error code = 0, HTTP status code = 499
    2013-06-09    00:17:03:036    1492    eb0    PT    WARNING: Failed to initialize Simple Targeting Cookie: 0x8024402b
    2013-06-09    00:17:03:036    1492    eb0    PT    WARNING: PopulateAuthCookies failed: 0x8024402b
    2013-06-09    00:17:03:036    1492    eb0    PT    WARNING: RefreshCookie failed: 0x8024402b
    2013-06-09    00:17:03:036    1492    eb0    PT    WARNING: RefreshPTState failed: 0x8024402b
    2013-06-09    00:17:03:036    1492    eb0    PT    WARNING: Sync of Updates: 0x8024402b
    2013-06-09    00:17:03:036    1492    eb0    PT    WARNING: SyncServerUpdatesInternal failed: 0x8024402b
    2013-06-09    00:17:03:036    1492    eb0    Agent      * WARNING: Failed to synchronize, error = 0x8024402B
    2013-06-09    00:17:03:036    1492    eb0    Agent      * WARNING: Exit code = 0x8024402B
    2013-06-09    00:17:03:036    1492    eb0    Agent    *********
    2013-06-09    00:17:03:036    1492    eb0    Agent    **  END  **  Agent: Finding updates [CallerId = ]
    2013-06-09    00:17:03:036    1492    eb0    Agent    *************
    2013-06-09    00:17:03:036    1492    eb0    Agent    WARNING: WU client failed Searching for update with error 0x8024402b
    2013-06-09    00:17:03:067    3908    290    COMAPI    >>--  RESUMED  -- COMAPI: Search [ClientId = <NULL>]
    2013-06-09    00:17:03:067    3908    290    COMAPI      - Updates found = 0
    2013-06-09    00:17:03:067    3908    290    COMAPI      - WARNING: Exit code = 0x00000000, Result code = 0x8024402B
    2013-06-09    00:17:03:067    3908    290    COMAPI    ---------
    2013-06-09    00:17:03:067    3908    290    COMAPI    --  END  --  COMAPI: Search [ClientId = <NULL>]
    2013-06-09    00:17:03:067    3908    290    COMAPI    -------------
    2013-06-09    00:17:03:067    3908    d00    COMAPI    WARNING: Operation failed due to earlier error, hr=8024402B

    Any help will be more than appreciated.

    Thank you,

    Tom.

    Freitag, 14. Juni 2013 20:02

Antworten

  • 2013-06-09    00:17:02:989    1492    eb0    PT    Initializing simple targeting cookie, clientId = be185879-df4b-4595-8555-80a1bc59bb15, target group = , DNS name = wselmwood030.brydsongroup.com
    2013-06-09    00:17:02:989    1492    eb0    PT      Server URL = http://ELMFS1/SimpleAuthWebService/SimpleAuth.asmx
    2013-06-09    00:17:03:036    1492    eb0    PT    WARNING: GetAuthorizationCookie failure, error = 0x8024402B, soap client error = 10, soap error code = 0, HTTP status code = 499

    This is an unknown NOT-HTTP 200 return code, which suggests some issue with the web server. The fact that it's affecting 140/200 computers reinforces the probability that it's a server-side issue.

    Unfortunately, there's not much else we can infer from the provided information.

    My suggestion would be to review the IIS Logs for the website and see if they offer up any additional insight as to why IIS could not respond to the client's request.

    Also, some background on where/how you installed WSUS, and what else existed on that system prior to installing WSUS. Are you confident that the Web Server role was installed in compliance with the requirements for a WSUS server (as documented in the WSUS Deployment Guide)?


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Sonntag, 16. Juni 2013 15:59
    Moderator
  • Here is a snippet of one of my IIS logs. Not sure what to look for though as far as errors go. One of my problematic computers has an IP of 60.53 and I don't find it anywhere in the logs.

    The absence of any entries would be that this IIS log does not correspond to the time of the WindowsUpdate.log event. IIS logs are timestamped in GMT; the WindowsUpdate.log is timestamped in local time. The WindowsUpdate.log snippet is incomplete, in that it does not show the TZ of that client system, so you'll have to do the TZ arithmetic on your own to get the correct segment of IIS logs.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Montag, 17. Juni 2013 22:12
    Moderator
  • I was able to find the log entry.

    This is what it says:

    2013-06-14 19:05:16 192.168.60.143 GET / - 80 - 192.168.60.53 Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.1;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.04506.30;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729) 200 0 0 93
    2013-06-14 19:05:16 192.168.60.143 GET /welcome.png - 80 - 192.168.60.53 Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.1;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.04506.30;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729) 200 0 0 62
    2013-06-14 19:05:16 192.168.60.143 GET /favicon.ico - 80 - 192.168.60.53 Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.1;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.04506.30;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729) 404 0 2 46

    The only error in the above log segment, is an HTTP 404 trying to access an ICO file, which is not part of a Windows Update Agent event; although it did originate from 192.168.60.53. Neither of the other two (successful) entries are WUAgent events either.

    2013-06-14 19:05:52 fe80::5183:23f9:c40f:f84%10 POST /ClientWebService/Client.asmx - 80 - fe80::5183:23f9:c40f:f84%10 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.5466) 200 0 0 0

    The rest of the entries did not come from that client, they came from the WSUS server itself -- notice that the source and destination IPv6 addresses are identical.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Dienstag, 18. Juni 2013 19:01
    Moderator

Alle Antworten

  • 2013-06-09    00:17:02:989    1492    eb0    PT    Initializing simple targeting cookie, clientId = be185879-df4b-4595-8555-80a1bc59bb15, target group = , DNS name = wselmwood030.brydsongroup.com
    2013-06-09    00:17:02:989    1492    eb0    PT      Server URL = http://ELMFS1/SimpleAuthWebService/SimpleAuth.asmx
    2013-06-09    00:17:03:036    1492    eb0    PT    WARNING: GetAuthorizationCookie failure, error = 0x8024402B, soap client error = 10, soap error code = 0, HTTP status code = 499

    This is an unknown NOT-HTTP 200 return code, which suggests some issue with the web server. The fact that it's affecting 140/200 computers reinforces the probability that it's a server-side issue.

    Unfortunately, there's not much else we can infer from the provided information.

    My suggestion would be to review the IIS Logs for the website and see if they offer up any additional insight as to why IIS could not respond to the client's request.

    Also, some background on where/how you installed WSUS, and what else existed on that system prior to installing WSUS. Are you confident that the Web Server role was installed in compliance with the requirements for a WSUS server (as documented in the WSUS Deployment Guide)?


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Sonntag, 16. Juni 2013 15:59
    Moderator
  • Thanks for the reply Lawrence,

    The quick background:

    I have installed WSUS on a Windows 2012 Server from there I have two child connections one running windows 2008 and one running windows 2003. Also, one location has been setup for Branch Cache.

    I will look look back into the web server role. I can't be 100% sure it was installed with compliance. This is the link I used for preparing my WSUS install http://technet.microsoft.com/en-ca/windowsserver/bb332157.aspx

    On our network we have xp, vista, windows 7 computers of the roughly 200 computers only 59 are communicating.

    We previously had SCE installed which was removed.

    Here is a snippet of one of my IIS logs. Not sure what to look for though as far as errors go. One of my problematic computers has an IP of 60.53 and I don't find it anywhere in the logs.

    Thank you again.

    #Software: Microsoft Internet Information Services 7.5
    #Version: 1.0
    #Date: 2013-06-09 00:00:38
    #Fields: date time s-ip cs-method cs-uri-stem cs-uri-query s-port cs-username c-ip cs(User-Agent) sc-status sc-substatus sc-win32-status time-taken
    2013-06-09 00:00:38 192.168.60.143 POST /ReportingWebService/ReportingWebService.asmx - 80 - 192.168.60.112 Windows-Update-Agent 200 0 0 218
    2013-06-09 00:02:28 192.168.60.143 POST /ReportingWebService/ReportingWebService.asmx - 80 - 192.168.60.107 Windows-Update-Agent 200 0 0 140
    2013-06-09 00:02:38 192.168.60.143 POST /SimpleAuthWebService/SimpleAuth.asmx - 80 - 192.168.60.164 Windows-Update-Agent 200 0 0 0
    2013-06-09 00:02:38 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.164 Windows-Update-Agent 200 0 0 15
    2013-06-09 00:02:38 192.168.60.143 POST /ReportingWebService/ReportingWebService.asmx - 80 - 192.168.60.164 Windows-Update-Agent 200 0 0 140
    2013-06-09 00:03:14 fe80::5183:23f9:c40f:f84%10 GET /selfupdate/iuident.cab - 80 - fe80::5183:23f9:c40f:f84%10 - 200 0 0 0
    2013-06-09 00:03:14 fe80::5183:23f9:c40f:f84%10 GET /selfupdate/iuident.cab - 80 - fe80::5183:23f9:c40f:f84%10 - 200 0 0 62
    2013-06-09 00:03:14 fe80::5183:23f9:c40f:f84%10 POST /reportingwebservice/reportingwebservice.asmx - 80 - fe80::5183:23f9:c40f:f84%10 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.5466) 200 0 0 0
    2013-06-09 00:03:14 fe80::5183:23f9:c40f:f84%10 POST /ApiRemoting30/WebService.asmx - 80 BRYDSONGROUP\ELMFS1$ fe80::5183:23f9:c40f:f84%10 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.5466) 200 0 0 0
    2013-06-09 00:03:14 fe80::5183:23f9:c40f:f84%10 POST /ServerSyncWebService/serversyncwebservice.asmx - 80 - fe80::5183:23f9:c40f:f84%10 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.5466) 200 0 0 0
    2013-06-09 00:03:14 fe80::5183:23f9:c40f:f84%10 POST /ClientWebService/Client.asmx - 80 - fe80::5183:23f9:c40f:f84%10 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.5466) 200 0 0 0
    2013-06-09 00:03:14 fe80::5183:23f9:c40f:f84%10 POST /SimpleAuthWebService/SimpleAuth.asmx - 80 - fe80::5183:23f9:c40f:f84%10 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.5466) 200 0 0 0
    2013-06-09 00:03:14 fe80::5183:23f9:c40f:f84%10 POST /DssAuthWebService/DssAuthWebService.asmx - 80 - fe80::5183:23f9:c40f:f84%10 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.5466) 200 0 0 0
    2013-06-09 00:06:07 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.134 Windows-Update-Agent 200 0 0 46
    2013-06-09 00:06:07 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.134 Windows-Update-Agent 200 0 0 218
    2013-06-09 00:07:43 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.174 Windows-Update-Agent 200 0 0 31
    2013-06-09 00:07:43 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.174 Windows-Update-Agent 200 0 0 234
    2013-06-09 00:08:28 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.115 Windows-Update-Agent 200 0 0 31
    2013-06-09 00:08:28 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.115 Windows-Update-Agent 200 0 0 218
    2013-06-09 00:09:26 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.133 Windows-Update-Agent 200 0 0 46
    2013-06-09 00:09:26 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.133 Windows-Update-Agent 200 0 0 296
    2013-06-09 00:11:27 192.168.60.143 POST /SimpleAuthWebService/SimpleAuth.asmx - 80 - 192.168.60.136 Windows-Update-Agent 200 0 0 15
    2013-06-09 00:11:27 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.136 Windows-Update-Agent 200 0 0 46
    2013-06-09 00:11:27 192.168.60.143 POST /ReportingWebService/ReportingWebService.asmx - 80 - 192.168.60.136 Windows-Update-Agent 200 0 0 203
    2013-06-09 00:11:46 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.132 Windows-Update-Agent 200 0 0 31
    2013-06-09 00:11:46 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.132 Windows-Update-Agent 200 0 0 234
    2013-06-09 00:11:57 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.122 Windows-Update-Agent 200 0 0 31
    2013-06-09 00:11:57 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.122 Windows-Update-Agent 200 0 0 234
    2013-06-09 00:12:33 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.120 Windows-Update-Agent 200 0 0 31
    2013-06-09 00:12:33 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.120 Windows-Update-Agent 200 0 0 218
    2013-06-09 00:12:38 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.112 Windows-Update-Agent 200 0 0 31
    2013-06-09 00:12:38 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.112 Windows-Update-Agent 200 0 0 218
    2013-06-09 00:13:14 fe80::5183:23f9:c40f:f84%10 GET /selfupdate/iuident.cab - 80 - fe80::5183:23f9:c40f:f84%10 - 200 0 0 0
    2013-06-09 00:13:14 fe80::5183:23f9:c40f:f84%10 GET /selfupdate/iuident.cab - 80 - fe80::5183:23f9:c40f:f84%10 - 200 0 0 62
    2013-06-09 00:13:14 fe80::5183:23f9:c40f:f84%10 POST /reportingwebservice/reportingwebservice.asmx - 80 - fe80::5183:23f9:c40f:f84%10 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.5466) 200 0 0 0
    2013-06-09 00:13:14 fe80::5183:23f9:c40f:f84%10 POST /ApiRemoting30/WebService.asmx - 80 BRYDSONGROUP\ELMFS1$ fe80::5183:23f9:c40f:f84%10 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.5466) 200 0 0 0
    2013-06-09 00:13:14 fe80::5183:23f9:c40f:f84%10 POST /ServerSyncWebService/serversyncwebservice.asmx - 80 - fe80::5183:23f9:c40f:f84%10 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.5466) 200 0 0 0
    2013-06-09 00:13:14 fe80::5183:23f9:c40f:f84%10 POST /ClientWebService/Client.asmx - 80 - fe80::5183:23f9:c40f:f84%10 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.5466) 200 0 0 0
    2013-06-09 00:13:14 fe80::5183:23f9:c40f:f84%10 POST /SimpleAuthWebService/SimpleAuth.asmx - 80 - fe80::5183:23f9:c40f:f84%10 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.5466) 200 0 0 0
    2013-06-09 00:13:14 fe80::5183:23f9:c40f:f84%10 POST /DssAuthWebService/DssAuthWebService.asmx - 80 - fe80::5183:23f9:c40f:f84%10 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.5466) 200 0 0 0
    2013-06-09 00:13:21 192.168.60.143 POST /ReportingWebService/ReportingWebService.asmx - 80 - 192.168.60.132 Windows-Update-Agent 200 0 0 218
    2013-06-09 00:13:34 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.110 Windows-Update-Agent 200 0 0 31
    2013-06-09 00:13:34 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.110 Windows-Update-Agent 200 0 0 234
    2013-06-09 00:15:29 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.163 Windows-Update-Agent 200 0 0 31
    2013-06-09 00:15:29 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.163 Windows-Update-Agent 200 0 0 218
    2013-06-09 00:15:32 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.163 Windows-Update-Agent 200 0 0 234
    2013-06-09 00:15:37 192.168.60.143 POST /ReportingWebService/ReportingWebService.asmx - 80 - 192.168.60.134 Windows-Update-Agent 200 0 0 218
    2013-06-09 00:16:07 192.168.60.143 POST /SimpleAuthWebService/SimpleAuth.asmx - 80 - 192.168.60.112 Windows-Update-Agent 200 0 0 31
    2013-06-09 00:16:07 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.112 Windows-Update-Agent 200 0 0 31
    2013-06-09 00:16:07 192.168.60.143 POST /ReportingWebService/ReportingWebService.asmx - 80 - 192.168.60.112 Windows-Update-Agent 200 0 0 203
    2013-06-09 00:16:37 192.168.60.143 POST /ReportingWebService/ReportingWebService.asmx - 80 - 192.168.60.110 Windows-Update-Agent 200 0 0 203
    2013-06-09 00:16:47 192.168.60.143 POST /SimpleAuthWebService/SimpleAuth.asmx - 80 - 192.168.60.109 Windows-Update-Agent 200 0 0 31
    2013-06-09 00:16:47 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.109 Windows-Update-Agent 200 0 0 265
    2013-06-09 00:16:50 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.109 Windows-Update-Agent 200 0 0 31
    2013-06-09 00:16:50 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.109 Windows-Update-Agent 200 0 0 234
    2013-06-09 00:17:53 192.168.60.143 POST /SimpleAuthWebService/SimpleAuth.asmx - 80 - 192.168.60.115 Windows-Update-Agent 200 0 0 15
    2013-06-09 00:17:53 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.115 Windows-Update-Agent 200 0 0 31
    2013-06-09 00:17:53 192.168.60.143 POST /ReportingWebService/ReportingWebService.asmx - 80 - 192.168.60.115 Windows-Update-Agent 200 0 0 218
    2013-06-09 00:18:42 192.168.60.143 POST /SimpleAuthWebService/SimpleAuth.asmx - 80 - 192.168.60.133 Windows-Update-Agent 200 0 0 31
    2013-06-09 00:18:42 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.133 Windows-Update-Agent 200 0 0 15
    2013-06-09 00:18:42 192.168.60.143 POST /ReportingWebService/ReportingWebService.asmx - 80 - 192.168.60.133 Windows-Update-Agent 200 0 0 203
    2013-06-09 00:20:10 192.168.60.143 POST /SimpleAuthWebService/SimpleAuth.asmx - 80 - 192.168.60.174 Windows-Update-Agent 200 0 0 15
    2013-06-09 00:20:10 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.174 Windows-Update-Agent 200 0 0 31
    2013-06-09 00:20:10 192.168.60.143 POST /ReportingWebService/ReportingWebService.asmx - 80 - 192.168.60.174 Windows-Update-Agent 200 0 0 203
    2013-06-09 00:20:36 192.168.60.143 POST /ReportingWebService/ReportingWebService.asmx - 80 - 192.168.60.120 Windows-Update-Agent 200 0 0 218
    2013-06-09 00:20:53 192.168.60.143 POST /SimpleAuthWebService/SimpleAuth.asmx - 80 - 192.168.60.141 Windows-Update-Agent 200 0 0 15
    2013-06-09 00:20:53 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.141 Windows-Update-Agent 200 0 0 203
    2013-06-09 00:20:55 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.141 Windows-Update-Agent 200 0 0 15
    2013-06-09 00:20:55 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.141 Windows-Update-Agent 200 0 0 218
    2013-06-09 00:20:57 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.141 Windows-Update-Agent 200 0 0 203
    2013-06-09 00:21:08 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.106 Windows-Update-Agent 200 0 0 46
    2013-06-09 00:21:08 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.106 Windows-Update-Agent 200 0 0 203
    2013-06-09 00:21:14 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.141 Windows-Update-Agent 200 0 0 15
    2013-06-09 00:21:14 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.141 Windows-Update-Agent 200 0 0 203
    2013-06-09 00:21:16 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.141 Windows-Update-Agent 200 0 0 203
    2013-06-09 00:22:15 192.168.60.143 POST /ReportingWebService/ReportingWebService.asmx - 80 - 192.168.60.122 Windows-Update-Agent 200 0 0 218
    2013-06-09 00:23:14 fe80::5183:23f9:c40f:f84%10 GET /selfupdate/iuident.cab - 80 - fe80::5183:23f9:c40f:f84%10 - 200 0 0 0
    2013-06-09 00:23:14 fe80::5183:23f9:c40f:f84%10 GET /selfupdate/iuident.cab - 80 - fe80::5183:23f9:c40f:f84%10 - 200 0 0 62
    2013-06-09 00:23:14 fe80::5183:23f9:c40f:f84%10 POST /reportingwebservice/reportingwebservice.asmx - 80 - fe80::5183:23f9:c40f:f84%10 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.5466) 200 0 0 0
    2013-06-09 00:23:14 fe80::5183:23f9:c40f:f84%10 POST /ApiRemoting30/WebService.asmx - 80 BRYDSONGROUP\ELMFS1$ fe80::5183:23f9:c40f:f84%10 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.5466) 200 0 0 15
    2013-06-09 00:23:14 fe80::5183:23f9:c40f:f84%10 POST /ServerSyncWebService/serversyncwebservice.asmx - 80 - fe80::5183:23f9:c40f:f84%10 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.5466) 200 0 0 0
    2013-06-09 00:23:14 fe80::5183:23f9:c40f:f84%10 POST /ClientWebService/Client.asmx - 80 - fe80::5183:23f9:c40f:f84%10 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.5466) 200 0 0 0
    2013-06-09 00:23:14 fe80::5183:23f9:c40f:f84%10 POST /SimpleAuthWebService/SimpleAuth.asmx - 80 - fe80::5183:23f9:c40f:f84%10 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.5466) 200 0 0 0
    2013-06-09 00:23:14 fe80::5183:23f9:c40f:f84%10 POST /DssAuthWebService/DssAuthWebService.asmx - 80 - fe80::5183:23f9:c40f:f84%10 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.5466) 200 0 0 0
    2013-06-09 00:23:49 192.168.60.143 POST /SimpleAuthWebService/SimpleAuth.asmx - 80 - 192.168.60.163 Windows-Update-Agent 200 0 0 15
    2013-06-09 00:23:49 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.163 Windows-Update-Agent 200 0 0 31
    2013-06-09 00:23:49 192.168.60.143 POST /ReportingWebService/ReportingWebService.asmx - 80 - 192.168.60.163 Windows-Update-Agent 200 0 0 218
    2013-06-09 00:24:40 192.168.60.143 POST /ReportingWebService/ReportingWebService.asmx - 80 - 192.168.60.109 Windows-Update-Agent 200 0 0 218
    2013-06-09 00:25:07 192.168.60.143 POST /SimpleAuthWebService/SimpleAuth.asmx - 80 - 192.168.60.176 Windows-Update-Agent 200 0 0 15
    2013-06-09 00:25:07 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.176 Windows-Update-Agent 200 0 0 156
    2013-06-09 00:25:08 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.176 Windows-Update-Agent 200 0 0 15
    2013-06-09 00:25:08 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.176 Windows-Update-Agent 200 0 0 218
    2013-06-09 00:25:10 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.176 Windows-Update-Agent 200 0 0 171
    2013-06-09 00:25:29 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.176 Windows-Update-Agent 200 0 0 15
    2013-06-09 00:25:29 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.176 Windows-Update-Agent 200 0 0 187
    2013-06-09 00:25:31 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.176 Windows-Update-Agent 200 0 0 187
    2013-06-09 00:26:32 192.168.60.143 POST /SimpleAuthWebService/SimpleAuth.asmx - 80 - 192.168.60.106 Windows-Update-Agent 200 0 0 31
    2013-06-09 00:26:32 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.106 Windows-Update-Agent 200 0 0 250
    2013-06-09 00:26:32 192.168.60.143 POST /ReportingWebService/ReportingWebService.asmx - 80 - 192.168.60.106 Windows-Update-Agent 200 0 0 390
    2013-06-09 00:27:55 192.168.60.143 POST /ReportingWebService/ReportingWebService.asmx - 80 - 192.168.60.141 Windows-Update-Agent 200 0 0 234
    2013-06-09 00:28:22 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.117 Windows-Update-Agent 200 0 0 31
    2013-06-09 00:28:22 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.117 Windows-Update-Agent 200 0 0 234
    2013-06-09 00:29:40 192.168.60.143 HEAD /selfupdate/wuident.cab 1306090029 80 - 192.168.60.198 Windows-Update-Agent 200 0 0 203
    2013-06-09 00:29:40 192.168.60.143 HEAD /selfupdate/WSUS3/x86/Vista/wsus3setup.cab 1306090029 80 - 192.168.60.198 Windows-Update-Agent 200 0 0 203
    2013-06-09 00:29:44 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.198 Windows-Update-Agent 200 0 0 125
    2013-06-09 00:29:44 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.198 Windows-Update-Agent 200 0 0 218
    2013-06-09 00:29:55 192.168.60.143 HEAD /selfupdate/wuident.cab 1306090029 80 - 192.168.60.169 Windows-Update-Agent 200 0 0 140
    2013-06-09 00:29:55 192.168.60.143 HEAD /selfupdate/WSUS3/x86/Vista/wsus3setup.cab 1306090029 80 - 192.168.60.169 Windows-Update-Agent 200 0 0 203
    2013-06-09 00:29:59 192.168.60.143 POST /SimpleAuthWebService/SimpleAuth.asmx - 80 - 192.168.60.169 Windows-Update-Agent 200 0 0 15
    2013-06-09 00:29:59 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.169 Windows-Update-Agent 200 0 0 218
    2013-06-09 00:30:04 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.169 Windows-Update-Agent 200 0 0 31
    2013-06-09 00:30:04 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.169 Windows-Update-Agent 200 0 0 218
    2013-06-09 00:33:14 fe80::5183:23f9:c40f:f84%10 GET /selfupdate/iuident.cab - 80 - fe80::5183:23f9:c40f:f84%10 - 200 0 0 0
    2013-06-09 00:33:14 fe80::5183:23f9:c40f:f84%10 GET /selfupdate/iuident.cab - 80 - fe80::5183:23f9:c40f:f84%10 - 200 0 0 62
    2013-06-09 00:33:14 fe80::5183:23f9:c40f:f84%10 POST /reportingwebservice/reportingwebservice.asmx - 80 - fe80::5183:23f9:c40f:f84%10 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.5466) 200 0 0 0
    2013-06-09 00:33:14 fe80::5183:23f9:c40f:f84%10 POST /ApiRemoting30/WebService.asmx - 80 BRYDSONGROUP\ELMFS1$ fe80::5183:23f9:c40f:f84%10 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.5466) 200 0 0 0
    2013-06-09 00:33:14 fe80::5183:23f9:c40f:f84%10 POST /ServerSyncWebService/serversyncwebservice.asmx - 80 - fe80::5183:23f9:c40f:f84%10 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.5466) 200 0 0 0
    2013-06-09 00:33:14 fe80::5183:23f9:c40f:f84%10 POST /ClientWebService/Client.asmx - 80 - fe80::5183:23f9:c40f:f84%10 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.5466) 200 0 0 0
    2013-06-09 00:33:14 fe80::5183:23f9:c40f:f84%10 POST /SimpleAuthWebService/SimpleAuth.asmx - 80 - fe80::5183:23f9:c40f:f84%10 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.5466) 200 0 0 0
    2013-06-09 00:33:14 fe80::5183:23f9:c40f:f84%10 POST /DssAuthWebService/DssAuthWebService.asmx - 80 - fe80::5183:23f9:c40f:f84%10 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.5466) 200 0 0 0
    2013-06-09 00:33:50 192.168.60.143 POST /ReportingWebService/ReportingWebService.asmx - 80 - 192.168.60.169 Windows-Update-Agent 200 0 0 218
    2013-06-09 00:34:39 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.198 Windows-Update-Agent 200 0 0 46
    2013-06-09 00:34:39 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.198 Windows-Update-Agent 200 0 0 234
    2013-06-09 00:35:44 192.168.60.143 POST /ReportingWebService/ReportingWebService.asmx - 80 - 192.168.60.176 Windows-Update-Agent 200 0 0 203
    2013-06-09 00:36:45 192.168.60.143 POST /SimpleAuthWebService/SimpleAuth.asmx - 80 - 192.168.60.198 Windows-Update-Agent 200 0 0 46
    2013-06-09 00:36:45 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.198 Windows-Update-Agent 200 0 0 140
    2013-06-09 00:36:45 192.168.60.143 POST /ReportingWebService/ReportingWebService.asmx - 80 - 192.168.60.198 Windows-Update-Agent 200 0 0 234
    2013-06-09 00:38:32 192.168.60.143 POST /SimpleAuthWebService/SimpleAuth.asmx - 80 - 192.168.60.138 Windows-Update-Agent 200 0 0 0
    2013-06-09 00:38:32 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.138 Windows-Update-Agent 200 0 0 171
    2013-06-09 00:39:48 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.150 Windows-Update-Agent 200 0 0 46
    2013-06-09 00:39:48 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.150 Windows-Update-Agent 200 0 0 203
    2013-06-09 00:40:33 192.168.60.143 HEAD /selfupdate/wuident.cab 1306090040 80 - 192.168.60.141 Windows-Update-Agent 200 0 0 187
    2013-06-09 00:40:41 192.168.60.143 POST /ReportingWebService/ReportingWebService.asmx - 80 - 192.168.60.117 Windows-Update-Agent 200 0 0 218
    2013-06-09 00:40:41 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.141 Windows-Update-Agent 200 0 0 15
    2013-06-09 00:40:42 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.141 Windows-Update-Agent 200 0 0 203
    2013-06-09 00:40:45 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.141 Windows-Update-Agent 200 0 0 203
    2013-06-09 00:40:54 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.138 Windows-Update-Agent 200 0 0 31
    2013-06-09 00:40:54 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.138 Windows-Update-Agent 200 0 0 171
    2013-06-09 00:42:00 192.168.60.143 POST /ReportingWebService/ReportingWebService.asmx - 80 - 192.168.60.150 Windows-Update-Agent 200 0 0 218
    2013-06-09 00:42:08 192.168.60.143 POST /SimpleAuthWebService/SimpleAuth.asmx - 80 - 192.168.60.59 Windows-Update-Agent 200 0 0 0
    2013-06-09 00:42:08 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.59 Windows-Update-Agent 200 0 0 203
    2013-06-09 00:42:11 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.59 Windows-Update-Agent 200 0 0 31
    2013-06-09 00:42:11 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.59 Windows-Update-Agent 200 0 0 187
    2013-06-09 00:42:31 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.59 Windows-Update-Agent 200 0 0 125
    2013-06-09 00:43:14 fe80::5183:23f9:c40f:f84%10 GET /selfupdate/iuident.cab - 80 - fe80::5183:23f9:c40f:f84%10 - 200 0 0 0
    2013-06-09 00:43:14 fe80::5183:23f9:c40f:f84%10 GET /selfupdate/iuident.cab - 80 - fe80::5183:23f9:c40f:f84%10 - 200 0 0 62
    2013-06-09 00:43:14 fe80::5183:23f9:c40f:f84%10 POST /reportingwebservice/reportingwebservice.asmx - 80 - fe80::5183:23f9:c40f:f84%10 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.5466) 200 0 0 0
    2013-06-09 00:43:14 fe80::5183:23f9:c40f:f84%10 POST /ApiRemoting30/WebService.asmx - 80 BRYDSONGROUP\ELMFS1$ fe80::5183:23f9:c40f:f84%10 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.5466) 200 0 0 0
    2013-06-09 00:43:14 fe80::5183:23f9:c40f:f84%10 POST /ServerSyncWebService/serversyncwebservice.asmx - 80 - fe80::5183:23f9:c40f:f84%10 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.5466) 200 0 0 0
    2013-06-09 00:43:14 fe80::5183:23f9:c40f:f84%10 POST /ClientWebService/Client.asmx - 80 - fe80::5183:23f9:c40f:f84%10 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.5466) 200 0 0 0
    2013-06-09 00:43:14 fe80::5183:23f9:c40f:f84%10 POST /SimpleAuthWebService/SimpleAuth.asmx - 80 - fe80::5183:23f9:c40f:f84%10 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.5466) 200 0 0 0
    2013-06-09 00:43:14 fe80::5183:23f9:c40f:f84%10 POST /DssAuthWebService/DssAuthWebService.asmx - 80 - fe80::5183:23f9:c40f:f84%10 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.5466) 200 0 0 0
    2013-06-09 00:44:00 192.168.60.143 HEAD /selfupdate/wuident.cab 1306090043 80 - 192.168.60.122 Windows-Update-Agent 200 0 0 93
    2013-06-09 00:44:00 192.168.60.143 HEAD /selfupdate/WSUS3/x86/Vista/wsus3setup.cab 1306090044 80 - 192.168.60.122 Windows-Update-Agent 200 0 0 218
    2013-06-09 00:44:02 192.168.60.143 POST /SimpleAuthWebService/SimpleAuth.asmx - 80 - 192.168.60.122 Windows-Update-Agent 200 0 0 15
    2013-06-09 00:44:02 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.122 Windows-Update-Agent 200 0 0 218
    2013-06-09 00:44:03 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.122 Windows-Update-Agent 200 0 0 31
    2013-06-09 00:44:03 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.122 Windows-Update-Agent 200 0 0 218
    2013-06-09 00:47:34 192.168.60.143 POST /ReportingWebService/ReportingWebService.asmx - 80 - 192.168.60.141 Windows-Update-Agent 200 0 0 203
    2013-06-09 00:48:01 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.138 Windows-Update-Agent 200 0 0 171
    2013-06-09 00:50:51 192.168.60.143 POST /ReportingWebService/ReportingWebService.asmx - 80 - 192.168.60.59 Windows-Update-Agent 200 0 0 203
    2013-06-09 00:52:56 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.164 Windows-Update-Agent 200 0 0 15
    2013-06-09 00:52:56 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.164 Windows-Update-Agent 200 0 0 203
    2013-06-09 00:52:58 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.164 Windows-Update-Agent 200 0 0 156
    2013-06-09 00:53:14 fe80::5183:23f9:c40f:f84%10 GET /selfupdate/iuident.cab - 80 - fe80::5183:23f9:c40f:f84%10 - 200 0 0 0
    2013-06-09 00:53:14 fe80::5183:23f9:c40f:f84%10 GET /selfupdate/iuident.cab - 80 - fe80::5183:23f9:c40f:f84%10 - 200 0 0 62
    2013-06-09 00:53:14 fe80::5183:23f9:c40f:f84%10 POST /reportingwebservice/reportingwebservice.asmx - 80 - fe80::5183:23f9:c40f:f84%10 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.5466) 200 0 0 0
    2013-06-09 00:53:14 fe80::5183:23f9:c40f:f84%10 POST /ApiRemoting30/WebService.asmx - 80 BRYDSONGROUP\ELMFS1$ fe80::5183:23f9:c40f:f84%10 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.5466) 200 0 0 0
    2013-06-09 00:53:14 fe80::5183:23f9:c40f:f84%10 POST /ServerSyncWebService/serversyncwebservice.asmx - 80 - fe80::5183:23f9:c40f:f84%10 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.5466) 200 0 0 0
    2013-06-09 00:53:14 fe80::5183:23f9:c40f:f84%10 POST /ClientWebService/Client.asmx - 80 - fe80::5183:23f9:c40f:f84%10 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.5466) 200 0 0 0
    2013-06-09 00:53:14 fe80::5183:23f9:c40f:f84%10 POST /SimpleAuthWebService/SimpleAuth.asmx - 80 - fe80::5183:23f9:c40f:f84%10 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.5466) 200 0 0 0
    2013-06-09 00:53:14 fe80::5183:23f9:c40f:f84%10 POST /DssAuthWebService/DssAuthWebService.asmx - 80 - fe80::5183:23f9:c40f:f84%10 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.5466) 200 0 0 0
    2013-06-09 00:53:18 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.164 Windows-Update-Agent 200 0 0 31
    2013-06-09 00:53:18 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.164 Windows-Update-Agent 200 0 0 125
    2013-06-09 00:53:18 192.168.60.143 POST /ClientWebService/client.asmx - 80 - 192.168.60.164 Windows-Update-Agent 200 0 0 187
    2013-06-09 00:54:21 192.168.60.143 POST /ReportingWebService/ReportingWebService.asmx - 80 - 192.168.60.122 Windows-Update-Agent 200 0 0 203

    Montag, 17. Juni 2013 16:02
  • Here is a snippet of one of my IIS logs. Not sure what to look for though as far as errors go. One of my problematic computers has an IP of 60.53 and I don't find it anywhere in the logs.

    The absence of any entries would be that this IIS log does not correspond to the time of the WindowsUpdate.log event. IIS logs are timestamped in GMT; the WindowsUpdate.log is timestamped in local time. The WindowsUpdate.log snippet is incomplete, in that it does not show the TZ of that client system, so you'll have to do the TZ arithmetic on your own to get the correct segment of IIS logs.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Montag, 17. Juni 2013 22:12
    Moderator
  • Now that I am looking into it further. I have noticed that the computers configured in the GPO to connect to my 2003 server are all reporting fine. It is just the ones pointing to the 2008 and 2012 that are the issue. Of those two, only the 2008 has computers reporting to it, albeit not all computers.

    I will check all the logs to see if I can find.

    Thanks again for the info.

    Dienstag, 18. Juni 2013 14:08
  • Sorry Lawrence one quick question. Do I need an SSL Certificate for my 2008 and 2012 Servers? or can I get by without them.

    Tom.

    Dienstag, 18. Juni 2013 14:13
  • I was able to find the log entry.

    This is what it says:

    2013-06-14 19:05:16 192.168.60.143 GET / - 80 - 192.168.60.53 Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.1;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.04506.30;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729) 200 0 0 93
    2013-06-14 19:05:16 192.168.60.143 GET /welcome.png - 80 - 192.168.60.53 Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.1;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.04506.30;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729) 200 0 0 62
    2013-06-14 19:05:16 192.168.60.143 GET /favicon.ico - 80 - 192.168.60.53 Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.1;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.04506.30;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729) 404 0 2 46
    2013-06-14 19:05:52 fe80::5183:23f9:c40f:f84%10 GET /selfupdate/iuident.cab - 80 - fe80::5183:23f9:c40f:f84%10 - 200 0 0 0
    2013-06-14 19:05:52 fe80::5183:23f9:c40f:f84%10 GET /selfupdate/iuident.cab - 80 - fe80::5183:23f9:c40f:f84%10 - 200 0 0 62
    2013-06-14 19:05:52 fe80::5183:23f9:c40f:f84%10 POST /reportingwebservice/reportingwebservice.asmx - 80 - fe80::5183:23f9:c40f:f84%10 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.5466) 200 0 0 0
    2013-06-14 19:05:52 fe80::5183:23f9:c40f:f84%10 POST /ApiRemoting30/WebService.asmx - 80 BRYDSONGROUP\ELMFS1$ fe80::5183:23f9:c40f:f84%10 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.5466) 200 0 0 15
    2013-06-14 19:05:52 fe80::5183:23f9:c40f:f84%10 POST /ServerSyncWebService/serversyncwebservice.asmx - 80 - fe80::5183:23f9:c40f:f84%10 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.5466) 200 0 0 0
    2013-06-14 19:05:52 fe80::5183:23f9:c40f:f84%10 POST /ClientWebService/Client.asmx - 80 - fe80::5183:23f9:c40f:f84%10 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.5466) 200 0 0 0
    2013-06-14 19:05:52 fe80::5183:23f9:c40f:f84%10 POST /SimpleAuthWebService/SimpleAuth.asmx - 80 - fe80::5183:23f9:c40f:f84%10 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.5466) 200 0 0 0
    2013-06-14 19:05:52 fe80::5183:23f9:c40f:f84%10 POST /DssAuthWebService/DssAuthWebService.asmx - 80 - fe80::5183:23f9:c40f:f84%10 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.5466) 200 0 0 0

    Dienstag, 18. Juni 2013 14:42
  • Do I need an SSL Certificate for my 2008 and 2012 Servers?

    Only if you want/need to use SSL. :-)

    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Dienstag, 18. Juni 2013 18:53
    Moderator
  • I was able to find the log entry.

    This is what it says:

    2013-06-14 19:05:16 192.168.60.143 GET / - 80 - 192.168.60.53 Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.1;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.04506.30;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729) 200 0 0 93
    2013-06-14 19:05:16 192.168.60.143 GET /welcome.png - 80 - 192.168.60.53 Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.1;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.04506.30;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729) 200 0 0 62
    2013-06-14 19:05:16 192.168.60.143 GET /favicon.ico - 80 - 192.168.60.53 Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.1;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.04506.30;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729) 404 0 2 46

    The only error in the above log segment, is an HTTP 404 trying to access an ICO file, which is not part of a Windows Update Agent event; although it did originate from 192.168.60.53. Neither of the other two (successful) entries are WUAgent events either.

    2013-06-14 19:05:52 fe80::5183:23f9:c40f:f84%10 POST /ClientWebService/Client.asmx - 80 - fe80::5183:23f9:c40f:f84%10 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.5466) 200 0 0 0

    The rest of the entries did not come from that client, they came from the WSUS server itself -- notice that the source and destination IPv6 addresses are identical.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Dienstag, 18. Juni 2013 19:01
    Moderator