Feature Request [Simplify veeam agent listening port conflict]

[TylerVF]

My case number is: #03282257

When running an agent-based backup job for physical Windows servers, I received the following error message: "Error: Managed session has failed. Failed to establish connection: no valid IP addresses were found"

This stumped me as connectivity was any/any both ways and DNS was good. I ended up raising a support case and going down rabbit holes simultaneously investigating the issue myself.
It turns out the solution was a third-party security agent (Qualys) was hogging listening on port 10005. This was hard to diagnose because the firewall was open and I could successfully connect from the agent server to veeam server on that port. Also complicating things, the agent logs specified connecting over an RPC dynamic port was the issue.

Some software solutions to avoid anyone else having this issue could be...
*Veeam raises an error in the B&R console that's more specific. "Windows agent is unable to connect to B&R server on port xxxx. Please check x y z and that no other process is listening on that port"
*Veeam agent attempts on a few different ports instead of one
*As part of the protection group scan, all necessary ports and protocols are checked
I'm sure there are more.

This might not be a top priority, since I'm sure the number of people experiencing this is low. But I'm sure it could save some hair pulling in the future.

[Mildur]

Hi Tyler

Thank you for sharing. It makes sense to enhance error messages for clarity whenever possible.
May I ask, was this error message in our debug logs or in the session details in the backup console?

Can you also please check your case number again? A case number starts with #07. #03 is your contract number.

Best,
Fabian

[TylerVF]

Here is the corrected case number: #07147784

This is the only error that was raised in the backup console:
"Error: Managed session has failed. Failed to establish connection: no valid IP addresses were found"

The agent logs had various errors, what finally led to figuring it out was:
[22.02.2024 15:41:42] <16> Info Networking error: [Exception has been thrown by the target of an invocation.. Failed to establish connection: no valid IP addresses were found.]
[22.02.2024 15:42:02] <16> Info Trying connect to (AddressFamily: 'InterNetwork') IP addresses: ['192.168.XX.XX]
[22.02.2024 15:43:41] <36> Info Received from 192.168.XX.XX:52234

It seems simple when put like this, but it was a 4-5 day ordeal getting everything pinned down

[dariusz.tyka]

I've had similar issue also related to Qualys agent installed on B&R machine. In my case AfW was not able to obtain license from B&R server and I couldn't create a backup job targeted to SOBR repository. Case #07259725
In my case I needed to change via registry port for agent communication from 10001 to sth else (10007) as ports 10001 to 10005 could be used by Qualys agent.

[Mike.Powell]

https://www.veeam.com/kb4557 this KB was recently updated for this specific issue. Qualys gets an honorable mention.

"Third-Party Software Port Conflicts
While firewalls blocking port communication remains the most common cause of support cases, Veeam Support has seen a marked increase in the number of cases caused by the Cloud Agent of Qualys vulnerability scanner, as it shares many of the same default ports:"

Hopefully this will help reduce the confusion when encountering this port conflict.

[jimstumbo]

I've had similar issue also related to Qualys agent installed on B&R machine. In my case AfW was not able to obtain license from B&R server and I couldn't create a backup job targeted to SOBR repository. Case #07259725
In my case I needed to change via registry port for agent communication from 10001 to sth else (10007) as ports 10001 to 10005 could be used by Qualys agent.

Did you have to update the registry just on the B&R server, or also on all the systems with the clients?

[dariusz.tyka]

I needed to update port number via registry only on B&R machine.

[mcostanunes]

dariusz, how are you?

I'm just starting to get involved with Veeam Backup & Replication and I'm facing a situation like the one described in this post, including the same third-party software (Qualys). In the case of this solution of changing the ports in Veeam, could you tell me exactly which ports and which registry keys need to be changed?

Thanks in advance

Marcos Nunes