WSUS 4 connecting to WSUS 3.0 upstream: http error occurred

Our WSUS configuration was completely shot, so I wiped and rebuilt. Our primary server at HQ is 2008 R2, and the downstream server is 2012. The primary server has been up and running for more than a week, but I can't get the downstream to connect. When I click Start Connecting, it takes about 30 seconds and then reports "An HTTP error occurred." Here's what I get when I click details:

WebException: Unable to connect ot the remote server ---> System.Net.Scokets.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 <ip address>:8530
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, WebServiceCommunicationHelperwebServiceHelpter)
   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)
SupportSpecMSAsked:
Who is Participating?
 
SupportSpecMSConnect With a Mentor Author Commented:
Found the problem. The remote location's Exinda was blocking traffic from our WSUS problem due to a broadcast storm by that server years ago. The old block was removed and the system synchronized properly.
0
 
LukeMoCommented:
Check the port number of the 2008 R2 server WSUS in the IIS Manager.   I do believe it's port 80 by default if not running SSL.

See attached JPG from my 2012R2 SUS  IIS control panel.    I realize it's not 2008R2, but that's what I've got now in my lab.
WSUS12R2.jpg
0
 
SupportSpecMSAuthor Commented:
Okay, so I didn't do one basic piece of troubleshooting that I should have done: when I go to http://servername on my PC (on site with the upstream) the IIS7 splash loads. When I try to load the same page in IE on the downstream server, it doesn't work.

Is there a setting in IIS I need to tweak, or should I be talking to the network guys at the remote location to get them to check out a connectivity problem?

The remote site connects via VPN and is in a different subnet than the upstream server, if that matters. But the downstream can ping the upstream.
0
 
LukeMoCommented:
If you've got routing setup, the subnets don't matter.  

Do you have any other machines in the downstream subnet that can try to reach http://servername?

from your PC, can you reach http://downstreamservername and get the IIS splash?
0
 
SupportSpecMSAuthor Commented:
Network problem
0
All Courses

From novice to tech pro — start learning today.