Skip to main content
  • EN

Hi everyone,

recenly i’m doing some test on the veeam backup&replication community edition on my Dell R710 which is running server 2019 standard. And at the first time, i can add a hyper-v server which is running server2019 (standalone) to the backup job, but once i deleted the job, i cannot add any hyper-v again.

It always shows :

Failed to connect to host 10.178.3.41

Access denied or timeout expired. (sometimes is invalid namespace)
Check if you have local administrator privileges on computer '10.178.3.41'.

Possible reasons:
1. Invalid credentials.
2. Specified host is not a Hyper-V server.

================

what i did for this issue:

  1. https://www.veeam.com/kb1914
  2. https://www.scribd.com/document/421024195/Veeam-Backup-Invalid-Credentials-Error-Adding-a-Hyper#

  3.  

  4. I added both the target server and the server with the veeam installed to the domain
  5. created the local admin account for both server, using same account and pwd
  6. using domain admin account cannot work
  7. checking the port and disable the firewall , also the turn off the defender.
  8. checking the network is fine, dns is fine.

Now I'm really lost, how should I solve this problem.

This worked for me:

Credentials format: user@hostname

Same error trying to add Hyper V host in the Azure.

Tried all the above. No solution yet?

 

Failed to connect to host 48.216.227.99

Access denied or timeout expired. (sometimes is invalid namespace)
Check if you have local administrator privileges on computer '48.216.227.99'.

Possible reasons:
1. Invalid credentials.
2. Specified host is not a Hyper-V server.

Hyper-V is not domain joined, I seem to have tried all the common fixes to no avail.

Regedit didn’t help, local Administrator account is active, doesn’t work.

Credentials format: user@hostname, doesn’t work.

 

@andysl 

I believe this is related to changes made Microsoft to DCOM. The below article may help

https://www.veeam.com/kb4376

 

Can you let me know the OS of VBR Server and HyperV Server.

Is HyperV in a cluster? Was this working fine before?

Can you also review Windows Event Viewer logs on the VBR server and HyperV Server

The below article shall help

https://www.veeam.com/kb4376

 

Hi @Jeric - did you ever get feedback from Support on this issue and get it resolved?  I wanted to follow up so we can ensure we select a best answer for the problem to assist others that have the issue.  Please let us know by updating this thread.

Hi @Jeric  - I just wanted to follow up to see if you were able to resolve your issue with one of the posted comments or if you found another solution.  If you could update the thread and if one of the comments helped you mark that as best answer or if you found another solution post it and then mark it as best answer that would be great.  It will help others and the community to get answers/details for similar problems.

host\user

thanks so much for your advice, Currently worked it is ok

 

New it Veeam….  Had all the issues you all are talking about. 

Maybe look at your host OS level, and your Veeam Server OS level and ensure that your activation authentication level is at least at RPC_C_AUTHN_LEVEL_PKT_INTEGRITY  on the Veeam Server.  It appears that the Server side authentication level policy does not allow the user that is trying to connect from the Veeam server (The credentials set) to activate the DCOM server.

Basically… make sure all your patching and windows updates are up to date on both sides of the fence (Veeam Server / Host Server so that they can play “nice in the sand box” together over Dcom.  

 

See if your getting this error in your security log on the Host server….  If so.. patch patch patch the Veeam server OS.

“The server-side authentication level policy does not allow the user Domain\Usernname SID (S-1-5-21-xxxxxxxxx-xxxxx-xxxxx-xxxxxx) from address xxx.xxx.xxx.xxx to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application.”

Updated my Veeam Server and works 10000%  

Comment


Terms & Conditions