> Can you please follow the resolution in the KB and see if it works?
>
>
http://support.microsoft.com/kb/823177>
> Thanks, Siva
> "Peter" <wont[ at ]tell.you> wrote in message
> news:u8Hyc0inHHA.208[ at ]TK2MSFTNGP05.phx.gbl...
>>i am not using any proxy...
>>
>>
>>
>> "Siva Shanmugam [MSFT]" <sivsha[ at ]online.microsoft.com> wrote in message
>> news:eqsATqinHHA.3544[ at ]TK2MSFTNGP03.phx.gbl...
>>> Do you use an authenticated proxy?
>>>
>>> If you use an authenticated proxy, then please do the following.
>>> Important configuration issue
>>> If you use a proxy server that requires authentication, you must
>>> overwrite the proxy server password in the WSUS Server Configuration
>>> Wizard. If you do not do this, the WSUS server may not synchronize
>>> updates. Because the configuration wizard starts automatically at the
>>> end of the Setup process, this problem can cause synchronization errors
>>> after you upgrade to WSUS 3.0. You can avoid this problem by canceling
>>> the Configuration Wizard after the upgrade or by reentering the correct
>>> proxy password when the wizard runs. To recover from this problem after
>>> it has occurred, follow these steps: 1. In the WSUS 3.0 console tree,
>>> click Options.
>>> 2. In the details pane, click Update Source and Proxy Server.
>>> 3. In the Update Source and Proxy Server dialog box, click the
>>> Proxy Server tab.
>>> 4. Reenter the proxy password. Then, save the setting.
>>> For more information about Windows Server Update Services, visit the
>>> following Microsoft Web site:
>>>
>>> "Peter" <wont[ at ]tell.you> wrote in message
>>> news:%238qaKzfnHHA.4032[ at ]TK2MSFTNGP02.phx.gbl...
>>>> hey there...
>>>>
>>>> I just upgraded to WSUS 3.0 (from WSUS 2.0) but it seems like WSUS 3.0
>>>> wont connect to Microsft Windows Upsdate Server. I get this error:
>>>>
>>>> WebException: The underlying connection was closed: Could not establish
>>>> trust relationship with remote server.
>>>> at System.Net.HttpWebRequest.CheckFinalStatus()
>>>> at System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult
>>>> asyncResult)
>>>> at System.Net.HttpWebRequest.GetRequestStream()
>>>> at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
>>>> methodName, Object[] parameters)
>>>> at
>>>> Microsoft.UpdateServices.ServerSyncWebServices.ServerSync.ServerSyncProxy.GetAuthConfig()
>>>> at
>>>> Microsoft.UpdateServices.ServerSync.ServerSyncLib.InternetGetServerAuthConfig(ServerSyncProxy
>>>> proxy, WebServiceCommunicationHelper webServiceHelper)
>>>> at
>>>> Microsoft.UpdateServices.ServerSync.ServerSyncLib.Authenticate(AuthorizationManager
>>>> authorizationManager, Boolean checkExpiration, ServerSyncProxy proxy,
>>>> Cookie cookie, WebServiceCommunicationHelper webServiceHelper)
>>>> at
>>>> Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.InternalGetConfig()
>>>> at
>>>> Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.CatalogSyncThreadProcessReal(Boolean
>>>> allowRedirect)
>>>>
>>>> And Event Viewer returns ID 10022
>>>> Anyway - WSUS is running on Windows 2003
>>>>
>>>>
>>>> I have tried to google around and figured out that this is a common
>>>> error for ASP.NET-application - something about the certificate and
>>>> stuff. But I havent been able to fix it - anybody with a solution?
>>>>
>>>>
>>>> // peter
>>>>
>>>
>>>
>>
>>
>
>