W2K, WinXP clients are not communicating with WSUS 3.0
JWEllis
1 Started out with SUS 1.0
2 Upgraded to WSUS 2.0
3 Upgraded to WSUS 3.0
4 Server removed from Domain & joined to workgroup
5 WSUS 3.0 stopped working
6 Tried to reinstall WSUS 3.0. Program tried to uninstall but failed.
Could not do anything else after that.
7 Performed Fresh Install of OS, SP1
8 Attempted restore from tape with System State. Got HAL error upon
reboot.
9 Did fresh installation of OS with SP2, IIS & WSUS 3.0
10 Server successfully synchs with upstream and downstream servers. Local
clients howerver are getting 0x80244008 errors.
11/7/2007 15:08:07:359 884 a18 PT +++++++++++ PT: Synchronizing server
updates +++++++++++
11/7/2007 15:08:07:359 884 a18 PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://tcoslsadmin/ClientWebService/client.asmx
11/7/2007 15:08:11:109 884 a18 PT WARNING: SyncUpdates failure, error =
0x80244008, soap client error = 8, soap error code = 0, HTTP status code = 200
11/7/2007 15:08:11:109 884 a18 PT WARNING: PTError: 0x80244008
11/7/2007 15:08:11:109 884 a18 PT WARNING: SyncUpdates_WithRecovery
failed.: 0x80244008
11/7/2007 15:08:11:109 884 a18 PT WARNING: Sync of Updates: 0x80244008
11/7/2007 15:08:11:109 884 a18 PT WARNING: SyncServerUpdatesInternal
failed: 0x80244008
11/7/2007 15:08:11:109 884 a18 Agent * WARNING: Failed to synchronize,
error = 0x80244008
11/7/2007 15:08:11:109 884 a18 Agent * WARNING: Exit code = 0x80244008
11 When I change the Windows Update Intranet server on TCOSLSADMIN to
Go-SL-MSUPD, its upstream server, it successfully communicates to this server
without the above error.
11/7/2007 14:55:49:390 884 a8c Agent * WSUS server: http://go-sl-msupd
11/7/2007 14:55:49:390 884 a8c Agent * WSUS status server:
http://go-sl-msupd
11/7/2007 14:55:49:390 884 a8c Agent * Target group: (Unassigned Computers)
11/7/2007 14:55:49:390 884 a8c Agent * Windows Update access disabled: No
11/7/2007 14:55:49:390 884 a8c DnldMgr Download manager restoring 0 downloads
11/7/2007 14:55:49:406 884 a8c AU ########### AU: Initializing Automatic
Updates ###########
11/7/2007 14:55:49:406 884 a8c AU AU setting next detection timeout to
2007-11-07 19:55:49
11/7/2007 14:55:49:406 884 a8c AU # WSUS server: http://go-sl-msupd
11/7/2007 14:55:49:406 884 a8c AU # Detection frequency: 22
11/7/2007 14:55:49:406 884 a8c AU # Approval type: Pre-install notify
(Policy)
11/7/2007 14:55:49:406 884 a8c AU # Auto-install minor updates: No (User
preference)
11/7/2007 14:55:49:406 884 a8c AU AU finished delayed initialization
11/7/2007 14:55:49:406 884 a8c AU Triggering AU detection through DetectNow
API
11/7/2007 14:55:49:406 884 a8c AU Triggering Online detection
(non-interactive)
11/7/2007 14:55:49:468 884 53c Report *********** Report: Initializing
static reporting data ***********
11/7/2007 14:55:49:468 884 53c Report * OS Version = 5.2.3790.2.0.196880
11/7/2007 14:55:49:546 884 53c Report * Computer Brand = UNISYS Corp.
11/7/2007 14:55:49:546 884 53c Report * Computer Model = ES3020
11/7/2007 14:55:49:546 884 53c Report * Bios Revision = A10
11/7/2007 14:55:49:546 884 53c Report * Bios Name = Phoenix ROM BIOS PLUS
Version 1.10 A10
11/7/2007 14:55:49:546 884 53c Report * Bios Release Date =
2003-10-14T00:00:00
11/7/2007 14:55:49:546 884 53c Report * Locale ID = 1033
11/7/2007 14:55:49:562 884 53c AU #############
11/7/2007 14:55:49:562 884 53c AU ## START ## AU: Search for updates
11/7/2007 14:55:49:562 884 53c AU #########
11/7/2007 14:55:49:562 884 53c AU <<## SUBMITTED ## AU: Search for updates
[CallId = {F718C94F-55C7-47BB-B7B7-0099E2818C57}]
11/7/2007 14:55:51:890 884 f74 PT WARNING: Cached cookie has expired or new
PID is available
11/7/2007 14:55:51:890 884 f74 PT Initializing simple targeting cookie,
clientId = a7670531-144d-4bae-b927-382f9f18f061, target group = , DNS name =
tcoslsadmin
11/7/2007 14:55:51:890 884 f74 PT Server URL =
http://go-sl-msupd/SimpleAuthWebService/SimpleAuth.asmx
11/7/2007 14:55:53:375 884 f74 Report Uploading 3 events using cached
cookie, reporting URL =
http://go-sl-msupd/ReportingWebService/ReportingWebService.asmx
11/7/2007 14:55:54:437 884 f74 Report Reporter successfully uploaded 3
events.
11/7/2007 14:55:54:515 884 f74 Report Uploading 1 events using cached
cookie, reporting URL =
http://go-sl-msupd/ReportingWebService/ReportingWebService.asmx
11/7/2007 14:55:54:531 884 f74 Report Reporter successfully uploaded 1
events.
11/7/2007 14:55:54:625 884 f74 Report Uploading 1 events using cached
cookie, reporting URL =
http://go-sl-msupd/ReportingWebService/ReportingWebService.asmx
11/7/2007 14:55:54:640 884 f74 Report Reporter successfully uploaded 1
events.
11/7/2007 14:55:54:734 884 f74 Report Uploading 1 events using cached
cookie, reporting URL =
http://go-sl-msupd/ReportingWebService/ReportingWebService.asmx
11/7/2007 14:55:54:750 884 f74 Report Reporter successfully uploaded 1
events.
11/7/2007 14:55:54:828 884 f74 Report Uploading 1 events using cached
cookie, reporting URL =
http://go-sl-msupd/ReportingWebService/ReportingWebService.asmx
11/7/2007 14:55:54:843 884 f74 Report Reporter successfully uploaded 1
events.
11/7/2007 14:55:54:921 884 f74 Report Uploading 1 events using cached
cookie, reporting URL =
http://go-sl-msupd/ReportingWebService/ReportingWebService.asmx
11/7/2007 14:55:54:937 884 f74 Report Reporter successfully uploaded 1
events.
11/7/2007 14:55:54:937 884 f74 Agent *************
11/7/2007 14:55:54:937 884 f74 Agent ** START ** Agent: Finding updates
[CallerId = AutomaticUpdates]
11/7/2007 14:55:54:937 884 f74 Agent *********
11/7/2007 14:55:54:937 884 f74 Agent * Online = Yes; Ignore download
priority = No
11/7/2007 14:55:54:937 884 f74 Agent * Criteria = "IsHidden=0 and
IsInstalled=0 and DeploymentAction='Installation' and IsAssigned=1 or
IsHidden=0 and IsPresent=1 and DeploymentAction='Uninstallation' and
IsAssigned=1 or IsHidden=0 and IsInstalled=1 and
DeploymentAction='Installation' and IsAssigned=1 and RebootRequired=1 or
IsHidden=0 and IsInstalled=0 and DeploymentAction='Uninstallation' and
IsAssigned=1 and RebootRequired=1"
11/7/2007 14:55:54:937 884 f74 Agent * ServiceID =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
11/7/2007 14:55:54:937 884 f74 Misc Validating signature for
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wuident.cab:
11/7/2007 14:55:54:968 884 f74 Misc Microsoft signed: Yes
11/7/2007 14:55:54:968 884 f74 Misc Validating signature for
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wuident.cab:
11/7/2007 14:55:54:984 884 f74 Misc Microsoft signed: Yes
11/7/2007 14:55:55:015 884 f74 Misc Validating signature for
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wsus3setup.cab:
11/7/2007 14:55:55:031 884 f74 Misc Microsoft signed: Yes
11/7/2007 14:55:55:031 884 f74 Setup *********** Setup: Checking whether
self-update is required ***********
11/7/2007 14:55:55:031 884 f74 Setup * Inf file:
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wsus3setup.inf
11/7/2007 14:55:55:046 884 f74 Setup Update NOT required for
C:\WINDOWS\system32\cdm.dll: target version = 7.0.6000.374, required version
= 7.0.6000.374
11/7/2007 14:55:55:046 884 f74 Setup Update NOT required for
C:\WINDOWS\system32\wuapi.dll: target version = 7.0.6000.374, required
version = 7.0.6000.374
11/7/2007 14:55:55:046 884 f74 Setup Update NOT required for
C:\WINDOWS\system32\wuapi.dll.mui: target version = 7.0.6000.374, required
version = 7.0.6000.374
11/7/2007 14:55:55:046 884 f74 Setup Update NOT required for
C:\WINDOWS\system32\wuauclt.exe: target version = 7.0.6000.374, required
version = 7.0.6000.374
11/7/2007 14:55:55:046 884 f74 Setup Update NOT required for
C:\WINDOWS\system32\wuaucpl.cpl: target version = 7.0.6000.374, required
version = 7.0.6000.374
11/7/2007 14:55:55:046 884 f74 Setup Update NOT required for
C:\WINDOWS\system32\wuaucpl.cpl.mui: target version = 7.0.6000.374, required
version = 7.0.6000.374
11/7/2007 14:55:55:046 884 f74 Setup Update NOT required for
C:\WINDOWS\system32\wuaueng.dll: target version = 7.0.6000.374, required
version = 7.0.6000.374
11/7/2007 14:55:55:046 884 f74 Setup Update NOT required for
C:\WINDOWS\system32\wuaueng.dll.mui: target version = 7.0.6000.374, required
version = 7.0.6000.374
11/7/2007 14:55:55:046 884 f74 Setup Update NOT required for
C:\WINDOWS\system32\wucltui.dll: target version = 7.0.6000.374, required
version = 7.0.6000.374
11/7/2007 14:55:55:046 884 f74 Setup Update NOT required for
C:\WINDOWS\system32\wucltui.dll.mui: target version = 7.0.6000.374, required
version = 7.0.6000.374
11/7/2007 14:55:55:046 884 f74 Setup Update NOT required for
C:\WINDOWS\system32\wups.dll: target version = 7.0.6000.374, required version
= 7.0.6000.374
11/7/2007 14:55:55:046 884 f74 Setup Update NOT required for
C:\WINDOWS\system32\wups2.dll: target version = 7.0.6000.374, required
version = 7.0.6000.374
11/7/2007 14:55:55:046 884 f74 Setup Update NOT required for
C:\WINDOWS\system32\wuweb.dll: target version = 7.0.6000.374, required
version = 7.0.6000.374
11/7/2007 14:55:55:046 884 f74 Setup * IsUpdateRequired = No
11/7/2007 14:55:55:218 884 f74 PT +++++++++++ PT: Synchronizing server
updates +++++++++++
11/7/2007 14:55:55:218 884 f74 PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://go-sl-msupd/ClientWebService/client.asmx
11/7/2007 14:56:12:343 884 f74 PT +++++++++++ PT: Synchronizing extended
update info +++++++++++
11/7/2007 14:56:12:343 884 f74 PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://go-sl-msupd/ClientWebService/client.asmx
11/7/2007 14:56:16:734 884 f74 Agent * Found 0 updates and 35 categories
in search; evaluated appl. rules of 355 out of 436 deployed entities
11/7/2007 14:56:16:734 884 f74 Agent *********
11/7/2007 14:56:16:734 884 f74 Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
11/7/2007 14:56:16:734 884 f74 Agent *************
11/7/2007 14:56:16:750 884 fe8 AU >>## RESUMED ## AU: Search for updates
[CallId = {F718C94F-55C7-47BB-B7B7-0099E2818C57}]
11/7/2007 14:56:16:750 884 fe8 AU # 0 updates detected
11/7/2007 14:56:16:750 884 fe8 AU #########
11/7/2007 14:56:16:750 884 fe8 AU ## END ## AU: Search for updates
[CallId = {F718C94F-55C7-47BB-B7B7-0099E2818C57}]
11/7/2007 14:56:16:750 884 fe8 AU #############
11/7/2007 14:56:16:750 884 fe8 AU AU setting next detection timeout to
2007-11-08 15:22:44
11/7/2007 14:56:21:734 884 f74 Report REPORT EVENT:
{46DC648D-6C5E-4F12-A895-A0ED849C268A}
11/7/2007 14:56:21:734 884 f74 Report REPORT EVENT:
{4F8A06B1-D6EA-40DD-9F3D-849787EF43CD}
11/7/2007 15:06:40:125 884 f74 Report Uploading 2 events using cached
cookie, reporting URL =
http://go-sl-msupd/ReportingWebService/ReportingWebService.asmx
11/7/2007 15:06:40:156 884 f74 Report Reporter successfully uploaded 2
events.
11/7/2007 15:07:07:890 884 53c AU ########### AU: Uninitializing Automatic
Updates ###########
11/7/2007 15:07:07:937 884 53c Service *********
11/7/2007 15:07:07:937 884 53c Service ** END ** Service: Service exit
[Exit code = 0x240001]
11/7/2007 15:07:07:937 884 53c Service *************
12 Verified the file versions for the files below are at least beyound the
level identified for SP2 which contains a fix for a previous issue similar to
the one being encounterd at this time.
date time version size file name
2/18/2007 7:00 AM 5.2.3790.3959 285 KB http.sys
2/18/2007 7:00 AM 6.2.29.0 363 KB updspapi.dll
13 Verified the directory security permissions and settings are according to
the parameters identified in the WSUS setup guides.
Lawrence Garvin [MVP]
news:EF8D0F34-82A3-42A2...@microsoft.com...
> Environment History.
> 1 Started out with SUS 1.0
> 2 Upgraded to WSUS 2.0
> 3 Upgraded to WSUS 3.0
Without reading further at this point, unless you performed this unreported
Step2a
2a. Completed uninstallation of SUS 1.0
> 4 Server removed from Domain & joined to workgroup
> 5 WSUS 3.0 stopped working
Actually... it's likely that WSUS 3.0 was never working at all.
> 6 Tried to reinstall WSUS 3.0. Program tried to uninstall but failed.
> Could not do anything else after that.
Basically a result of the failure to fully uninstall SUS 1.0.
> 9 Did fresh installation of OS with SP2, IIS & WSUS 3.0
Thus eliminating the remnants of the SUS 1.0 installation...
> 10 Server successfully synchs with upstream and downstream servers. Local
> clients howerver are getting 0x80244008 errors.
> {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
> http://tcoslsadmin/ClientWebService/client.asmx
> 11/7/2007 15:08:11:109 884 a18 PT WARNING: SyncUpdates failure, error =
> 0x80244008, soap client error = 8, soap error code = 0, HTTP status code =
> 200
0x80244008 - SUS E PT SOAPCLIENT PARSEFAULT
> 11 When I change the Windows Update Intranet server on TCOSLSADMIN to
> Go-SL-MSUPD, its upstream server, it successfully communicates to this
> server
> without the above error.
Suggesting there is a fault in the TCOSLSADMIN server installation, since a
fault anywhere else would continue to manifest this error.
And... based on your "...upstream and downstream servers..." statement
above... did you mean downstream CLIENTS,
or is TCOSLSADMIN a mid-stream server in a three-server-deep heirarchy?
> 11/7/2007 14:55:51:890 884 f74 PT Initializing simple targeting cookie,
> clientId = a7670531-144d-4bae-b927-382f9f18f061, target group = , DNS name
> =
> tcoslsadmin
Oh.... you forgot to mention that the *CLIENT* and the *SERVER* are the same
system!
At least, that's where the logfile seems to have come from.
Is TCOSLSADMIN a *replica* of GO-SL-MSUPD, or just an autonomous downstream
server?
Please reset the URLs to http://tcoslsadmin and run the Client Diagnostic
Tool on TCOSLSADMIN
and post the results.
--
Lawrence Garvin, M.S., MCTS, MCP
MVP - Software Distribution (2005-2007)
MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
JWEllis
deinstalled WSUS 1.0 as required and the restore from tape attempt with
system state was at a point after WSUS 3.0 had been installed onto the
server. The timeline for the SUS 1.0 and WSUS 2.0 happened well before I
came upon the scene so I do not have a lot of information regarding what
actually transpired for those events.
I did look at the registry keys to see if any residual SUS 1.0 keys were
left over but I did not see any. I also look to see if I could find any
documentation on what a fresh installation of WSUS 3.0 registry keys should
contain but could not find any online. I did verify that the IIS
Permissions, Scripts, directory security, etc. were in accordance with the
docmumentation provided for WSUS 3.0, except for the APIReporting30 directory
which appears to have changed since the docuementation was created.
I worked with Microsoft Tech Support last Friday trying everything short of
flattening the box and rebuilding it from scratch, blowing out WSUS 3.0 with
the MSI deinstallation tool, R&R IIS, .NET 2.0, etc. and reinstalling
everything from scratch and running the .NET verifier tool, MSREPORTS tool
and anthing else we could think of that might point us in the right
direction. We believe that something got corrupted during the 'system state'
restore and subsequent repair of the OS that isn't showing up in any
diagnostic routines that we can pinpoint.
After all this we are back to where we were. The box syncs fine with its
upstream and downstream servers but not with its clients. This is a bit
better than where it was when it didn't work at all...but not much.
Our next plan of action is to 'flatten' the system drive and do a complete
fresh installation unless someone can think of another method we can try that
may resolve the issue.
Lawrence Garvin [MVP]
> When I originally had upgraded the systems to WSUS 3.0 from 2.0 I had
> deinstalled WSUS 1.0 as required
Excellent -- although the symptoms reported contradict this. :-\
> Our next plan of action is to 'flatten' the system drive and do a complete
> fresh installation unless someone can think of another method we can try
> that
> may resolve the issue.
The truth is that the SUS 1.0 uninstaller fails to remove the SUS 1.0
catalog from the root of the DWS, and the presence of that catalog file
appears to have caused issues with successfully upgrading to WSUS 3.0 in at
least one other incident I can recall.
Could you please inventory the list of filenames in the root of the Default
Web Server and post them here. (I can't remember the specific name of the
file(s), but I'll recognize them when I see them, if they're still there.)
--
Lawrence Garvin, M.S., MCTS, MCP
Senior Data Architect, APQC, Houston, Texas
JWEllis
pass all the test and show the version number of Wuaueng.dll to be associated
with WSUS 2.0...
C:\Program Files\Update Services\Tools>clientdiag
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 7.0.6000.381. . . . . . . . . . . . PASS
This version is WSUS 2.0
Checking AU Settings
AU Option is 3 : Notify Prior to 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. . . . . . . . . . . . . . . . . NONE
User IE ProxyByPass. . . . . . . . . . . . . . NONE
User IE AutoConfig URL Proxy . . . . . . . . . NONE
User IE AutoDetect
AutoDetect not in use
Checking Connection to WSUS/SUS Server
WUServer = http://tcoslsadmin
WUStatusServer = http://tcoslsadmin
UseWuServer is enabled. . . . . . . . . . . . . . . . . PASS
Connection to server. . . . . . . . . . . . . . . . . . PASS
SelfUpdate folder is present. . . . . . . . . . . . . . PASS
Press Enter to Complete
The following client diagnostic is from a 2nd client machine
C:\Program Files>clientdiag
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 7.0.6000.374. . . . . . . . . . . . PASS
This version is WSUS 2.0
Checking AU Settings
AU Option is 3 : Notify Prior to 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. . . . . . . . . . . . . . . . . NONE
User IE ProxyByPass. . . . . . . . . . . . . . NONE
User IE AutoConfig URL Proxy . . . . . . . . . NONE
User IE AutoDetect
AutoDetect not in use
Checking Connection to WSUS/SUS Server
WUServer = http://tcoslsadmin
WUStatusServer = http://tcoslsadmin
UseWuServer is enabled. . . . . . . . . . . . . . . . . PASS
Connection to server. . . . . . . . . . . . . . . . . . PASS
SelfUpdate folder is present. . . . . . . . . . . . . . PASS
Press Enter to Complete
C:\Program Files>
Lawrence Garvin [MVP]
> Here is the Client Diagnostic from the server itself and a 2nd machine.
> Both
> pass all the test and show the version number of Wuaueng.dll to be
> associated
> with WSUS 2.0...
Yes.. this is a non-sequiter -- ignore this anomaly. The CDT was written for
the WUA v5.x product. It is totally obliviuos to version numbers beyond 5.x.
All it knows is if the version number is < 5.4.3790.1000 then "The version
is SUS 1.0"; otherwise it reports all newer versions as "WSUS 2.0".
As noted, there is no flaw with the CDT output on the server, nor this
client machine.
This confirms that nothing in the =configuration= of the WUA, or the WSUS
Server, appears to be at fault.
However, if you're still receiving 0x80244008 errors, then you'll want to
chase down that error code.
A Google search on the code shows one possible error is that the
ClientWebService virtual directory does not have the correct application
configuration settings.
Open IIS - Click Default Web Site - Right Click Client Web Service -
Properties - In the Application Settings, In the Application name, click
Create.
Test this url:
http://tcoslsadmin/clientwebservice/client.asmx
You should get back a simple web page listing the services available.
Another case example involves the WSUS Server being configured to use
complex passwords, which may interfere with the proper creation of
WSUS-required accounts and/or group membership assignments, specifically the
ASPNET machine account.
See this thread for details on the above two items:
http://www.wsus.info/forums/lofiversion/index.php?t5896.html
Other notes suggest that proxy servers and firewalls could impact the WUA
talking to WU/MU, so it makes sense that it could also impact the WUA trying
to talk to a WSUS Server. The WUA uses anonymous access to use the HTTP
resources on the WSUS Server. If the proxy server/firewall requires
authentication for HTTP requests, this connection could fail.
And, in general, if there's been any customization of the ASP.NET
environment on the WSUS Server, that could be a contributing factor.
--
Lawrence Garvin, M.S., MCTS, MCP
Senior Data Architect, APQC, Houston, Texas
JWEllis
'http://tcoslsadmin/clientwebservice/client.asmx' URL.
I ran the .NET 2.0 verifier program against the box to ensure it has the
latest versions and hotfixes. Even removed and reinstalled .NET and .ASP
portions per Microsofts guidelines.
There are no Proxy machines in this environment as all clients connect on
the same subnet to the WSUS server. I verified the Anonymous Access was
configured per the MS guidelines for WSUS 3.0.
So I ended up rebuiliding the OS portion of this server and then
reinstalling the WSUS 3.0 services from scratch which has resolved the
problem.
I appreciate you willingness to share your vast knowlege on this product and
have gain some valuable insight into this product. Thanks.