1-800-691-1991 | 9am - 8pm ET
EN

"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-07-30

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:

  • A domain account that is a member of the Local Administrators group.
  • The built-in account named Administrator.

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.
KB ID: 1914
Product: Veeam Backup & Replication
Published: 2014-08-07
Last Modified: 2021-07-30

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later
Knowledge base content request
By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Policy.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
site.forms.confirmation.title
site.forms.confirmation.subtitle
site.forms.confirmation.timer
Didn't receive the code? Click to resend

ty icon

Thank you!

We have received your request and our team will reach out to you shortly.

OK

error icon

Oops! Something went wrong.

Please go back try again later.