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

Ports and UNC paths

8192 is used for the clients to report back to the enterprise server (according to Sophos telephone support), would that port be displayed on the client as a remote port or a local one.

A number of clients are displaying it as a local port, but not a remote one, they are also not reporting back to the EC, and I'm trying to find out why.

Another issue is.

How can I force Sophos EC to use IP's rather then machines names, Sophos refuses to allow me to use \\<ip> and insist on me using \\<machinename>

One other thing,

On the main screen of the EC it tells me that :

An update manager has not updated since 04 march 2011 16:31

However, looking at the update managers of which are 3, only the one with the EC has an error of "Software delivery failed" which only deliveres to itself and updates direct from Sophos just like the other two.

So as far as I understand it, it's failing to update itself but quite happy to update what little clients it wants to respond to, how would this even be possible, the UM should download the update and place it into the share that the clients use, this it is doing according to the clients but it isn't according to the server?

:11229


This thread was automatically locked due to age.
Parents
  • I've had a look over the logs, and the latest udpated made the following logs

    Cannot create stream <path>

    Decoding of product release <name or program> <software distribution name> because the sync failed.

    verion not gathered by Dispatcher due to sync fail

    decoding of product release wasn't done due to sync fail

    From what I can gather from that, it cannot write to a file in the C:/Programdata/sophos/update manager/update manager/ warehouse/randomnumber

    I'll assume that the path slashes being backwards is a bug in the log viewer and not an "issue" with the program.

    1 - If the SEC goes belly up, it's restored from a backup made every hour onto another VM machine, that's ready. (which would only effect the one site, not all 3)

    2 - if the a SUM goes down the clients are instructioned to fall back to Sophos direct via the 2nd update location.

    Its not ideal but all I got to work with, which isn't much.

    :11427
Reply
  • I've had a look over the logs, and the latest udpated made the following logs

    Cannot create stream <path>

    Decoding of product release <name or program> <software distribution name> because the sync failed.

    verion not gathered by Dispatcher due to sync fail

    decoding of product release wasn't done due to sync fail

    From what I can gather from that, it cannot write to a file in the C:/Programdata/sophos/update manager/update manager/ warehouse/randomnumber

    I'll assume that the path slashes being backwards is a bug in the log viewer and not an "issue" with the program.

    1 - If the SEC goes belly up, it's restored from a backup made every hour onto another VM machine, that's ready. (which would only effect the one site, not all 3)

    2 - if the a SUM goes down the clients are instructioned to fall back to Sophos direct via the 2nd update location.

    Its not ideal but all I got to work with, which isn't much.

    :11427
Children
No Data