#1 Global Leader in Data Protection & Ransomware Recovery

"Established connection failed because connected host has failed to respond <vbr_ip>:10005"

KB ID: 4557
Product: Veeam Backup & Replication | 11 | 12 | 12.1
Veeam Agent for Microsoft Windows | 5.0 | 6.0 | 6.1
Published: 2024-03-13
Last Modified: 2024-03-18
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please try again later.

Challenge

A Windows Agent Backup or Windows Agent Policy type job within Veeam Backup & Replication fails with either of the following errors.

  • A Veeam Agent Backup operating in Managed by backup server fails with the error:

    Error: Managed session has failed: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond <vbr_ip>:10005
    
  • A Veeam Agent Policy fails to deploy with the following error:

    Failed to send backup job configuration to <machine> Error: Failed to update backup job 
    Managed by agent job ID: <job_id_guid>. 
    Managed by agent job name: <job_name>.
    Invalid job configuration.
    Connection problems.
    Exception has been thrown by the target of an invocation.
    Failed to establish connection: no valid IP addresses were found.
    A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond <vbr_ip>:10005  
    
Similar Ports in Errors

This article is regarding Veeam Agent for Microsoft Windows deployments that are managed by Veeam Backup & Replication and use the port 10005. Other nearby ports are used for similar purposes:

  • 10001 — Port used by Standalone Veeam Agent for Microsoft Windows Deployments to communicate with Veeam Backup & Replication.
  • 10002 — Legacy port used by older versions of Veeam Agent for Linux to communicate with Veeam Backup & Replication.
  • 10003 — Port used for Veeam Cloud Connect communication from Backup Server to Backup Server.
  • 10004 — Unused
  • 10005 — Port used by Managed Deployments of Veeam Agent for Microsoft Windows to communicate with Veeam Backup & Replication.
  • 10006 — Port used by Veeam Agent for Linux and Veeam Agent for Mac to communicate with the Veeam Backup Server.
Third-Party Software Port Conflicts

While firewalls blocking port communication remains the most common cause of support cases, Veeam Support has seen a marked increase in the number of cases caused by the Cloud Agent of Qualys vulnerability scanner, as it shares many of the same default ports:

"During an unauthenticated scan using the Qualys scanner, the Cloud Agent will return its Correlation ID to [the] scanner over one of the Agent Scan Merge ports (10001, 10002, 10003, 10004, 10005)."

The ports used by the Agent Scan Merge can be customized: Agent Correlation Identifier.

Cause

These errors occur when the Windows machine where Veeam Agent for Microsoft Windows is installed cannot reach the Veeam Backup Service on the Veeam Backup Server over port 10005.

This may occur if:

  • The machine where Veeam Agent for Microsoft Windows is deployed cannot resolve the hostname or FQDN of the Veeam Backup Server.
  • The Veeam Backup Service could not assign itself port 10005 when it started because another application already used that port.
  • A firewall in the environment is blocking traffic between the machine where Veeam Agent for Microsoft Windows is installed and the Veeam Backup Server.
    • Firewall on the Veeam Backup Server
    • Firewall on the Windows machine itself.
    • Firewall in the network (if the traffic is crossing them).

Solution

A complete guide on how to test port connectivity can be found on KB4444.
Troubleshooting Checklist
  • Ensure that the Veeam Backup Service on the Veeam Backup Server is associated with port 10005.
Get-Process -Id (Get-NetTCPConnection -LocalPort 10005).OwningProcess
Port Ownership
If the process listed is not Veeam.Backup.Service, investigate why that process is using the port. If the third-party software can be reconfigured to use a different port, it is advised to reconfigure it rather than the Veeam software. It is possible to change the port Veeam Backup & Replication uses to receive traffic from the Veeam Agent for Microsoft Windows deployments. See the More Information section for information about changing the port used by Veeam Backup & Replication for receiving managed Veeam Agent for Microsoft Windows deployment traffic.
  • Ensure that the Windows machine being backed up can correctly resolve the the hostname and FQDN of the Veeam Backup Server.
nslookup <vbr_fqdn>
ping <vbr_fqdn>
nslookup and ping
Note: The success of ping is not necessary for the functionality of agent management. The ping is only intended to confirm that the machine's local DNS uses the data received from the DNS server, as shown in the nslookup results.
  • Ensure that the Windows machine being backed up can reach port 10005 on the Veeam Backup Server.
Test-NetConnection -ComputerName <vbr.server.ip> -Port 10005
TestNetConnection

More Information

Customize Port Used To Recieve Communication

If you are facing a situation where another product is using port 10005, and that third-party software cannot be adjusted to use a different port, Veeam Backup & Replication can be configured to listen on a different port for communication from managed Veeam Agent for Microsoft Windows deployments.

Considerations and Limitations

Changing the port that managed Veeam Agent for Microsoft Windows deployments use to communicate with Veeam Backup & Replication will cause them to lose contact with Veeam Backup & Replication until their configuration is updated to make them aware of the port change.

  • For machines not in a Computer with pre-install backup agents type Protection Group, when Veeam Backup & Replication connects out to the Veeam Agent for Microsoft Windows deployment (job start or protection group rescan), it will update that deployment with the new inbound communication port.
  • For machines in a Computer with pre-install backup agents type Protection Group, each machine must be manually reconfigured to communicate with Veeam Backup & Replication over the new port. This is because machines in that type of Protection Group cannot have a configuration pushed out to them; they receive their configuration instead by periodically contacting the Veeam Backup & Replication server to see if their job settings have changed. Therefore, changing the inbound communication port causes them to no longer be able to reach the Veeam Backup & Replication software. To update the machine in this type of protection group, either:
    • Update configuration using the Configurator — Generate a new pre-configured deployment package, copy the <protection_group_name>.xml configuration file to the Windows machine, then use the following command to update the configuration:
      "C:\Program Files\Veeam\Endpoint Backup\Veeam.Agent.Configurator.exe" -setVBRsettings /p:"<protection_group_name>.xml"
      
      or
    • Update the port by editing the registry — Edit the SerializedConnectionParamsstring value in the [HKLM\SOFTWARE\Veeam\Veeam EndPoint Backup] key on the Windows machine. The string value will contain a port number; update that to match the port selected on the Veeam Backup Server.
      <?xml version="1.0"?><ConnectionParams ConnectionPoint="VBR.domain.tld" Port="10005"><IpAddresses>10.0.0.115</IpAddresses></ConnectionParams>
      
 
Registry Value

Create the following registry value on the Veeam Backup Server.

Key Location: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\
Value Name: EndPointServerSslPort
Value Type: DWORD (32-Bit) Value
Value Data(Dec): 10005 (Default)

To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.