Skip to main content
Solved

Question on Remote Console connection requirements on map feature

  • April 30, 2026
  • 2 comments
  • 27 views

Forum|alt.badge.img+3

https://www.veeam.com/calculators/maps

Very neat feature, but a question comes up while testing a few scenarios:

 

  1. Why does remote console need connection to non-hardened repositories, but not the hardened one here?
  2. The ports tell about “file restore”, but I’m not sure on the source of this, as I don't see this in the ports list (Note: I’m aware this list is suspect, we’re working on it but point is more what is the source that we need Remote Console => repo connections for file restore?)
    1. If you're talking about mounting to console, I can understand but doesn’t hardened repository need this also?

 

Best answer by tsmith

Hey David, good catch!

those ports are listed under “common ports” here: https://helpcenter.veeam.com/docs/vbr/userguide/used_ports.html?ver=13#common-ports

and you are correct, it should exist for the hardened repo as well. This was missed as the hardened repo was added later on in the process, and apparently didn’t inherit the rule.  It will be added to the list!

 

2 comments

tsmith
Forum|alt.badge.img+5
  • Veeam MVP
  • Answer
  • April 30, 2026

Hey David, good catch!

those ports are listed under “common ports” here: https://helpcenter.veeam.com/docs/vbr/userguide/used_ports.html?ver=13#common-ports

and you are correct, it should exist for the hardened repo as well. This was missed as the hardened repo was added later on in the process, and apparently didn’t inherit the rule.  It will be added to the list!

 


Forum|alt.badge.img+3
  • Author
  • Experienced User
  • May 4, 2026

Great, thanks for the answer ​@tsmith

 

I would add in an additional request then, can we mark 2500-3300 as “optional failover” somehow in this tool? To best of my knowledge, most all places where 2500-3300 used to be required it is now optional as a failback, everything should go through 6162 now I suppose