"Invalid Credentials" error adding a Hyper-V host using a local account

KB ID: 1914
Product: Veeam Backup & Replication
Published: 2014-08-07
Last Modified: 2021-10-18
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please try again later.

Challenge

When attempting to add a Hyper-V host to Veeam Backup & Replication using a local (non-domain) user account, the following error occurs:
Failed to connect to host
Access denied or timeout expired. 
Check if you have local administrator privileges on computer
Possible reasons:
1. Invalid credentials.
2. Specified host is not a Hyper-V server.
add server access is denied error

Cause

When using a local account other than the built-in Administrator account, remote access is blocked by UAC remote restrictions.

Solution

When adding a Hyper-V server to Veeam Backup & Replication, the account assigned must comply with UAC remote restrictions. Specifically, the account must be either of the following:

Use Case Examples:

  • If the Hyper-V server being added to Veeam Backup & Replication is joined to a domain (as recommended by Microsoft), a domain account that is a member of the local Administrators group on the Hyper-V server should be used to add the server to Veeam Backup & Replication.

  • If the Hyper-V server being added to Veeam Backup & Replication is not joined to a domain, or there is a need to avoid using a domain account, the built-in account named Administrator must be used to add the server to Veeam Backup & Replication. Other local accounts will be restricted by UAC, even if they are members of the Administrators group.

    Note: If the local built-in Administrator account has been renamed, it can still be used as the unique SID that bypasses Remote UAC Restrictions remains valid.

More information

If none of the provided account options are viable, it is possible to disable UAC remote restrictions. This will allow local accounts other than the Administrator to be used for remote access. This option should be considered a last resort as it involves disabling a major Microsoft Windows OS security feature that may leave the Hyper-V server vulnerable.
If the error listed on this KB article occurs while using the built-in Administrator account or a domain account that is a member of the local Administrators group, the issue may be related to a firewall or NAT. During the initial connection to the Hyper-V server, Veeam Backup & Replication will attempt to communicate with the Hyper-V server to determine if it is, in fact, a Hyper-V server. If those connections fail, the error on this KB will occur. Review the Used Ports section of the User Guide.
Click here to send feedback regarding this KB, or suggest content for a new KB.
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.