Unable to install veeam windows agent remotely from backup server version 13

Hi Bennet, 

What is the output on the console when starting the process?  Are you using Protection Groups? 

Regards

ShaunB.

Yes, The server is part of protection group below is the error:

 Failed : Unable to install backup agent: failed to connect to <server name >

Error: Failed to connect with deployment kit. (Failed to connect with deployment kit on <server>:6160: 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.) (Failed to connect with deployment kit on <server>:11731: Unable to establish connection: timeout reached.).

Hi ​@Bennet ,

I would first double-check the ports.

You mentioned ports 6160 and 11735, but the error shows Veeam trying to connect on 6160 and 11731. So I would confirm if TCP 11731 is allowed from the Veeam Backup Server to the target server.

Also, I had a similar issue recently where the problem was not the firewall, but another Windows service using port 6160. In my case, the Print Spooler service was listening on port 6160, causing the Veeam deployment to fail.

You can check it on the target server with:

netstat -ano | findstr :6160

Then check the PID:

tasklist /FI "PID eq <PID>"

If another service is using port 6160, stop/adjust that service and retry the Veeam Agent deployment.

It does appear that 6160 is shared by another PID as well:

Please find below:

PS C:\WINDOWS\system32> netstat -ano | findstr :6160
  TCP    0.0.0.0:6160           0.0.0.0:0              LISTENING       3052
  TCP    0.0.0.0:6160           0.0.0.0:0              LISTENING       13792
  TCP    [::]:6160              [::]:0                 LISTENING       13792

PS C:\WINDOWS\system32> tasklist /FI "PID eq 3052"

Image Name                     PID Session Name        Session#    Mem Usage
========================= ======== ================ =========== ============
spoolsv.exe                   3052 Services                   0    109,060 K

PS C:\WINDOWS\system32> tasklist /FI "PID eq 13792"

Image Name                     PID Session Name        Session#    Mem Usage
========================= ======== ================ =========== ============

VeeamDeploymentSvc.exe       13792 Services                   0     23,400 K
PS C:\WINDOWS\system32>
 

You have any idea of what that other service is ​@Bennet using 6160? Maybe it’s just a random Windows Service & a reboot would cause it to use a different port upon startup? Have you tried that? If this is what I think it is, it’s the service responsible for Printing. (Print Spooler) At the very least, try stopping that service for a bit then re-attempt to deploy. See if that works.

I think server reboot was done recently and the print spooler service again picked port 6160 . Also I did check on another server on which the veeam agent backup is running fine and as well find the same spooler service using port 6160.

PS C:\Windows\system32> netstat -ano | findstr :6160
  TCP    0.0.0.0:6160           0.0.0.0:0              LISTENING       4364
  TCP    10.4.4.7:59319         10.12.84.25:61603      ESTABLISHED     8228
  TCP    10.4.4.7:59319         10.34.4.55:61602       ESTABLISHED     8228
  TCP    [::]:6160              [::]:0                 LISTENING       4364

PS C:\Windows\system32> tasklist /FI "PID eq 4364"

Image Name                     PID Session Name        Session#    Mem Usage
========================= ======== ================ =========== ============
VeeamDeploymentSvc.exe        4364 Services                   0     29,264 K

PS C:\Windows\system32> tasklist /FI "PID eq 8228"

Image Name                     PID Session Name        Session#    Mem Usage
========================= ======== ================ =========== ============
spoolsv.exe                   8228 Services                   0    299,540 K
PS C:\Windows\system32>
 

A quick search did confirm the spoolsv.exe is indeed the Print Spooler service. Try stopping it and attempt to deploy. Do you need printing on your Veeam Server? If not, just disable it and that would take care of that issue. Interesting Windows chose a port already in use by Veeam; although...I guess it’s not continually in use...only when Agent deployment is needed. Try that & let us know how it goes.

it is not on a veeam server, trying to deploy veeam windows agent remotely on an application server that requires veeam backup. I am checking with concern team if this can be disabled / stopped. Thank you

Ah, ok.. understood.

Ok...keep us posted what they say & how it goes. At least we have an idea what is potentially causing the conflict.