Loading...
Loading...
FLR browse operation fails with the following error: Browser: Unable to establish a connection with the client. javax.net.ssl.SSLPeerUnverifiedException: Peer not authenticated Avagent logs show failed IP resolution and rejected inbound connections: agent_message::resolve_client_ip ping to MCS AvamarserverFQDN:10.10.10.X using local IP:(none) failed Received inbound connection from an unrecognized address 1.1.1.1:39628, rejecting
The issue occurs when NAT modifies the Avamar server’s IP address for outbound traffic. MCS attempts to connect to the proxy on ports 28009 or 30009 using the NAT IP (for example, 1.1.1.1 ) instead of the original Avamar IP ( 10.10.10.X ). The Avagent rejects the connection because the source IP does not match the registered Avamar IP. Log Location: /usr/local/avamarclient/var/avagent.log
Verify NAT Impact SSH into the Avamar server and connect to the proxy: ssh admin@proxy_IP_or_FQDN Run: who If the output shows the NAT IP (for example, 1.1.1.1 ) instead of the Avamar IP, NAT is causing the issue. Correct Network Configuration Engage the network team to review and adjust firewall/NAT settings. Ensure that the Avamar server communicates with the proxy using its original IP address.
Click on a version to see all relevant bugs
Dell Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.