Replica JOB on hyperv standalone = hyperv target goes to unavailable -Case ID 05962459

[urbanspike]

Hello,
I have a really weird problem. We have added a standalone hyperv server under windows 2019 in Veeam. LocalAccountTokenFilterPolicy key to 1. This server is not on a domain, the firewall is OK, no connectivity problem between the Veeam server and this server. We were able to add it to the Veeam console without any errors. The account used is indeed the local administrator of this hyperv machine. Everything is ok for Veeam until we launch a replication job. As soon as we launch a replication job, we arrive at the waiting for a proxy stage then after a few seconds, we notice that the target server goes unavailable in the console. It is quite possible to do a rescan (which is OK) then again the server switches to unavailable. Veeam services continue to run on the target server, no errors in the logs. We tried adding it with the ip more than the dns name, same problem.
We have 11 other servers of the same type to which we are replicating and they are all ok.
Thank you for your help.

[Mildur]

Hello

Please give our support team some time to analyze your logs.
The case was opened just minutes ago.

Best,
Fabian