Skip to main content
commvault.com commvault.com
Question

Issue Adding Standalone Hyper-V Host – Credential/Connection Failure

  • November 27, 2025
  • 2 replies
  • 24 views
F
Forum|alt.badge.img+1

 

 

Dears,

I am trying to add a standalone Hyper-V host (not joined to a domain) into Commvault, but I am facing issues with the credentials during the hypervisor configuration.

The Hyper-V host is not part of the domain, so I entered the hostname, local administrator username, and password.
I also added the Hyper-V host and Commvault server entries to the hosts file on all related servers.

However, the system fails during the connection and validation process.
Below is the exact error message:

Failed to connect to virtual machine host [CommvaultSVR.xxxxxxxxxxx.com] as user [.\Administrator] 
from access node [commvaultsvr]. Please ensure that the access node is able to communicate 
with the host and that the user account and password are correct.

I would appreciate your assistance in identifying why the access node cannot authenticate to the standalone Hyper-V host and how to resolve this credential/communication issue.

Thank you.

    Mohammed Ramadan

    2 replies

    Mohammed Ramadan
    Forum|alt.badge.img+6

    hello ​@Fawzi 

    Hope you're having a great day, my friend.

    Let's start with some basic troubleshooting. Could you please check if you can ping the Hyper-V host from the CS machine using the hostname? Also make sure the required ports are open port 8400 if they are in the same subnet or 8403 if they re on different networks.

    If all of that looks good and still facing same issue I recommend installing the agent manually on the Hyper-V host. You can copy the installation package to the Hyper-V machine and install at least the File System Core and File System agents. Once the installation is complete, refresh the CommCell Console and you should see the Hyper-V client appear then you can add hyper v agent 


    Let me know how it goes, and if you run into any issues or have any doubts

    Best Regards,
    Mohammed Ramadan
    Data Protection Engineer

    https://www.linkedin.com/in/eng-mohammed-ramadan/
    Jennifer Kelley
    F
    Arvind
    Vaulter
    Forum|alt.badge.img+5
    • ArvindVaulter
    • Vaulter
    • November 27, 2025

    Good Day ​@Fawzi,

    Adding to fewer pointers shared by ​@Mohammed Ramadan. I would start with verifying on the below flow: 

    1. Network Connectivity

    Make sure the access node can actually reach the hypervisor.

    • Try pinging the host from the access node.

    • Confirm DNS is resolving the host name correctly.

    • Check that the required ports are open (VMware: 443/902, Hyper-V: 135/445 + dynamic RPC).

    • Tools like cvping can help confirm port access.

    2. Credentials

    Double-check the credentials configured in Commvault.

    • Username and password should be correct.

    • The account needs admin-level rights on the VM host.

    • Also confirm the account isn’t locked or disabled.

    3. Access Node Setup

    Verify the access node being used is actually healthy and online.

    • For Hyper-V, the VSA needs to be installed on the physical host.

    • Make sure the right access node is assigned to the hypervisor.

    4. Hyper-V WMI Connectivity

    If Hyper-V is involved, try connecting via wbemtest from the access node:

    • Namespace: \\<HostName>\root\virtualization\v2

    • Use the same credentials as in Commvault.
      If it fails, it’s usually firewall or permission related.

    Reference: https://learn.microsoft.com/en-us/intune/configmgr/develop/core/understand/introduction-to-wbemtest
     

    5. Firewall/Security Rules

    Confirm that nothing is blocking communication between the access node and the VM host. ICMP (ping) and required TCP ports should be allowed.
     

    6. Logs

    Check the access node logs (cvd.log, vsdiscovery.log and vsbkp.log) for any error details that point to the root cause.

    7. Re-enter Credentials in Commvault

    Sometimes it’s just a stale credential. Try re-entering and validating the credentials in Command Center or the CommCell Console.

    If still an issue, I would suggest to make an ticket with Commvault Support, we can review what's going on. Feel free to let me know if any additional questions or concerns, thank you!

    - Cheers, Arvind
    Jennifer Kelley
    P
    F
    Terms & ConditionsCookie settingsAccessibility statement