The second question is which smbclient is using vs. Now question is, how long is your path which you want to list.
In windows world it depends if you are accessing it as \\server\share (the 260 limit applies) or \\?\UNC\server\share (the 32767 limit applies). There is an Unicode way to access the API, which has a 32,767 limitation. You maybe hitting the infamous 260 Maximum Path Length Limitation. Īs intika has indicated in the comment you did not give us enough details. Passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully*. # panic action = /usr/share/samba/panic-action %d etc/smb/smb.conf (probably not relevant for client functions) root/fs-p01.credentials username=username Xxxxxxxxxxxxxxxxxxx/xxxxxxxxxxxxxxxxxxxxx/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx/2020/2020_06 config files I should be able to access its parent, too, i.e. The path length within the share is 85 characters for the directory I want to work in. I have to wait for the Windows admins to do that on Monday.
Unfortunately I cannot check whether mount would work if I use the wrong domain with it as I cannot change the permissions on the Windows server back to their original settings. However, that is a difference in the configuration between the commands. I just realize that windowsdomain in the smbclient command was incomplete. smbclient //fs-p01.dnsdomain/Data -U username -W windowsdomain./etc/fstab: //fs-p01.dnsdomain/Data /data cifs credentials=/root/fs-p01.credentials 0 0.responses to comments and answers Windows serverĤ.5.16 not a member of the domain commands used Very strange.Ī remark I was going to make an additional bounty for your answer but while I was doing so you for some reason deleted your answer. As before I cannot see the contents of the share but now the mount can access the deep subdirectories. I had the Windows admin reset the permissions of the share so that I could test the suggestions in the answers. How can mount.cifs be made to behave like smbclient?.What are the differences between the ways how smbclient and mount.cifs access a Windows share?.However, the problem must be on the Linux side anyway. We have not determined yet what the minimal set of Windows permissions is which we need for this to work in the current configuration.
And now I can reach the deeper level subdirectories via the mount, too. The Windows admin has given my user additional permissions so that I can now see contents of the moint point. That should not be a problem and it is not for smbclient. I have neither "display content" nor "change into" permission for the lower level subdirectories. I can mount the share (no error message mount point is in /proc/mounts) but I cannot change to the same path or list its contents.I can connect with smbclient, change to the (deep) subdirectory or show its content.The (to me) very strange situation is that I have been given an account on a Windows file server.