Im planning on adding a remote TrueNAS box to my Veeam setup as a further step in restricting sabotage of my backups with snapshots.
My Veeam backup server is not part of the AD group, it backs up to a local storage drive for a fast recovery if needed, it also backs up to some local Synology NAS drives (without snapshop capability) using username/password - all good so far.
I wanted to add a remote TrueNAS with snapshots so that they couldn’t be deleted via Veeam if compromised. (yes not air gapped but one extra precaution)
It appears that a Windows 10 Machine is having a terrible time connecting to TrueNAS using just username/password if its different from the AD account.
Veeam backup server (not AD joined) can connect happily to the share using its inbuilt authentication but Windows 10 cant. (I have a bunch of backups I want to copy into the directory to seed the remote repository)
Watching tail on the samba logs doesnt seem to provide activity on the Windows 10 attempt (most of the time)
Any ideas - I’ve been bashing away at this for quite a while…