Repository Storage failed to connect

[Robsoncb]

Hello,
In my scenario, I made a Vm VBR with an internal network, IP 10.0.252.2/24, gw 10.0.252.1/24. This IP is for management and will communicate with the VMS for backup.
In another network card of the VBR, which communicates with the immutable Linux repository I have the IP 10.201.14.1/24, and in the repository the IP 10.201.14.2/24. In this network segment I don't have a Gateway, because 2 gateways in the same VM not Because 2 gateways in the same VM, it doesn't work very well.

But when running the backup, it starts, creates a vbk in the repository, but at the end an error occurs, informing that the time limit has expired, and it cannot communicate with the IP of the repository 10.201.14.2 on port 2501:
03/14/2023 20:32:20 :: Processing VMTESTE Error: Failed to connect to the endpoint [10.201.14.2:2501]. A connection attempt failed because the connected party did not respond properly after a period of time, or established connection failed because the connected host has failed to respond.
I already removed it, added the linux and the repository again, but I still have errors.
I also went to network traffic rules, I created a rule for the rule for the range 10.201.14.1 - 10.201.14.255 in the source and target, and I also added the network 10.201.14.0/24 in preferred networks, to the repository, but it didn't solve the problem.

Does anyone have an idea why it's giving this error?

[HannesK]

Hello,
it looks like, the port requirements are not met. I don't have the full network picture, but it sounds like the Hyper-V cannot connect to the Hardened Repository.

If that's not the right guess, please open a support case as requested when you click New Topic.

Best regards,
Hannes

[Robsoncb]

Hello,
I open a ticket for this Case #05949640.

[Robsoncb]

Sorry,
The ticket is 05949721