Skip to main content
Question

NFC storage connection is unavailable. Storage Failed to create NFC download stream

  • November 21, 2023
  • 10 comments
  • 2119 views

NFC storage connection is unavailable.
. Storage Failed to create NFC download stream

10 comments

MicoolPaul
Forum|alt.badge.img+23
  • 2425 comments
  • November 21, 2023

Hi, can you provide some extra context. Is this for a particular VM, or server, or every backup job? What version of vsphere are you using? What version of Veeam are you using?


Chris.Childerhose
Forum|alt.badge.img+21
  • Veeam Legend, Veeam Vanguard
  • 9587 comments
  • November 21, 2023

As per Michael we need more details to try to help out. Also check the logs here C:\ProgramData\Veeam\Backup


coolsport00
Forum|alt.badge.img+21
  • Veeam Legend
  • 4903 comments
  • November 21, 2023

@compute - As noted, we do need more info to assist. Can you share a screenshot of the error and what step you’re getting it on? I assume from a Backup job, but don’t wanna be too presumptuous.


coolsport00
Forum|alt.badge.img+21
  • Veeam Legend
  • 4903 comments
  • February 16, 2024

Hi @compute -

I’m just following up on your NFC Storage error post. Do you still have a problem? If not, can you share what you did to resolve your issue? Or if still not resolved, can you provide further info so we can try to assist?

Thank you.


I Have the same problem for all backup jobs, how can we fix this?

 


coolsport00
Forum|alt.badge.img+21
  • Veeam Legend
  • 4903 comments
  • May 27, 2025

@nikolapintaric -

I recommend you get in touch with Veeam Support.


Marcel.K
Forum|alt.badge.img+9
  • Veeam Legend
  • 297 comments
  • May 27, 2025

its typically if you have an issue with dns of vcenter or esx hosts

for example if one esx lost dns record like proxy server is not able to resolve ip of esx or certificate of vcenter could be as well


Scott
Forum|alt.badge.img+9
  • Veeam Legend
  • 1110 comments
  • May 27, 2025

I vote DNS or firewall rules.  Open a ticket, check your logs, and check your firewall, try and ping everything from within the Veeam proxies and repos. 

I had this pop up recently when someone reloaded an ESXi host, but changed the subnet.  


Marcel.K
Forum|alt.badge.img+9
  • Veeam Legend
  • 297 comments
  • May 27, 2025

I had such an issue in April, when someone enabled on esx host local firewall and port 902/tcp was blocked from VBR/proxy server.


Mohamed Ali
Forum|alt.badge.img+2
  • VUG Leader
  • 85 comments
  • May 28, 2025

I also faced similar issue when port 902 was blocked from the VBR to the ESXi host. Please check the communication from VBR to ESXi hosts