Question

Veeam backup and replication error port 2500

  • 24 November 2021
  • 2 comments
  • 88 views

Hi,

I had some errors on a Veeam Backup and Replication 11.0.1.1261 (latest): 
Backup from a dedicated backup server and the target is a physical windows machine that uses Veeam Agent 5.0.1.4584 (latest) 

Error: 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 %IPADRESS%:2500

Backup job is managed by Backup server.
Port 2500 is opened in both directions, and  Kaspbersky Security is used and the Veeam processes are whitelisted. Have applied several fixes from the forums but the problem keeps occuring when backup is made from this specific machine only. And the first run is often faulty but when executed a second run it works without any errors.
 

This text is from nov 1st, i have updated the software to the latest and problem still occurs. 
the NAS and the backup object are online all the time and on same subnet. 
 

thanks
 

 


2 comments

Userlevel 1

Port 2500 is just the starting port, depending on the number or actions being carried out the server may need quite a few above that. Try opening it up a bit, say 2500 to 3000.

Make sure the othe required ports are open too, see this guide.

 

https://helpcenter.veeam.com/docs/backup/agents/used_ports.html?ver=110

 

Please reply to say how it goes.

Port 2500 is just the starting port, depending on the number or actions being carried out the server may need quite a few above that. Try opening it up a bit, say 2500 to 3000.

Make sure the othe required ports are open too, see this guide.

 

https://helpcenter.veeam.com/docs/backup/agents/used_ports.html?ver=110

 

Please reply to say how it goes.

Hi Kevin,
I have followed that guide and opened the port range in the firewalls 2500-3000 on both the backup server and the target that the backup agent is running on.

I have another server on same network that runs without problems but this specific server sometimes have this problem. When the job is executed later with a retry it works without problems.
This server do have an ancient OS and compatibility might be the issue here i guess.
I have followed every guide regarding this and even changed the hosting port.
Don’t know what to do more regarding this recurring issue. 1/10th backup this error occurs during a long period of many windows updates, reboots and Veeam Backup & Replication updates as well.
The Agents are updates as well after each server application upgrade.

 

 

Comment