I've upgraded from v11 to v12 yesterday and now the connection to the backup host itself says it's failing in the console.
I'm getting the following errors:
"Failed to send certificate, but certificate is required for remote agent management Error: Failed to establish a connection: cannot find valid IP address"
Task failed. Error: Connection problems.
After a bit of research it seems that v12 changed the way it authenticates with Agents, using Kerberos instead of NTLM when using a hostname instead of an IP. I'm using Veeam in my homelab and don't have a domain set up, my Backup host (the one running B&R) is failing now while the second Windows Server is still backing up just fine.
Is there any way to "force" clients to use NTLM instead of Kerberos? Or can I somehow change this in some other way to make the connection work again?
For now I've deleted the hostname entry from my inventory and just added the server via its IP, this seems to work now at least. But I would love to have an option available to choose which authentication method it will use, I love Veeam B&R for its simplicity, but sometimes it's almost "too" simple already
For many security reasons we will just follow what the operating system is doing. As shared the authentication method in this case is controlled by the group policy/registry setting in windows. My guess is that you had another issue with one of the certificates used and therefore adding the server again solved it. A wild guess but maybe an explanation.
