Failing to connect

[SwindoNut]

We seem to suffer a number of servers saying
"MediaAgent failed to connect back to CommClient".

The agent has been reinstalled, and updates applied from the Commserve (which confirms communication between the client and the Commcell!).
I've tried data interface pairs, host file entries, none work.
Any ideas?

 

[ITtekkie]

Have you checked that both computers are in DNS?
CommVault relies on reverse look-up
Do an nslookup of the agent computer from the main commvault computer and see if returns the IP

 

[SwindoNut]

We ran nslookup, netperf, both returned correct status.
Setup data interface pairs using IP address (not hostname) and resolved the issue.

 

[socrys]

I was having the same issue but when I did an nslookup by name I couldn't get an IP but setting are correct in DNS. I added to the hostfiles and that didn't work, and I am trying to set up DIP's but they aren't giving me the CommServe as an option.

 

[birky]

I've experienced this error before and setting the nics to autosense fixed it...seems strange but, it worked.

 

[ekudinov]

Hi SwindoNut,
I have the same error message, but my Server and client are separated by the FireWall. It's WatchGuard X2500 FireBox. I've configured new service, and open all available ports, but back up failed with "Media Agent failed to connect back to CommClient" error message. When I analyzed the FireWall’s log, it said that communication was refused. The DNS is not an issue, because you can add the IP address of server or client to the hosts file under your “%windir%\system32\drivers\etc\”. All nslookup tests, ping by name and trace routes will be succeeded.
So check if there any firewall or access list on the routers prevents your backup.