Event ID:386 The underlying connection was closed,

Discussion in 'Update Services' started by Jason Stough, Dec 21, 2005.

  1. Jason Stough

    Jason Stough Guest

    When I try to sync a replica server to my upstream WSUS server, I get the
    above error. The following is a list of what I have tried so far:
    1. Added the NETWORK SERVICE account to the root drive that contains the
    wsus content folder.
    2. Ran wsusutil reset command. I also ran the debug command line tool and
    deleted all expired updates.
    3. Restarted the automatic updates, wsus sql, www, and bits services.

    This server is running Win2003 SP1 and is a DC. Any suggestions would be
    much apprecated. Thanks in advance.

    Jason
     
    Jason Stough, Dec 21, 2005
    #1
    1. Advertisements

  2. Is there a proxy server or firewall between the replica and master server?

    "connection was closed" errors generally pop up as a result of a proxy or
    firewall interfering with the connection/session.
     
    Lawrence Garvin \(MVP\), Dec 22, 2005
    #2
    1. Advertisements

  3. Jason Stough

    Jason Stough Guest

    Thank you for the quick response! No, there is not a proxy server or
    firewall between the replica and master. It is a WAN link with Cisco's at
    each end.
     
    Jason Stough, Dec 22, 2005
    #3
  4. Do the Cisco routers have any packet filtering configured?

    Does the replica server have any configuration information for a proxy
    server?

    Can you run 'proxycfg.exe' and post the output from that command?

    What is the URL you have directed your replica server to query for updates?
     
    Lawrence Garvin \(MVP\), Dec 22, 2005
    #4
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.