today the support closed the case with no resolution
“ This is Veeam Support with a system generated courtesy notification. Unfortunately, due to high Support Team load we were unable to process your request and it has been archived automatically”
Although the credentials themselves were not the issue, however I have managed to isolate the scenario that triggers the behaviour:
When you login into a newly created windows profile, veeam credentials on agent alone are not sufficient for accessing the network share. Before starting the agent new job wizard, the following procedure must be done first: Click on windows search menu, type “credential” to open Credential Manager settings app, click “Windows credentials”, click “Add a windows credential”. Enter the same credentials for the NAS identical to those needed by agent.
Note that some Samba configurations like “map to guest” might lead to partial read access on a share depending on server file and folder permissions and acls, when you don’t preload the credentials into windows Credential Manager.
Only then the new job wizard would correctly be able to map the existing backups.
The Win10 machine was working because it already had the credentials entered into Windows Credential Manager.
Just providing feeback here.
I have found what was stated by ml35 as to having to add credentials to Windows Credential Manager is indeed necessary. In another post I created: post509485.html#p509485, I found this to be true. If you read that post, I also stated two additional items that were pertinent in my testing: 1. The solution here only worked when I was logged in with an administrator account. 2. I have never had to put credentials in WCM when creating a VAW backup job. Only putting credentials in VAW were necessary.
