Skip to main content
added 437 characters in body
Source Link
Hauke Laging
  • 90.4k
  • 19
  • 130
  • 179

conclusion

I had the Windows admin reset the permissions of the share so that I could test the suggestions in the answers. Unfortunately the problem disappeared. As before I cannot see the contents of the share but now the mount can access the deep subdirectories. Very strange.

A remark @intika: I was going to make an additional bounty for your answer but while I was doing so you for some reason deleted your answer...

responses to comments and answers

responses to comments and answers

conclusion

I had the Windows admin reset the permissions of the share so that I could test the suggestions in the answers. Unfortunately the problem disappeared. As before I cannot see the contents of the share but now the mount can access the deep subdirectories. Very strange.

A remark @intika: I was going to make an additional bounty for your answer but while I was doing so you for some reason deleted your answer...

responses to comments and answers

Notice removed Draw attention by Hauke Laging
Bounty Ended with ram0nvaldez's answer chosen by Hauke Laging
added 28 characters in body
Source Link
Hauke Laging
  • 90.4k
  • 19
  • 130
  • 179

4.5.1616; not a member of the domain

4.5.16

4.5.16; not a member of the domain

added 52 characters in body
Source Link
Hauke Laging
  • 90.4k
  • 19
  • 130
  • 179

Windows server

Server 2016, SMB 3.1.1

Samba version

Samba version

Windows server

Server 2016, SMB 3.1.1

Samba version

added 33 characters in body
Source Link
Hauke Laging
  • 90.4k
  • 19
  • 130
  • 179
Loading
added 260 characters in body
Source Link
Hauke Laging
  • 90.4k
  • 19
  • 130
  • 179
Loading
added 1449 characters in body
Source Link
Hauke Laging
  • 90.4k
  • 19
  • 130
  • 179
Loading
Notice added Draw attention by Hauke Laging
Bounty Started worth 500 reputation by Hauke Laging
Source Link
Hauke Laging
  • 90.4k
  • 19
  • 130
  • 179
Loading