Getauthorizationcookie Failure Error 0x8024401b
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) Home20132010Other VersionsLibraryForumsGallery Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: WSUS Clients Not Receiving Updates Windows Server > WSUS Question 0 Sign winhttp proxy authentication in to vote Hi,I have approximately 60 clients which connect to a netsh winhttp set proxy username password machine running WSUS 3.0 SP1. The OS is Server 2003 R2 SP2. This machine is also used for managing windows proxy authentication ForeFront clients. The box also has the ForeFront client installed on it. This was clean install and has no other purpose other than WSUS and Forefront. It had been functioning without problems since March 08 when it was commissioned.Over the past couple of month machines have stopped communicating with the WSUS day range from 29 to 59 days without communication.Around the time the machines stopped around the time the machines stopped communicating we introduced a proxy server. However WSUS is able to download updates and machines are able to access the machine using the URL: Http://ForeFront and Http://ForeFront/SimpleAuthWebService/SimpleAuth.asmx. Displaying "SimpleAuth The following operations are supported. For a formal definition, please review the Service Description. GetAuthorizationCookie Ping " I found information at one forum which suggested IIS authentication problems which I have addressed. (See link below)http://www.wsus.info/forums/lofiversion/index.php?t5928.htmlI have also run the Client Diagnose Tool with the following results. 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.1.6001.65 . . . . . . . . . . . . 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
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > A Server (2008 R2) that won't connect to WSUS - Proxy Connection issues Want to Advertise Here? Solved A Server (2008 R2) that won't connect to WSUS - Proxy Connection issues https://social.technet.microsoft.com/Forums/office/en-US/8c394712-cf95-449f-bb0a-14679a2ebe9e/wsus-clients-not-receiving-updates?forum=winserverwsus Posted on 2012-11-20 Windows Server 2008 Windows Server 2003 MS Server OS 1 Verified Solution 25 Comments 8,700 Views Last Modified: 2013-02-17 We have a number of servers we monitor, and its been brought to my attention that a couple of the servers have not been communicating with WSUS. I'm looking at the one that has been offline according to WSUS for a lot https://www.experts-exchange.com/questions/27942703/A-Server-2008-R2-that-won't-connect-to-WSUS-Proxy-Connection-issues.html longer. I got into the windowsupdate.log (and below is a section of the log) and the error messages direct me to tell me there is something wrong with the proxy authentication. I must be missing something here because I go into Internet Options and the settings are correct. I'm able to browse the internet. I'm also able to browse internal websites, including those on the WSUS server. I see in the logs that it also has the correct Proxy server address, and it uses port 8080 which is what our proxy server uses. What am I missing? 2012-11-21 14:13:39:209 7756 1e20 Misc =========== Logging initialized (build: 7.6.7600.256, tz: +1300) =========== 2012-11-21 14:13:39:209 7756 1e20 Misc = Process: C:\Windows\system32\svchost.exe 2012-11-21 14:13:39:209 7756 1e20 Misc = Module: c:\windows\system32\wuaueng.dll 2012-11-21 14:13:39:209 7756 1e20 Service ************* 2012-11-21 14:13:39:209 7756 1e20 Service ** START ** Service: Service startup 2012-11-21 14:13:39:209 7756 1e20 Service ********* 2012-11-21 14:13:39:211 7756 1e20 Agent * WU client version 7.6.7600.256 2012-11-21 14:13:39:211 7756 1e20 Agent * Base directory: C:\Windows\SoftwareDistribution 2012-11-21 14:13:39:211 7756 1e20 Agent * Access type: Named proxy 2012-11-21 14:13:39:211 7756 1e20 Agent * Default proxy: http=mpgw1:8080;https=mpgw1:8080 2012-11-21 14:13:39:2
routers SCCM Client SUM Agent and http error 407 (Proxy Authentication Required) error in WU Agent Email Details Category: Microsoft SCCM 2007 Created: 02 May 2010 Last Updated: 24 November 2013 Hits: http://www.hermanvandrie.nl/index.php/microsoft-systemcenter/3-microsoft-sccm-2007/8-sccm-client-sum-agent-sets-wuserver-to-uppercase-causes-http-error-407-proxy-authentication-required-error-in-wu-agent 8536 User Rating:0/5Please Rate Vote 1 Vote 2 Vote 3 Vote 4 Vote http://www.wsus.info/index.php?showtopic=10890 5 I found out the cause and solution to a problem we're seeing with all our SCCM Clients that install their Windows Updates using Software Updates Management.Update scans fails showing these messages in the log files:WindowsUpdate.log2009-09-09 06:10:11:037 12 337c PT Server URL = http://
Content Page 1 of 1 You cannot start a new topic You cannot reply to this topic WSUS 3.0 Client will not check in. #1 TheBublitz Member Group: Regular Members Posts: 13 Joined: 16-May-06 Posted 20 Sep 2007, 13:09 I have installed and uninstalled 3.0 about 5 times I cannot get WSUS 3.0 working. THe clients are showing the correct site to check in http://servername/selfupdate they still will not show up in the 3.0 console. I have used the follwoing trouble shooting Try one or all of the following resolutions: Check the configuration of clients. Check connectivity from the client machine to the WSUS server and debug any issue found before proceeding to the next step. Open a command shell. Force a group policy update (if client machine is in a domain): type gpupdate /force Force a detection: type wuauclt.exe /resetauthorization /detectnow Wait 10 minutes for a detection cycle to finish before verification. and To check network connectivity on the WSUS client computer 1. Click Start, and then click Run. 2. In the Open box, type iexplore and then press ENTER 3. In the Internet Explorer Address bar, type: http://WSUSServerName/iuident.cab 2007-09-07 13:54:56:997 820 190 PT WARNING: GetAuthorizationCookie failure, error = 0x800710DD, soap client error = 5, soap error code = 0, HTTP status code = 200 2007-09-07 13:54:56:997 820 190 PT WARNING: Failed to initialize Simple Targeting Cookie: 0x800710dd 2007-09-07 13:54:56:997 820 190 PT WARNING: PopulateAuthCookies failed: 0x800710dd 2007-09-07 13:54:56:997 820 190 PT WARNING: RefreshCookie failed: 0x800710dd 2007-09-07 13:54:56:997 820 190 PT WARNING: RefreshPTState failed: 0x800710dd 2007-09-07 13:54:56:997 820 190 PT WARNING: PTError: 0x800710dd 2007-09-07 13:54:56:997 820 190 Report WARNING: Reporter failed to upload events with hr = 800710dd. 2007-09-07 14:08:33:236 820 190 PT WARNING: Cached cookie has expired or new PID is available 2007-09-07 14:08:33:236 820 190 PT Initializing simple targeting cookie, clientId = b93c4a55-cc39-4d0d-b33d-409a61dafa8b, target group = , DNS name = f_spare_server.marvin.com 2007-09-07 14:08:33:236 820 190 PT Server URL = http://wsinteg:8530/...SimpleAuth.asmx 2007-09-07 14:08:33:236 820 190 Misc WARNING: SendRequest failed with hr = 800710dd. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <> 2007-09-07 14:08:33:236 820 190 PT + Last proxy send request failed with hr = 0x800710DD, HTTP status code = 401 2007-09-07 14:08:33:236 820 190 PT + Caller provided credentials = No 2007-09-07 14:08:33:236 820 190 PT + Impersonate flags = 2 2007-09-07 14:08:33:236 820 190 PT + Possible authorization schemes used = This post