Hi, I updated our servers to 4.2.11, and I have a problem, but I'm not sure if the problem is related to the update. I am trying to use mount.cifs:> mount -t cifs -o username=username,password=super_secret,domain=WRKGRP //ip.of.our.samba/share /mnt > mount error(112): Host is down > Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)Host is up, i can use smbclient to connect, and also coming from windows everything works. I also tried adding sec=ntlmv2i, makes no difference. mount.cifs version: 6.4, debian jessie Could this perhaps have something to do with the new defaults getting in the way? Host down seems such a strange message... The only interesting lines on the samba server (log level 5) is:> [2016/04/18 21:39:44.373051, 5] ../source3/lib/messages.c:384(messaging_register) > Registering messaging pointer for type 1 - private_data=(nil) > [2016/04/18 21:39:44.496187, 5] ../source3/lib/util_sock.c:132(read_fd_with_timeout) > read_fd_with_timeout: blocking read. EOF from client. > [2016/04/18 21:39:44.496225, 5] ../source3/smbd/process.c:553(receive_smb_talloc) > receive_smb_raw_talloc failed for client ipv4:192.87.143.26:60884 read error = NT_STATUS_END_OF_FILE. > [2016/04/18 21:39:44.496318, 4] ../source3/smbd/sec_ctx.c:316(set_sec_ctx) > setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0 > [2016/04/18 21:39:44.496342, 5] ../libcli/security/security_token.c:53(security_token_debug) > Security token: (NULL)EOF from client, NT_STATUS_END_OF_FILE? Ideas anyone?
Hi lists at merit.unu.edu,> I updated our servers to 4.2.11, and I have a problem, but I'm not sure > if the problem is related to the update.I've had a call from a client yesterday who had issue with his copiers' scan2folder feature after badlock samba file server upgrade. The mount.cifs ntlm basic auth was not working either, and we had to configure "server signing=disabled" as a temporary workaround. Could you try that? Cheers, Denis> I am trying to use mount.cifs: > >> mount -t cifs -o username=username,password=super_secret,domain=WRKGRP >> //ip.of.our.samba/share /mnt >> mount error(112): Host is down >> Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) > > Host is up, i can use smbclient to connect, and also coming from windows > everything works. > > I also tried adding sec=ntlmv2i, makes no difference. > > mount.cifs version: 6.4, debian jessie > > Could this perhaps have something to do with the new defaults getting in > the way? Host down seems such a strange message... > > The only interesting lines on the samba server (log level 5) is: > >> [2016/04/18 21:39:44.373051, 5] >> ../source3/lib/messages.c:384(messaging_register) >> Registering messaging pointer for type 1 - private_data=(nil) >> [2016/04/18 21:39:44.496187, 5] >> ../source3/lib/util_sock.c:132(read_fd_with_timeout) >> read_fd_with_timeout: blocking read. EOF from client. >> [2016/04/18 21:39:44.496225, 5] >> ../source3/smbd/process.c:553(receive_smb_talloc) >> receive_smb_raw_talloc failed for client ipv4:192.87.143.26:60884 >> read error = NT_STATUS_END_OF_FILE. >> [2016/04/18 21:39:44.496318, 4] >> ../source3/smbd/sec_ctx.c:316(set_sec_ctx) >> setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0 >> [2016/04/18 21:39:44.496342, 5] >> ../libcli/security/security_token.c:53(security_token_debug) >> Security token: (NULL) > > EOF from client, NT_STATUS_END_OF_FILE? > > Ideas anyone? >-- Denis Cardon Tranquil IT Systems Les Espaces Jules Verne, bâtiment A 12 avenue Jules Verne 44230 Saint Sébastien sur Loire tel : +33 (0) 2.40.97.57.55 http://www.tranquil-it-systems.fr
Hi Denis, list, On 19-4-2016 9:18, Denis Cardon wrote:> Hi lists at merit.unu.edu, > >> I updated our servers to 4.2.11, and I have a problem, but I'm not sure >> if the problem is related to the update. > > I've had a call from a client yesterday who had issue with his copiers' > scan2folder feature after badlock samba file server upgrade. The > mount.cifs ntlm basic auth was not working either, and we had to > configure "server signing=disabled" as a temporary workaround. Could you > try that?Disabled server signing, but unfortunately the error remains the same. Any other suggestions..? Could someone else check that mount.cifs 6.4 on jessie is still working against samba after the badlock upgrade? MJ
On 19-4-2016 9:18, Denis Cardon wrote:> Hi lists at merit.unu.edu, > >> I updated our servers to 4.2.11, and I have a problem, but I'm not sure >> if the problem is related to the update. > > I've had a call from a client yesterday who had issue with his copiers' > scan2folder feature after badlock samba file server upgrade. The > mount.cifs ntlm basic auth was not working either, and we had to > configure "server signing=disabled" as a temporary workaround. Could you > try that?Reading the release notes for the samba badlock release, we are advised to use mount.cifs with "sec=krb5(i)" or "sec=ntlmssp(i)", and not "sec=ntlmv2". I am using those, but still receive the "mount error(112): Host is down" error. I tried mount.cifs to connect to a real windows machine, and that one works as expected. So the problem seems to be samba-specific..?