downstream server can no longer syncronize after update Glate <ddom[ at ]dayna.org> 6/5/2007 4:25:51 PM One of my downstream servers has been updated to WSUS 3.0 and can no longer synchronize. I initially thought it was because my upstream server was WSUS 2.0 SP1, but I have since updated it to WSUS 3.0 and still nothing. Due to another issue the upstream WSUS server has since been uninstalled, the database deleted, and then reinstalled. Still no workie. If anyone has any ideas I would appreciate it. Here is the error I receive when I attempt to sync: WebException: The underlying connection was closed: An unexpected error occurred on a receive. ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. at System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request) at System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRequest request) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at Microsoft.UpdateServices.Internal.Authorization.DownstreamServerAuthorizationProxy.GetAuthorizationCookie(String accountName, String accountGuid, Guid[] programKeys, String location) at Microsoft.UpdateServices.Internal.Authorization.DownstreamServerAuthorizationPlugIn.GetAuthorizationCookie(Uri url, String parameter) 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.Exe

Re: downstream server can no longer syncronize after update "Lawrence Garvin \(MVP\)" <onsitech[ at ]community.nospam> 6/5/2007 10:46:45 PM "Glate" <ddom[ at ]dayna.org> wrote in message news:1181060751.866352.164180[ at ]n4g2000hsb.googlegroups.com... [Quoted Text] > One of my downstream servers has been updated to WSUS 3.0 and can no > longer synchronize. I initially thought it was because my upstream > server was WSUS 2.0 SP1, It was. > but I have since updated it to WSUS 3.0 and still nothing. Lots of possibilities. > Due to another issue the upstream WSUS server has since > been uninstalled, the database deleted, and then reinstalled. Still no > workie. > If anyone has any ideas I would appreciate it. What's the DNS name of your upstream server? What does the downstream server have configured as the name of the upstream server? Are they in the same domain? Do they use the same DNS server(s)? Is your upstream server configured in DNS? Is there a firewall or proxy server between the two servers? Does your downstream server need to use the proxy server, if it exists? > Here is the error I receive when I attempt to sync: > > WebException: The underlying connection was closed: An unexpected > error occurred on a receive. ---> System.IO.IOException: Unable to > read data from the transport connection: An existing connection was > forcibly closed by the remote host. Looks like something is interfering with the connection. First place to look is firewalls and proxy servers, and the appropriate client-side configurations to use them. -- Lawrence Garvin, M.S., MCTS, MCP Independent WSUS Evangelist MVP-Software Distribution (2005-2007) https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E Everything you need for WSUS is at http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx And, almost everything else is at http://wsusinfo.onsitechsolutions.com .....

Re: downstream server can no longer syncronize after update Glate <ddom[ at ]dayna.org> 6/7/2007 4:07:50 PM I have tried using the FQDN, IP address, hostname, hosts file, etc. It's not a DNS issue. Yes they are in the same domain Yes they are configured in DNS: 3 other downstream servers are working fine. No firewall, no proxy. On Jun 5, 3:46 pm, "Lawrence Garvin \(MVP\)" <onsit...[ at ]community.nospam> wrote: [Quoted Text] > "Glate" <d...[ at ]dayna.org> wrote in message > > news:1181060751.866352.164180[ at ]n4g2000hsb.googlegroups.com... > > > One of my downstream servers has been updated to WSUS 3.0 and can no > > longer synchronize. I initially thought it was because my upstream > > server was WSUS 2.0 SP1, > > It was. > > > but I have since updated it to WSUS 3.0 and still nothing. > > Lots of possibilities. > > > Due to another issue the upstream WSUS server has since > > been uninstalled, the database deleted, and then reinstalled. Still no > > workie. > > If anyone has any ideas I would appreciate it. > > What's the DNS name of your upstream server? > What does the downstream server have configured as the name of the upstream > server? > Are they in the same domain? > Do they use the same DNS server(s)? > Is your upstream server configured in DNS? > Is there a firewall or proxy server between the two servers? > Does your downstream server need to use the proxy server, if it exists? > > > Here is the error I receive when I attempt to sync: > > > WebException: The underlying connection was closed: An unexpected > > error occurred on a receive. ---> System.IO.IOException: Unable to > > read data from the transport connection: An existing connection was > > forcibly closed by the remote host. > > Looks like something is interfering with the connection. First place to look > is firewalls and proxy servers, and the appropriate client-side > configurations to use them. > > -- > Lawrence Garvin, M.S., MCTS, MCP > Independent WSUS Evangelist > MVP-Software Distribution (2005-2007)https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D09... > > Everything you need for WSUS is athttp://technet2.microsoft.com/windowsserver/en/technologies/featured/... > > And, almost everything else is athttp://wsusinfo.onsitechsolutions.com > ....

Re: downstream server can no longer syncronize after update "Lawrence Garvin \(MVP\)" <onsitech[ at ]community.nospam> 6/7/2007 9:16:43 PM "Glate" <ddom[ at ]dayna.org> wrote in message news:1181232470.882532.315230[ at ]w5g2000hsg.googlegroups.com... [Quoted Text] >> > One of my downstream servers has been updated to WSUS 3.0 and can no >> > longer synchronize. I initially thought it was because my upstream >> > server was WSUS 2.0 SP1, >> >> It was. >> >> > but I have since updated it to WSUS 3.0 and still nothing. >> >> Lots of possibilities. >> > Here is the error I receive when I attempt to sync: >> >> > WebException: The underlying connection was closed: An unexpected >> > error occurred on a receive. ---> System.IO.IOException: Unable to >> > read data from the transport connection: An existing connection was >> > forcibly closed by the remote host. >> Looks like something is interfering with the connection. First place to >> look >> is firewalls and proxy servers, and the appropriate client-side >> configurations to use them. >I have tried using the FQDN, IP address, hostname, hosts file, etc. > It's not a DNS issue. > Yes they are in the same domain > Yes they are configured in DNS: 3 other downstream servers are working > fine. > No firewall, no proxy. Okay, humor me.. I'm trying to help... but not answering the questions doesn't help you at all, and it just makes me go on to the next message. >> What's the DNS name of your upstream server? Not yet answered. >> What does the downstream server have configured as the name of the >> upstream >> server? Not yet answered. >> Are they in the same domain? Same domain. Noted. >> Do they use the same DNS server(s)? Not yet answered. >> Is your upstream server configured in DNS? Not yet answered. >> Is there a firewall or proxy server between the two servers? No firewall. No proxy. Noted. Next question: What are the client's proxy configurations set to? (Run proxycfg.exe and paste results to your reply.) >> Does your downstream server need to use the proxy server, if it exists? Not applicable. There's no firewall, and no proxy server. -- Lawrence Garvin, M.S., MCTS, MCP Independent WSUS Evangelist MVP-Software Distribution (2005-2007) https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E Everything you need for WSUS is at http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx And, almost everything else is at http://wsusinfo.onsitechsolutions.com .....