This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Sophos Update manager not working

I have upgraded from Eneterprise Console 3.1 to 4. The migration of the EM Library settings failed. I have tried to manually create this, however I keep on getting timeout issues ( Timeout occured while trying to connect to specified address ) when I try and add the source. I have set the proxy, no joy.

So at the moment i am still using the EM library for updates. How can I get the update manager working properly??

:266


This thread was automatically locked due to age.
Parents

  • Fahdp wrote:

    In my Sophos EC, if I go to Update Manager, then edit the server there. Under sources It has the username/pass, then a proxy setting. I put the IP address and port in. Thats fine. When I OK it, it times out. I stilladd as source. Still IP is OK ( no http prefix yet ). When I close the Config Update Manager Wizars, then go back to sources and edit the Sophos source there, I see http:// has been added.


    Ah, now I see - it's the proxy address which is prefixed. Now this shouldn't make any difference.

    • Check if there are one or more files names SUMTraceyyyymmddThhmmss.log at Documents and Settings\All Users\Application Data\Sophos\Update Manager\Logs - look for the attempted http access. But maybe I just say "Cannot create stream ..."
    • Under Program Files\Sophos\Enterprise Console\SUM there's a program named Logviewer.exe which displays the SUM Log
    • and of course I'd check the proxy logs

    ( and no, I don't use a proxy in production but I've done some tests a while ago)

    Christian

    :286
Reply

  • Fahdp wrote:

    In my Sophos EC, if I go to Update Manager, then edit the server there. Under sources It has the username/pass, then a proxy setting. I put the IP address and port in. Thats fine. When I OK it, it times out. I stilladd as source. Still IP is OK ( no http prefix yet ). When I close the Config Update Manager Wizars, then go back to sources and edit the Sophos source there, I see http:// has been added.


    Ah, now I see - it's the proxy address which is prefixed. Now this shouldn't make any difference.

    • Check if there are one or more files names SUMTraceyyyymmddThhmmss.log at Documents and Settings\All Users\Application Data\Sophos\Update Manager\Logs - look for the attempted http access. But maybe I just say "Cannot create stream ..."
    • Under Program Files\Sophos\Enterprise Console\SUM there's a program named Logviewer.exe which displays the SUM Log
    • and of course I'd check the proxy logs

    ( and no, I don't use a proxy in production but I've done some tests a while ago)

    Christian

    :286
Children
No Data