Connection to Veeam Agent is not available

Hi, we are going to need some more context here,
is it a fresh install?
is it old?
did you check the system’s services that they are up?

If the error persists, contact support.

cheers.

Hello,

This is not fresh install, all services is running normally. Yes i already open ticket and waiting respond from veeam support.

Hi @hs08 -

I assume you’re attempting to perform the restore on the same system you’re running the Veeam Agent on? What it looks like to me is something else may be using port 9395. Try using netstat on your workstation to see what may be using that port, for example:

netstat -nao | find “9395”

Let us know.

Hi @coolsport00 

Of course i perform on same veeam agent server for restoring. I can see port 9395 is listened

Hi @hs08 

as you can see from your screenshot, 9395 port is internal for agent and all Veeam services. 

established or time_wait status is from localhost to localhost. 

I can suppose some changes in Windows OS as Firewall or antivirus/xdr. 

Can you check local firewall or antivirus and its exclusion? 

Please let us know

Hi @hs08 - ok; it appears all good there. Although, instead of using “-nao” options for netstat, I’d try “-sao” or just “-ao”. This way, the output shows the protocol using the port by name and not solely by number. This is just to verify the process using the port is what we want, in this case Veeam.

If that looks good, I agree with Antonio as far as nex steps and make sure if you use an Antivirus software, you have A/V temporarily disabled, or at the very least have folder exclusions. And even though you’re performing restore on the same machine you use the Agent on, local Firewall can pose issues sometimes. I’d temporarily disable that too and re-attempt the restore. Also, if you have UAC enabled, please disable that and then re-attempt the restore. Try all those things, if you haven’t already, and see if you have file restore success.

Thank you.

Another real quick test if you can is reboot the agent computer and then try again.  If there is/was something using the port, etc. then it should work after that.  This is the good old reboot fix for Microsoft.  😂

Hi @hs08 -

I’m just following up on your post here. Are you still having issues? Still have questions?...or, were you able to resolve the problem? If any of the provided comments helped you out, we ask you mark which comment helped you as ‘Best Answer’ so others with a similar issue who come across your post may benefit.

Thank you.

Hi @hs08  - I just wanted to follow up to see if you were able to resolve your issue with one of the posted comments or if you found another solution.  If you could update the thread and if one of the comments helped you mark that as best answer or if you found another solution post it and then mark it as best answer that would be great.  It will help others and the community to get answers/details for similar problems.