Skip to main content
Answer

Veeam server upgraded from v12.3 to v13.0.1. File1 is connecting fine but File2 is not

  • December 6, 2025
  • 2 comments
  • 19 views

EDIT: Title is misleading.  File2 is connecting fine but File1 is not.

(Inventory right now)
______________________________

Veeam backup server (backup1) running enterprise plus 13.0.1.180. Windows Server 2022

File1 and File2 on Windows Server 2022.  

All three servers are joined to the domain. 
______________________________

(Story)

Backup1 was running 12.3.2.3617, upgraded it to 12.3.2.4165.  After the upgrade I was able to successfully run backups on both file servers fine.  Decided to take the plunge and upgrade to v13.  This is where things started to fall apart.
File2 is connecting to Backup1 and taking backups fine.
File1 is not.  

(Where I am at now)
The issue with File1 one is Failed File1: Failed to upgrade host components. 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.' (0:01:04)

The credentials used to connect to both File1 and File2 are the same account.  The account happily named “veeam-sa” to connect from the Backup1 to File1 and File2.  Veeam-sa is a domain admin with local Administrator rights to both File1 and File2

I’ve attempted to reinstall the agent on File1, I’ve attempted to remove and readd File1 agent on the Veeam backup server, but I’m still not successful in getting the Veeam backup server to connect to File1.  "Test-NetConnection File1 -Port 6160" says it connects fine.  

(Things I haven't troubleshooted)
There are two backup proxies that handle the moving of files.  Prox1 and Prox2.  I'm a little new working with Veeam so I'm not sure how they play into all of this.  

Thanks in advance. 

Best answer by cadillac

Please mark this as resolved.

The issue was the internal firewall was blocking traffic.  Rule was set in place to allow all traffice from backup1 to the file servers.  It’s now working as intended. 

2 comments

  • Author
  • Not a newbie anymore
  • Answer
  • December 6, 2025

Please mark this as resolved.

The issue was the internal firewall was blocking traffic.  Rule was set in place to allow all traffice from backup1 to the file servers.  It’s now working as intended. 


coolsport00
Forum|alt.badge.img+21
  • Veeam Legend
  • December 6, 2025

Hi ​@cadillac -

As the poster, making the comment you did, stating the resolution, and marking it as “best answer” is marking a post as resolved...just FYI 😊 I marked your comment as Best Answer as what the issue was for you.

Thank you for following up what the issue was for you.

Best.