I have just built a Server 2019 standard physical server running the latest/current build of Veeam 12. It is not joined to a domain. I am trying to connect it to a Server 2016 standard Hyper-V server, also not joined to the domain. This is a standard 2016 OS with the Hyper-V role installed, not the Hyper-V version.
I get the same error commonly reported when I try to connect them: Access denied or timeout expired. Check for local admin privileges. Possible reasons, invalid credentials or host is not a hyper-v server.
The credentials I am supplying are in HOST\USER format, and they are definitely correct. If I try to open file explorer to \\HVHOST\C$ from the Veeam server, I am prompted for credentials. Entering the local admin creds in HOST\USER format here also give me an access denied error.
I work for an MSP and the manner in which the license was generated does not give me access to support. I’ll try to get a co-worker to contact their support while I see if anyone here can assist me. It seems to be a common issue, but the solution seems evasive.
UAC seems to be a hot topic in this context. I tried turning UAC off on the Veeam server and restarting. That made it so I couldn’t even open up the VBR console right on the Veeam server itself. The creds I am entering to connect to the hypervisor are verified as having local admin privileges. I tried disabling UAC on the hypervisor as well, but I don’t have permission to restart it so that’s not a thing I can fully verify.
Anyone have the magic answer here? Browsing event logs shows connection attempts, but no info on the root cause of the failure.
Best answer by csmithconvergence
View original