This is Debian bug #611834: smbclient fails to work on a server not supporting the Echo request. Old samba versions that does not support this request are still used for example in SLES 10. | $ smbclient //smb.example.org/VOL2 | Enter blank's password: | session request to SMB failed (Called name not present) | Domain=[JURA] OS=[SUSE LINUX 10.1] Server=[SUSE LINUX 10.1] | smb: \> SMBecho failed. Maybe server has closed the connection | $
Exactly what Samba version is this ? Even versions as far back as 3.0.x support SMBecho... Jeremy.
That was samba 3.5.6. I'll try to ping the original bug submitter as he might be of more help, having the test case handy -- Christian
Please also upload a network trace of the failure. Information on how to create useful network traces can be found under http://wiki.samba.org/index.php/Capture_Packets Thanks
I've got the same problem with an Apple Time Capsule that is not running Samba: Domain=[ZHADUM] OS=[Apple Base Station] Server=[CIFS 4.32] smb: \backups\> SMBecho failed. Maybe server has closed the connection The problem is simply caused by the fact that it doesn't support the SMBecho request.
Created attachment 7267 [details] Packet capture with the SMB echo packet and the response by the Apple Time Capsule This packet capture contains the SMB echo packet and the response.
Created attachment 7268 [details] Patch to fix problems between "smbclient" and CIFS 4.32 This patch fixes the problem for me by simply ignoring the error reported by the Time Capsule. The SMB echo will still serve the purpose of keeping the connection open in this case.
Wow - so it sets the NT_STATUS_ERROR code flag in flags2, then returns an invalid NT STATUS code of 0xFFFF0002. That's messed up. Jeremy.
Probably we should change this code to terminate the connection only if we get a well known socket error or timeout detected. Jeremy.
Created attachment 7269 [details] git-am fix for 3.5.next Matthias - can you confirm this fix works for you ? Jeremy.
Yes, this fix works for me. I can establish a connection to the Time Capsule and download a file without problems (and with excellent performance).
Comment on attachment 7269 [details] git-am fix for 3.5.next This git-am fix also applies to 3.6.next. Submitter has verified it fixes the problem. Jeremy.
Comment on attachment 7269 [details] git-am fix for 3.5.next I think we should just check cli_state_is_connected() after cli_echo(). There're more error codes possible than just 3.
Created attachment 7273 [details] Patches for master Jeremy, I think this is a better fix.
Comment on attachment 7273 [details] Patches for master Pushed to master.
Created attachment 7274 [details] git-am fix for both 3.5.next and 3.6.next. Back-port of Metze's patch for 3.5.next and 3.6.next.
Comment on attachment 7274 [details] git-am fix for both 3.5.next and 3.6.next. looks good
Karolin, please for the next releases
Pushed to both branches. Closing out bug report. Thanks!