Skip to main content
Solved

Error: Failed to get client information from CommServe.

  • October 16, 2022
  • 3 replies
  • 1984 views

Forum|alt.badge.img+3

Hi,

We are trying to install Commvault VSA agent to a VM from Azure public.(Manually from the VM side and not pushing from the commserve) We are getting following error…

 

We checked remote registry services and firewall ports, 135,139,445,8400,8402,8403. all are opened from existing firewall. Kindly help us figuring out this issue.

Best answer by Niall

Hi @Charith 

In addition to the Windows Firewall and any network Firewalls, Azure uses Network Security Groups - basically access control lists for network communication - you will need to ensure that these are configured to allow traffic through too. 

I would start by double checking that both the proxy and the Commserve can resolve each others hostnames - if they can, then I recommend you actually test the connectivity on the Commvault ports each way between the proxy and the Commserve. The error from your first post reads as a connectivity issue, the error from your second post reads as a DNS or connectivity issue. 

HTH

Niall

 

View original
Did this answer your question?

3 replies

Forum|alt.badge.img+3
  • Author
  • Byte
  • 8 replies
  • October 16, 2022

In the logs we could see the following  error message as well.

 

Error: Failed to get client information from CommServe

 

Since all the username/psswrd is correct and remote registry service is running from both commserve and azure VM side, Is this really a connectivity issue ? or are there any services from commvault side that needs to be checked ?


Niall
Vaulter
Forum|alt.badge.img+8
  • Vaulter
  • 35 replies
  • Answer
  • October 17, 2022

Hi @Charith 

In addition to the Windows Firewall and any network Firewalls, Azure uses Network Security Groups - basically access control lists for network communication - you will need to ensure that these are configured to allow traffic through too. 

I would start by double checking that both the proxy and the Commserve can resolve each others hostnames - if they can, then I recommend you actually test the connectivity on the Commvault ports each way between the proxy and the Commserve. The error from your first post reads as a connectivity issue, the error from your second post reads as a DNS or connectivity issue. 

HTH

Niall

 


Forum|alt.badge.img+3
  • Author
  • Byte
  • 8 replies
  • October 19, 2022

Thanks @Niall It was a DNS issue afterwall. Really appreciate your help.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings