danpass wrote:Today, on our stake computer, I observed that we are also having this problem. I looked in the Sophos log and found that the error is occurring when the client attempts a connection to a church owned update server. Unfortunately, I didn't write down the server address and I won't be able to get back to the computer until next Sunday.
Since apparently this problem is not affecting everyone, perhaps one of the update servers is down, or alternatively, it is possible that incorrect configuration information may have been pushed out to some clients.
Thanks for the additional suggestion. I'm going to contact the support desk tomorrow afternoon and see what they have to say. I DID call them last Friday and they suggested a complete scan followed by a re-install of the Sophos package. After that effort we still had the same problem.
It's a very frustrating problem which I'm sure can be resolved. I'll get back to everyone tomorrow afternoon and report on what has been gained (or lost).