Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 3 subscribers
  • Views 4491 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

Sophos Linux Client updates for Windows Enterprise Console Question

wmo

Working on a role out of Sophos end-point-security to Linux servers.

I have successfully installed the Linux client on a couple of CentOS 6.x and 7.x test boxes.

I successfully get update via the secondary connection which is the sophos Inet.

I get the following error which indicates a samba client error?   Is there a way to manually configure the samba client?

[root@CentosTest6x bin]# ./savupdate
mkdir failed on directory /build/samba-build/extra64/var/lock: No such file or directory
mkdir failed on directory /build/samba-build/extra64/var/lock: No such file or directory
mkdir failed on directory /build/samba-build/extra64/var/lock: No such file or directory
Failed to open remote location! - Connection timed out(110)
mkdir failed on directory /build/samba-build/extra64/var/lock: No such file or directory
mkdir failed on directory /build/samba-build/extra64/var/lock: No such file or directory
mkdir failed on directory /build/samba-build/extra64/var/lock: No such file or directory
Failed to open remote location! - Connection timed out(110)
Failed to replicate from \\EnterpriseConsole\SophosUpdate\CIDs\S000\savlinux
Failed to update from primary update source. Redirecting to secondary update source.
Successfully updated Sophos Anti-Virus from sdds:SOPHOS

 

Thanks for any guidance,

Will 



This thread was automatically locked due to age.
Parents Reply Children
  • 0 in reply to QC

    I installed the sambaclient package.  Open a firewall rule allowing all trafic to the sophosconsole, here is what I get:

    [root@HOST bin]# ./smbclient -U <username> //SOPHOSCONSOLE/SophosUpdate/CIDs/S000/savlinux -c get cidsync.upd
    Connection to SOPHOSCONSOLE failed (Error NT_STATUS_IO_TIMEOUT)

  • 0 in reply to wmo

    Hello Will,

    looks like your Linux boxes can't connect to the share on SOPHOSCONSOLE. I assume you have other (non-CentOS) endpoints that can access the share, haven't you?

    To get more insight I'd increase the log level on the command (./smbclient -d 3 ...) or use tcpdump/Wireshark to trace the connection to the server.
    Can you see the Linux machines in the console, i.e. do they communicate via RMS?

    Christian

Unfiltered HTML