Veeam Failed to connect to the port [xx.xx.xx.xx:2501].

If you are using Veeam for HyperV and onhost mode enabled you may receive an error like below.

Processing ‘VMName’ Error: Client error: Failed to connect to the port [ProxyIPAddress:2501].
Guest processing skipped (check guest OS VSS state and integration components version)
Error: Client error: Failed to connect to the port [ProxyIPAddress:2501].

Actually it is strange that it was working yesterday but today I met this error for the same job. anyway, to investigate the issue I check firewall traffic to see what traffic is passing through veeam proxy.

8.971765 HyperVNodeIPAddress.64095 -> VeeamProxyIPAddress.2502: syn 1651429723
8.971787 HyperVNodeIPAddress.64095 -> VeeamProxyIPAddress.2502: syn 1651429723
8.971788 HyperVNodeIPAddress.64095 -> VeeamProxyIPAddress.2502: syn 1651429723
8.971790 HyperVNodeIPAddress.64095 -> VeeamProxyIPAddress.2502: syn 1651429723
8.972030 VeeamProxyIPAddress.2502 -> HyperVNodeIPAddress.64095: syn 1824638411 ack 1651429724
8.972043 VeeamProxyIPAddress.2502 -> HyperVNodeIPAddress.64095: syn 1824638411 ack 1651429724
8.972045 VeeamProxyIPAddress.2502 -> HyperVNodeIPAddress.64095: syn 1824638411 ack 1651429724
8.972050 VeeamProxyIPAddress.2502 -> HyperVNodeIPAddress.64095: syn 1824638411 ack 1651429724
8.974483 HyperVNodeIPAddress.64095 -> VeeamProxyIPAddress.2502: ack 1824638412
8.974490 HyperVNodeIPAddress.64095 -> VeeamProxyIPAddress.2502: ack 1824638412
8.974492 HyperVNodeIPAddress.64095 -> VeeamProxyIPAddress.2502: ack 1824638412
8.974493 HyperVNodeIPAddress.64095 -> VeeamProxyIPAddress.2502: ack 1824638412
8.974495 HyperVNodeIPAddress.64095 -> VeeamProxyIPAddress.2502: psh 1651429724 ack 1824638412
8.974499 HyperVNodeIPAddress.64095 -> VeeamProxyIPAddress.2502: psh 1651429724 ack 1824638412
8.974500 HyperVNodeIPAddress.64095 -> VeeamProxyIPAddress.2502: psh 1651429724 ack 1824638412
8.974501 HyperVNodeIPAddress.64095 -> VeeamProxyIPAddress.2502: psh 1651429724 ack 1824638412
9.222199 HyperVNodeIPAddress.64096 -> VeeamProxyIPAddress.2500: syn 1901637618
9.222217 HyperVNodeIPAddress.64096 -> VeeamProxyIPAddress.2500: syn 1901637618
9.222218 HyperVNodeIPAddress.64096 -> VeeamProxyIPAddress.2500: syn 1901637618
9.222220 HyperVNodeIPAddress.64096 -> VeeamProxyIPAddress.2500: syn 1901637618
9.222681 VeeamProxyIPAddress.2500 -> HyperVNodeIPAddress.64096: syn 467214191 ack 1901637619
9.222690 VeeamProxyIPAddress.2500 -> HyperVNodeIPAddress.64096: syn 467214191 ack 1901637619
9.222691 VeeamProxyIPAddress.2500 -> HyperVNodeIPAddress.64096: syn 467214191 ack 1901637619
9.222693 VeeamProxyIPAddress.2500 -> HyperVNodeIPAddress.64096: syn 467214191 ack 1901637619
9.230036 HyperVNodeIPAddress.64096 -> VeeamProxyIPAddress.2500: ack 467214192
9.230045 HyperVNodeIPAddress.64096 -> VeeamProxyIPAddress.2500: ack 467214192
9.230047 HyperVNodeIPAddress.64096 -> VeeamProxyIPAddress.2500: ack 467214192
9.230048 HyperVNodeIPAddress.64096 -> VeeamProxyIPAddress.2500: ack 467214192
9.230051 HyperVNodeIPAddress.64096 -> VeeamProxyIPAddress.2500: psh 1901637619 ack 467214192
9.230054 HyperVNodeIPAddress.64096 -> VeeamProxyIPAddress.2500: psh 1901637619 ack 467214192
9.230056 HyperVNodeIPAddress.64096 -> VeeamProxyIPAddress.2500: psh 1901637619 ack 467214192
9.230057 HyperVNodeIPAddress.64096 -> VeeamProxyIPAddress.2500: psh 1901637619 ack 467214192
9.702185 HyperVNodeIPAddress.64097 -> VeeamProxyIPAddress.2500: syn 1316321474
9.702202 HyperVNodeIPAddress.64097 -> VeeamProxyIPAddress.2500: syn 1316321474
9.702217 HyperVNodeIPAddress.64097 -> VeeamProxyIPAddress.2500: syn 1316321474
9.702219 HyperVNodeIPAddress.64097 -> VeeamProxyIPAddress.2500: syn 1316321474
9.702623 VeeamProxyIPAddress.2500 -> HyperVNodeIPAddress.64097: syn 2219436463 ack 1316321475
9.702633 VeeamProxyIPAddress.2500 -> HyperVNodeIPAddress.64097: syn 2219436463 ack 1316321475
9.702634 VeeamProxyIPAddress.2500 -> HyperVNodeIPAddress.64097: syn 2219436463 ack 1316321475
9.702639 VeeamProxyIPAddress.2500 -> HyperVNodeIPAddress.64097: syn 2219436463 ack 1316321475
9.727047 HyperVNodeIPAddress.64097 -> VeeamProxyIPAddress.2500: ack 2219436464
9.727056 HyperVNodeIPAddress.64097 -> VeeamProxyIPAddress.2500: ack 2219436464
9.727058 HyperVNodeIPAddress.64097 -> VeeamProxyIPAddress.2500: ack 2219436464
9.727059 HyperVNodeIPAddress.64097 -> VeeamProxyIPAddress.2500: ack 2219436464

As you can see HyperV Node owning the VM is trying to access Veeamproxy and 2502/2500 are also used.( you may change these ports while installing agents).. I wish proxy would first initiate the session but revere is happening :)

So make sure that hyperV nodes are reaching Veaam Proxy agents. That solves the problem.

Leave a Reply