WSUS Sync Error

Question

Dears , 
my WSUS server ,when am trying to synchronizing, it display a HTTP error accrued and below is the error message :
 WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected
host has failed to respond 10.xxx.xxx.5:8080
at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
   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.SyncConfigUpdatesFromUSS()
   at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ExecuteSyncProtocol(Boolean allowRedirect)
Please advise me . 

Answer 1

connection failed because connected host has failed to respond 10.xxx.xxx.5:8080
I would venture a guess that your proxy server (or the proxy client settings of the WSUS server) are misconfigured.
If this masked out address on port 8080 is your proxy server, then that will be your root cause.
First, the WSUS Server needs to be able to communicate on port 80 AND port 443 *simultaneously* to different URLs, so your proxy server needs to be able to manage those separate communications. If the only port your proxy server is listening on is port 8080,
then it probably doesn't know how to properly route HTTP sessions vs HTTPS sessions.
Second... if at all possible... WSUS is *NOT* an appropriate candidate for using a proxy (caching) server. Among other things, the gigabytes of content downloaded by the WSUS server (which will be of ZERO use to any other proxy client) will clog up the proxy
cache, effectively rendering the proxy cache useless for the rest of the enterprise.
Best option: Allow the WSUS server to bypass the proxy server.
If that's NOT an option, then you'll likely need to configure a second listener port on the proxy server, or ensure that the proxy server is able to route traffic from the protocol level (HTTP vs HTTPS).
Bottom line... the communication is getting lost inside the proxy server because it's mishandling the traffic.
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.