Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • Add the output of mount -vvv -t cifs//192.168.1.12/Share1$ /mnt/Share1/ to the question. Commented Sep 4, 2022 at 0:33
  • The above comment didn't have one, but you might be right, let me check. Edit: Yes, it needed a space. Same output as before, error 13. – Commented Sep 4, 2022 at 6:13
  • Output from -vvv was the same short error message. Credentials are correct, I am entering them by hand each time and I am certain of them. I've never, to my recollection, had to allow client I.P.'s before. Did something change where I now have to do this? Commented Sep 4, 2022 at 6:17
  • 1. If you replaced the os disk you may need to use smbpasswd to recreate the samba user accounts and set their passwords Commented Sep 4, 2022 at 6:22
  • 2. You will get poor performance if the underlying filesystem used on the samba server is NTFS. Your rationale about samba clients being Windows has no bearing at all. What happens is that samba emulates NTFS network shares on top of a Linux filesystem. In the case of NTFS that's not native so there's yet another layer of emulation and conversion Commented Sep 4, 2022 at 6:24