Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 2 replies
  • Subscribers 1 subscriber
  • Views 1025 views
  • Users 0 members are here
Options
Suggested
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

Problems protecting an XP client

PeterT

I had Sophos Endpoint Security and Control running on a Windows 2003 Server. The Windows XP clients were protected and Sophos Anti_virus and Sophos Auto Update were all running fine.

Then I got a new Server. I put Sophos Endpoint Security and Control on that. One of my XP clients that was attached to the old server has now left that domain and been attached to the new Server.

I have successfully "discovered" this new computer from the Sophos Enterprise Console but I have not managed to "Protect" it.

I tried uninstalling "Sophos AutoUpdate" and "Sophos Anti-Virus" on the client. Then when I went to "Protect" it, the AutoUpdate appears to have been installed on the client but not the Sophos Anti-Virus.

I get an error in the "C:\Program Files\Sophos\AutoUpdate\logs\alc.log" file which says :
"Could not add a connection to server \\<server-name>\SophosUpdate; user ABCD\SophosUpdateMgr; Windows error 1909

Does anybody know what this means and how I can get over this problem ?

Thanks

            Peter

:13335


This thread was automatically locked due to age.
  • 0

    HI,

    Running:

    net helpmsg 1909

    returns:
    "The referenced account is currently locked out and may not be logged on to. "

    I suspect that clients have the wrong password for the SophosUpdateMgr account and have therefore locked it out.  You might be best creating a new update account for the clients to use and send that to them via the upating policy.

    I hope that helps.

    Regards,

    Jak

    :13341
  • 0

    Hello Jak,

    I reckon my first mistake was that when I originally uninstalled Sophos Anti Virus it left some junk lying around in my client's "C:\Program Files\Sophos" folder.

    This probably caused one or two failures when I subsequently attempted to "protect" the client from my new Server. This may have locked out SophosUpdateMgr.

    I had not noticed that SophosUpdateMgr account was locked out, so thanks for that tip. I just unlocked it and then tried again. This time making sure I had completely deleted the "C:\Program Files\Sophos" folder.

    It's all working now so I'm happy.

    Peter

    :13355
Unfiltered HTML