Homerboy
Lifer
I normally have my WSUS server set to auto-update nightly
However, lately its failing and reporting the following error:
WebException: The underlying connection was closed: Unable to connect to the remote server. ---> System.Net.WebException: The remote server returned an error: (407) Proxy Authentication Required.
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(S
rverSyncProxy proxy, WebServiceCommunicationHelper webServiceHelper)
at Microsoft.UpdateServices.ServerSync.ServerSyncLib.InternetGetServerAuthConfig(S
rverSyncProxyMicrosoft.UpdateServices.ServerSync.ServerSyncLib.Authenticate(AuthorizationMan
ger authorizationManager, Boolean checkExpiration, ServerSyncProxy proxy, Cookie cookie, WebServiceCommunicationHelper webServiceHelper)
at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.InternalGetConfig()
at Microsoft.UpdateServices.ServerSync.ServerSyncLib.InternetGetServerAuthConfig(S
rverSyncProxyMicrosoft.UpdateServices.ServerSync.ServerSyncLib.Authenticate(AuthorizationMan
gerMicrosoft.UpdateServices.ServerSync.CatalogSyncAgentCore.CatalogSyncThreadProce
sReal(Boolean allowRedirect)
This server should not be going through our HTTP proxy server at all. The only other "proxy" on the network is a Cisco PIX firewall that doubles as the DHCP server... I'm at a loss.
However, lately its failing and reporting the following error:
WebException: The underlying connection was closed: Unable to connect to the remote server. ---> System.Net.WebException: The remote server returned an error: (407) Proxy Authentication Required.
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(S
rverSyncProxy proxy, WebServiceCommunicationHelper webServiceHelper)
at Microsoft.UpdateServices.ServerSync.ServerSyncLib.InternetGetServerAuthConfig(S
rverSyncProxyMicrosoft.UpdateServices.ServerSync.ServerSyncLib.Authenticate(AuthorizationMan
ger authorizationManager, Boolean checkExpiration, ServerSyncProxy proxy, Cookie cookie, WebServiceCommunicationHelper webServiceHelper)
at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.InternalGetConfig()
at Microsoft.UpdateServices.ServerSync.ServerSyncLib.InternetGetServerAuthConfig(S
rverSyncProxyMicrosoft.UpdateServices.ServerSync.ServerSyncLib.Authenticate(AuthorizationMan
gerMicrosoft.UpdateServices.ServerSync.CatalogSyncAgentCore.CatalogSyncThreadProce
sReal(Boolean allowRedirect)
This server should not be going through our HTTP proxy server at all. The only other "proxy" on the network is a Cisco PIX firewall that doubles as the DHCP server... I'm at a loss.