karmic smbclient fails to access NAS box

Bug #407583 reported by Rolf Leggewie on 2009-08-01
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
samba
Confirmed
High
samba (Ubuntu)
Low
Unassigned

Bug Description

Binary package hint: samba

I have a cheap NAS box that does not understand the unix extensions of samba. Other than that, it was more or less working fine in Jaunty. After recent updates, accessing the box from Karmic is hit-and-miss at best.

smblient returns undecipherable errors that change from one second to the next

$ smbclient -L mynas
Enter rolf' password:
protocol negotiation failed: NT_STATUS_END_OF_FILE
$ smbclient -L mynas
Enter rolf's password:
Receiving SMB: Server stopped responding
session request to MYNAS failed (Call returned zero bytes (EOF))
Receiving SMB: Server stopped responding
session request to *SMBSERVER failed (Call returned zero bytes (EOF))

An autofs/smbfs mount with nounix option turned on does see the shares, but the shares themselves are empty.

$ ll /mnt/smb/mynas/
total 0
drwx------ 1 rolf rolf 0 2008-07-07 18:40 backup
drwx------ 1 rolf rolf 0 2008-07-07 18:39 Musik
drwx------ 1 rolf rolf 0 2008-07-07 18:39 PUBLIC
drwx------ 1 rolf rolf 0 2008-07-07 18:40 Video

$ ll /mnt/smb/mynas/backup/
total 0

GUI clients such as thunar or nautilus can sometimes access the shares themselves, but it's hit-and-miss. You never know if it will work today. Accessing from a hardy box usually works fine.

Rolf Leggewie (r0lf) on 2009-08-01
summary: - smbclient fails to access NAS box
+ karmic smbclient fails to access NAS box
Rolf Leggewie (r0lf) wrote :

simply downgrading samba-common, smbfs and smbclient to the Jaunty versions did not resolve the issue.

Chuck Short (zulcss) wrote :

Can you include the output smbclient -d 10 -L mynas to this bug report making sure you dont have any passwords attached to the output of the log.

Thanks
chuck

Changed in samba (Ubuntu):
status: New → Incomplete
Rolf Leggewie (r0lf) wrote :

Chuck, thank you for taking a look. I'll gladly provide more information. First is the log from the hardy client, the NAS box can be accessed without further problems. I'll then attach the log from the karmic box (although currently with downgraded samba packages).

Rolf Leggewie (r0lf) wrote :
Thierry Carrez (ttx) on 2009-08-17
Changed in samba (Ubuntu):
status: Incomplete → New
Changed in samba:
status: Unknown → Confirmed
Chuck Short (zulcss) on 2009-09-02
Changed in samba (Ubuntu):
status: New → Confirmed
Changed in samba (Ubuntu):
importance: Undecided → Low
status: Confirmed → Triaged
Changed in samba:
importance: Unknown → High
Rolf Leggewie (r0lf) wrote :

+--[ https://bugs.launchpad.net/ubuntu/+source/samba/+bug/226777/comments/9 ]
|
| Hurra, I believe I just found the solution at least to my problem with mounting the NAS at all.
| The box does not understand the Unix extensions, thus "sudo mount -t smbfs //mynas/PUBLIC /mnt/test
| -o nounix" manages to mount the share, at least. Am I correct to assume that any CIFS share not
| provided by a Linux host has to be mounted with the nounix option?
|
+--

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.