When set to Detect Only, clients search WAN instead of WSUS server

Discussion in 'Update Services' started by Jeff, Mar 20, 2007.

  1. Jeff

    Jeff Guest

    I have a downstream WSUS server with 106 clients. When the upstream server
    sets the updates to Detect Only rather than Install, the clients create lots
    of WAN traffic. All the settings pointing to the WSUS server are correct on
    the client. They are set in Group Policy through Novell Zenworks. I'm
    guessing that the clients know the updates are needed, but can't get them
    from WSUS since it's set to Detect Only, so they try to get them from
    Microsoft's site. The only WAN traffic recorded in the WSUS log occurs when
    the client is trying to get a cookie. It fails to get a cookie from the WSUS
    server and then gets it from microsoft's website:

    2007-03-18 20:45:54 1140 494 PT Initializing simple targeting cookie,
    clientId = f710be11-6fe6-4316-8e18-7e8856f50a41, target group = , DNS name =
    tzw610.cc.sunywcc.edu
    2007-03-18 20:45:54 1140 494 PT Server URL =
    http://cc-enterprise2/SimpleAuthWebService/SimpleAuth.asmx
    2007-03-18 20:46:07 1140 494 PT WARNING: GetCookie failure, error =
    0x8024400D, soap client error = 7, soap error code = 300, HTTP status code =
    200
    2007-03-18 20:46:07 1140 494 PT WARNING: SOAP Fault: 0x00012c
    2007-03-18 20:46:07 1140 494 PT WARNING: faultstring:Fault occurred
    2007-03-18 20:46:07 1140 494 PT WARNING: ErrorCode:ConfigChanged(2)
    2007-03-18 20:46:07 1140 494 PT WARNING: Message:

    2007-03-18 20:46:07 1140 494 PT WARNING:
    Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/GetCookie"
    2007-03-18 20:46:07 1140 494 PT WARNING:
    ID:b198525e-d19c-41f0-a5b9-33b83fa8f390
    2007-03-18 20:46:07 1140 494 PT Initializing simple targeting cookie,
    clientId = f710be11-6fe6-4316-8e18-7e8856f50a41, target group = , DNS name =
    tzw610.cc.sunywcc.edu


    Does anyone know how to stop this WAN traffic from occurring?

    Thanks, Jeff
     
    Jeff, Mar 20, 2007
    #1
    1. Advertisements

  2. Just for reference sake. The volume of data traffic between the WUA and the
    WSUS Server during a detection event (not including downloading), should be
    exactly the same regardless of whether an update is set to "Detect Only" or
    "Install".

    An increase in traffic will be seen for Needed updates, as the update
    content will then be downloaded when detected after being marked as approved
    for installation.
    This guess would be fundamentally inaccurate. A client configured to talk to
    a WSUS server will =never= talk to microsoft.com via "Automatic Updates".
    And, unless you're not maintaining a local content store on your WSUS
    server, the client will never talk to microsoft.com directly, at all!
    No.. it doesn't..and if it does this, then the client is either grossly
    misconfigured (policy/registry), or you're misreading your network trace. As
    noted above, a client properly configured to talk to a WSUS server will
    =never= initiate communications with microsoft.com, except to download
    =content= in the instance where the WSUS server does not maintain a local
    content store.


    So.. now that we've talked about all the things that are NOT happening on
    your system, let's talk about what is.
    [1] This client does not have target group information. This can be caused
    by any one of the following:
    [a] The policy is not configured to enable client-side targeting, thus
    no target group membership is applied via policy.
    Client-side targeting is being used, is properly configured, but the
    WUA has a cached targeting cookie, and thus has not obtained updated
    client-side target group membership information.
    [c] Server-side targeting is being used, and the client is still a
    member of the Unassigned Computers target group.
    [d] Server-side targeting is being used, the client has been assigned a
    new target group at the WSUS Console, but the WUA has a cached targeting
    cookie, and thus has not obtained updated server-side target group
    membership information.

    Regardless of the actual cause, the remediation is essentially the same:
    [a] Ensure the policy is configured correctly.
    Ensure the policy is applied correctly.
    [c] Ensure the WSUS Server is configured correctly. (Client-side
    targeting requires a server-side options change.)
    [d] Ensure the target group exists on the WSUS Server.
    [e] Ensure the client is populated into the correct target group on the
    WSUS Server if using server-side targeting.
    [f] Run 'wuauclt /resetauthorization /detectnow' on the client to purge
    the existing targeting cookie and obtain updated targeting data.

    The 0x8024400D error, in association with the SOAP Fault 0x12c, is discussed
    in these links, and has been traced to a couple of different possible
    causes:
    http://www.wsuswiki.com/AgentFailedDetecting0x8024400d
    http://www.wsuswiki.com/SOAPFault0x00012c

    Significantly missing from your incomplete log segment is any information
    which would indicate the actual version of the WUA running on this cleint,
    which would also imply the version of WSUS you're running on your WSUS
    server. Both of these questions are relevant to these issues.
    I do, however, acknowledge, this log entry, which I've never before seen.
    So, perhaps, in order to put all in perspective, with the correct reference,
    we should properly establish the versioning of your environment, so that we
    can identify the proper and expected behaviors of the WUA in this scenario.
    In short... fixing the broken data communications between this client and
    the WSUS server seems to be the most appropriate objective.

    --
    Lawrence Garvin, M.S., MCTS, MCP
    Independent WSUS Evangelist
    MVP-Software Distribution (2005-2007)
    https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E

    Everything you need for WSUS is at
    http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx

    And, almost everything else is at
    http://wsusinfo.onsitechsolutions.com
    .....
     
    Lawrence Garvin \(MVP\), Mar 23, 2007
    #2
    1. Advertisements

  3. Jeff

    Jeff Guest

    Here's the log for the full detection cycle for the events described below.
    (I did try the fixes described in
    http://www.wsuswiki.com/AgentFailedDetecting0x8024400d and
    http://www.wsuswiki.com/SOAPFault0x00012c and they didn't work.)

    2007-03-18 20:45:37 1140 14c AU #############
    2007-03-18 20:45:37 1140 14c AU ## START ## AU: Search for updates
    2007-03-18 20:45:37 1140 14c AU #########
    2007-03-18 20:45:37 1140 14c AU <<## SUBMITTED ## AU: Search for updates
    [CallId = {BEA06ED1-1961-46EF-BD16-1C5E2FE7D511}]
    2007-03-18 20:45:37 1140 494 Agent *************
    2007-03-18 20:45:37 1140 494 Agent ** START ** Agent: Finding updates
    [CallerId = AutomaticUpdates]
    2007-03-18 20:45:37 1140 494 Agent *********
    2007-03-18 20:45:49 1140 494 Setup *********** Setup: Checking whether
    self-update is required ***********
    2007-03-18 20:45:49 1140 494 Setup * Inf file:
    C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wusetup.inf
    2007-03-18 20:45:49 1140 494 Setup Update NOT required for
    C:\WINDOWS\system32\cdm.dll: target version = 5.8.0.2607, required version =
    5.8.0.2607
    2007-03-18 20:45:49 1140 494 Setup Update NOT required for
    C:\WINDOWS\system32\iuengine.dll: target version = 5.8.0.2607, required
    version = 5.8.0.2607
    2007-03-18 20:45:49 1140 494 Setup Update NOT required for
    C:\WINDOWS\system32\wuapi.dll: target version = 5.8.0.2607, required version
    = 5.8.0.2607
    2007-03-18 20:45:49 1140 494 Setup Update NOT required for
    C:\WINDOWS\system32\wuauclt.exe: target version = 5.8.0.2607, required
    version = 5.8.0.2607
    2007-03-18 20:45:49 1140 494 Setup Update NOT required for
    C:\WINDOWS\system32\wuauclt1.exe: target version = 5.8.0.2607, required
    version = 5.8.0.2607
    2007-03-18 20:45:49 1140 494 Setup Update NOT required for
    C:\WINDOWS\system32\wuaucpl.cpl: target version = 5.8.0.2607, required
    version = 5.8.0.2607
    2007-03-18 20:45:49 1140 494 Setup Update NOT required for
    C:\WINDOWS\system32\wuaueng.dll: target version = 5.8.0.2607, required
    version = 5.8.0.2607
    2007-03-18 20:45:49 1140 494 Setup Update NOT required for
    C:\WINDOWS\system32\wuaueng1.dll: target version = 5.8.0.2607, required
    version = 5.8.0.2607
    2007-03-18 20:45:49 1140 494 Setup Update NOT required for
    C:\WINDOWS\system32\wucltui.dll: target version = 5.8.0.2607, required
    version = 5.8.0.2607
    2007-03-18 20:45:49 1140 494 Setup Update NOT required for
    C:\WINDOWS\system32\wups.dll: target version = 5.8.0.2607, required version =
    5.8.0.2607
    2007-03-18 20:45:49 1140 494 Setup Update NOT required for
    C:\WINDOWS\system32\wups2.dll: target version = 5.8.0.2607, required version
    = 5.8.0.2607
    2007-03-18 20:45:49 1140 494 Setup Update NOT required for
    C:\WINDOWS\system32\wuweb.dll: target version = 5.8.0.2607, required version
    = 5.8.0.2607
    2007-03-18 20:45:49 1140 494 Setup * IsUpdateRequired = No
    2007-03-18 20:45:54 1140 494 PT +++++++++++ PT: Synchronizing server
    updates +++++++++++
    2007-03-18 20:45:54 1140 494 PT + ServiceId =
    {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
    http://cc-enterprise2/ClientWebService/client.asmx
    2007-03-18 20:45:54 1140 494 PT Initializing simple targeting cookie,
    clientId = f710be11-6fe6-4316-8e18-7e8856f50a41, target group = , DNS name =
    tzw610.cc.sunywcc.edu
    2007-03-18 20:45:54 1140 494 PT Server URL =
    http://cc-enterprise2/SimpleAuthWebService/SimpleAuth.asmx
    2007-03-18 20:46:07 1140 494 PT WARNING: GetCookie failure, error =
    0x8024400D, soap client error = 7, soap error code = 300, HTTP status code =
    200
    2007-03-18 20:46:07 1140 494 PT WARNING: SOAP Fault: 0x00012c
    2007-03-18 20:46:07 1140 494 PT WARNING: faultstring:Fault occurred
    2007-03-18 20:46:07 1140 494 PT WARNING: ErrorCode:ConfigChanged(2)
    2007-03-18 20:46:07 1140 494 PT WARNING: Message:

    2007-03-18 20:46:07 1140 494 PT WARNING:
    Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/GetCookie"
    2007-03-18 20:46:07 1140 494 PT WARNING:
    ID:b198525e-d19c-41f0-a5b9-33b83fa8f390
    2007-03-18 20:46:07 1140 494 PT Initializing simple targeting cookie,
    clientId = f710be11-6fe6-4316-8e18-7e8856f50a41, target group = , DNS name =
    tzw610.cc.sunywcc.edu
    2007-03-18 20:46:07 1140 494 PT Server URL =
    http://cc-enterprise2/SimpleAuthWebService/SimpleAuth.asmx
    2007-03-18 20:46:44 1140 494 PT +++++++++++ PT: Synchronizing extended
    update info +++++++++++
    2007-03-18 20:46:44 1140 494 PT + ServiceId =
    {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
    http://cc-enterprise2/ClientWebService/client.asmx
    2007-03-18 20:46:52 1140 494 Agent * Found 0 updates and 12 categories in
    search
    2007-03-18 20:46:52 1140 494 Agent *********
    2007-03-18 20:46:52 1140 494 Agent ** END ** Agent: Finding updates
    [CallerId = AutomaticUpdates]
    2007-03-18 20:46:52 1140 494 Agent *************
    2007-03-18 20:46:52 1140 494 AU >>## RESUMED ## AU: Search for updates
    [CallId = {BEA06ED1-1961-46EF-BD16-1C5E2FE7D511}]
    2007-03-18 20:46:52 1140 494 AU # 0 updates detected
    2007-03-18 20:46:52 1140 494 AU #########
    2007-03-18 20:46:52 1140 494 AU ## END ## AU: Search for updates [CallId
    = {BEA06ED1-1961-46EF-BD16-1C5E2FE7D511}]
    2007-03-18 20:46:52 1140 494 AU #############
    2007-03-18 20:46:52 1140 494 AU AU setting next detection timeout to
    2007-03-19 19:30:27
    2007-03-18 20:46:57 1140 494 Report REPORT EVENT:
    {A921C7C6-5ABA-45D6-A0A5-CA816B4079B8} 2007-03-18
    20:46:52-0400 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Agent has finished detecting items.
    2007-03-18 20:46:57 1140 494 Report REPORT EVENT:
    {5FB959C5-B5BE-4560-A138-58F8D4D84036} 2007-03-18
    20:46:52-0400 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
    2007-03-18 20:50:23 1140 488 Report Uploading 2 events using cached cookie,
    reporting URL =
    http://cc-enterprise2/ReportingWebService/ReportingWebService.asmx
    2007-03-18 20:50:25 1140 488 Report Reporter successfully uploaded 2 events.



     
    Jeff, Mar 23, 2007
    #3
  4. Jeff

    Jeff Guest

    My situation was as described in 1C below: "Server-side targeting is being
    used, and the client is still a member of the Unassigned Computers target
    group." I set up client side targeting for a few test computers and followed
    the steps a to f below. I also tried the fixes described in
    http://www.wsuswiki.com/AgentFailedDetecting0x8024400d and
    http://www.wsuswiki.com/SOAPFault0x00012c and they didn't work. The errors
    and WAN traffic have not stopped. Does any one have any suggestions?

    2007-03-27 23:07:58 1148 490 PT Initializing simple targeting cookie,
    clientId = f710be11-6fe6-4316-8e18-7e8856f50a41, target group = Cross County,
    DNS name = tzw610.cc.sunywcc.edu
    2007-03-27 23:07:58 1148 490 PT Server URL =
    http://cc-enterprise2/SimpleAuthWebService/SimpleAuth.asmx
    2007-03-27 23:08:11 1148 490 PT WARNING: GetCookie failure, error =
    0x8024400D, soap client error = 7, soap error code = 300, HTTP status code =
    200
    2007-03-27 23:08:11 1148 490 PT WARNING: SOAP Fault: 0x00012c
    2007-03-27 23:08:11 1148 490 PT WARNING: faultstring:Fault occurred
    2007-03-27 23:08:11 1148 490 PT WARNING: ErrorCode:ConfigChanged(2)
    2007-03-27 23:08:11 1148 490 PT WARNING: Message:

    2007-03-27 23:08:11 1148 490 PT WARNING:
    Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/GetCookie"
    2007-03-27 23:08:11 1148 490 PT WARNING:
    ID:89869745-ee8e-467f-af2b-fc77512392f3
    2007-03-27 23:08:11 1148 490 PT Initializing simple targeting cookie,
    clientId = f710be11-6fe6-4316-8e18-7e8856f50a41, target group = Cross County,
    DNS name = tzw610.cc.sunywcc.edu
    2007-03-27 23:08:11 1148 490 PT Server URL =
    http://cc-enterprise2/SimpleAuthWebService/SimpleAuth.asmx



     
    Jeff, Mar 28, 2007
    #4
  5. [Repeating from the previous reply]:
    If you can post the log entries for the entire detection event, through the
    completion of the reporting event, that would be helpful.

    There's not much I can deduce from the entries provided here.

    --
    Lawrence Garvin, M.S., MCTS, MCP
    Independent WSUS Evangelist
    MVP-Software Distribution (2005-2007)
    https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E

    Everything you need for WSUS is at
    http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx

    And, almost everything else is at
    http://wsusinfo.onsitechsolutions.com
    .....
     
    Lawrence Garvin \(MVP\), Mar 29, 2007
    #5
  6. Jeff

    Jeff Guest

    Here's the log entries for the entire reporting event. Please tell me is
    there's anything you can figure out that would stop the GetCookie Failures
    and the WAN traffic.
    Thanks.


    2007-03-27 23:07:39 1148 a98 AU #############
    2007-03-27 23:07:39 1148 a98 AU ## START ## AU: Search for updates
    2007-03-27 23:07:39 1148 a98 AU #########
    2007-03-27 23:07:39 1148 a98 AU <<## SUBMITTED ## AU: Search for updates
    [CallId = {E52F90A2-3D9B-4D55-A892-CFA9795446C6}]
    2007-03-27 23:07:39 1148 490 Agent *************
    2007-03-27 23:07:39 1148 490 Agent ** START ** Agent: Finding updates
    [CallerId = AutomaticUpdates]
    2007-03-27 23:07:39 1148 490 Agent *********
    2007-03-27 23:07:52 1148 490 Setup *********** Setup: Checking whether
    self-update is required ***********
    2007-03-27 23:07:52 1148 490 Setup * Inf file:
    C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wusetup.inf
    2007-03-27 23:07:52 1148 490 Setup Update NOT required for
    C:\WINDOWS\system32\cdm.dll: target version = 5.8.0.2607, required version =
    5.8.0.2607
    2007-03-27 23:07:52 1148 490 Setup Update NOT required for
    C:\WINDOWS\system32\iuengine.dll: target version = 5.8.0.2607, required
    version = 5.8.0.2607
    2007-03-27 23:07:52 1148 490 Setup Update NOT required for
    C:\WINDOWS\system32\wuapi.dll: target version = 5.8.0.2607, required version
    = 5.8.0.2607
    2007-03-27 23:07:52 1148 490 Setup Update NOT required for
    C:\WINDOWS\system32\wuauclt.exe: target version = 5.8.0.2607, required
    version = 5.8.0.2607
    2007-03-27 23:07:52 1148 490 Setup Update NOT required for
    C:\WINDOWS\system32\wuauclt1.exe: target version = 5.8.0.2607, required
    version = 5.8.0.2607
    2007-03-27 23:07:52 1148 490 Setup Update NOT required for
    C:\WINDOWS\system32\wuaucpl.cpl: target version = 5.8.0.2607, required
    version = 5.8.0.2607
    2007-03-27 23:07:52 1148 490 Setup Update NOT required for
    C:\WINDOWS\system32\wuaueng.dll: target version = 5.8.0.2607, required
    version = 5.8.0.2607
    2007-03-27 23:07:52 1148 490 Setup Update NOT required for
    C:\WINDOWS\system32\wuaueng1.dll: target version = 5.8.0.2607, required
    version = 5.8.0.2607
    2007-03-27 23:07:52 1148 490 Setup Update NOT required for
    C:\WINDOWS\system32\wucltui.dll: target version = 5.8.0.2607, required
    version = 5.8.0.2607
    2007-03-27 23:07:52 1148 490 Setup Update NOT required for
    C:\WINDOWS\system32\wups.dll: target version = 5.8.0.2607, required version =
    5.8.0.2607
    2007-03-27 23:07:52 1148 490 Setup Update NOT required for
    C:\WINDOWS\system32\wups2.dll: target version = 5.8.0.2607, required version
    = 5.8.0.2607
    2007-03-27 23:07:52 1148 490 Setup Update NOT required for
    C:\WINDOWS\system32\wuweb.dll: target version = 5.8.0.2607, required version
    = 5.8.0.2607
    2007-03-27 23:07:52 1148 490 Setup * IsUpdateRequired = No
    2007-03-27 23:07:57 1148 490 PT +++++++++++ PT: Synchronizing server
    updates +++++++++++
    2007-03-27 23:07:57 1148 490 PT + ServiceId =
    {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
    http://cc-enterprise2/ClientWebService/client.asmx
    2007-03-27 23:07:58 1148 490 PT Initializing simple targeting cookie,
    clientId = f710be11-6fe6-4316-8e18-7e8856f50a41, target group = Cross County,
    DNS name = tzw610.cc.sunywcc.edu
    2007-03-27 23:07:58 1148 490 PT Server URL =
    http://cc-enterprise2/SimpleAuthWebService/SimpleAuth.asmx
    2007-03-27 23:08:11 1148 490 PT WARNING: GetCookie failure, error =
    0x8024400D, soap client error = 7, soap error code = 300, HTTP status code =
    200
    2007-03-27 23:08:11 1148 490 PT WARNING: SOAP Fault: 0x00012c
    2007-03-27 23:08:11 1148 490 PT WARNING: faultstring:Fault occurred
    2007-03-27 23:08:11 1148 490 PT WARNING: ErrorCode:ConfigChanged(2)
    2007-03-27 23:08:11 1148 490 PT WARNING: Message:

    2007-03-27 23:08:11 1148 490 PT WARNING:
    Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/GetCookie"
    2007-03-27 23:08:11 1148 490 PT WARNING:
    ID:89869745-ee8e-467f-af2b-fc77512392f3
    2007-03-27 23:08:11 1148 490 PT Initializing simple targeting cookie,
    clientId = f710be11-6fe6-4316-8e18-7e8856f50a41, target group = Cross County,
    DNS name = tzw610.cc.sunywcc.edu
    2007-03-27 23:08:11 1148 490 PT Server URL =
    http://cc-enterprise2/SimpleAuthWebService/SimpleAuth.asmx
    2007-03-27 23:08:55 1148 490 PT +++++++++++ PT: Synchronizing extended
    update info +++++++++++
    2007-03-27 23:08:55 1148 490 PT + ServiceId =
    {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
    http://cc-enterprise2/ClientWebService/client.asmx
    2007-03-27 23:09:03 1148 490 Agent * Found 0 updates and 12 categories in
    search
    2007-03-27 23:09:03 1148 490 Agent *********
    2007-03-27 23:09:03 1148 490 Agent ** END ** Agent: Finding updates
    [CallerId = AutomaticUpdates]
    2007-03-27 23:09:03 1148 490 Agent *************
    2007-03-27 23:09:03 1148 490 AU >>## RESUMED ## AU: Search for updates
    [CallId = {E52F90A2-3D9B-4D55-A892-CFA9795446C6}]
    2007-03-27 23:09:03 1148 490 AU # 0 updates detected
    2007-03-27 23:09:03 1148 490 AU #########
    2007-03-27 23:09:03 1148 490 AU ## END ## AU: Search for updates [CallId
    = {E52F90A2-3D9B-4D55-A892-CFA9795446C6}]
    2007-03-27 23:09:03 1148 490 AU #############
    2007-03-27 23:09:03 1148 490 AU AU setting next detection timeout to
    2007-03-28 23:18:34
    2007-03-27 23:09:08 1148 490 Report REPORT EVENT:
    {A28E8F88-B36D-4FCB-9566-7CCBFA4D90F6} 2007-03-27
    23:09:03-0400 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Agent has finished detecting items.
    2007-03-27 23:09:08 1148 490 Report REPORT EVENT:
    {495FC3A0-5F9F-4F67-B08B-18ECD2C2885E} 2007-03-27
    23:09:03-0400 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
    2007-03-27 23:20:29 1148 50c Report Uploading 2 events using cached cookie,
    reporting URL =
    http://cc-enterprise2/ReportingWebService/ReportingWebService.asmx
    2007-03-27 23:20:31 1148 50c Report Reporter successfully uploaded 2 events.

     
    Jeff, Mar 29, 2007
    #6
  7. Jeff

    Jeff Guest

    Does anyone have any ideas on this? The problem is still occurring. I have
    posted the entire reporting event as requested. Any advice would be greatly
    appreciated.
    Thanks, Jeff

     
    Jeff, Apr 5, 2007
    #7
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.