Dimitris Bastas

I am running the latest version of ERA (version 6.5.31.0) Following MartinK suggestions I changed a line in the file /var/opt/eset/RemoteAdministrator/Server/Scripts/UnixWindowsNetworkRemoteInstall.sh Specifically the line LANG= mount -t cifs -o "${mount_domain_option}username=$ERA_RD_WN_USERNAME" "$remote_cifs_share" "$local_cifs_mount" becomes LANG= mount -t cifs -o "${mount_domain_option}username=$ERA_RD_WN_USERNAME,vers=2.0" "$remote_cifs_share" "$local_cifs_mount" After that i run the command /sbin/restorecon -F -R -v /var/opt/eset/RemoteAdministrator/Server and I tried to deploy the agent to one of the Windows 7 machines. This workaround worked for me and I wish that a change will be made to the ERA webconsole interface, so that a user can tell that a windows computer has SMB version 2, before the agent can be installed remotely. Thank you very much for the help.

It seems that our new ESET Remote Administrator Linux appliance cannot deploy the agent on windows 7 machines which have the SMB1 protocol disabled for security reasons. The error I see in system logs is 'CIFS VFS: cifs_mount failed w/return code = -112' I suppose that this has to do with the fact that windows 7 machines cannot talk SMB1 any more. When i try to manually mount a remote windows 7 share using the parameter mount -t cifs -o vers=2.0 then the mount succeeds, but how to append this parameter to ESET remote administrator? Is there any solution to this problem?