Can you share the screenshot of the error?

Hi @Nolzzz.

So you’re supplying Veeam Cloud Connect services to a customer with Hyper-V hosts available for replication services is that correct?

The key information is missing here as we need to see the logs from the customer’s VBR server AND the VCC cloud gateway/gateway pool to see if the problem is communication from customer to VCC or your gateway speaking to the Hyper-V server.

As this is a new host standup, have you checked that the cloud gateway server can ping the Hyper-V host and resolve any DNS records successfully? I’d start with the basic network connectivity tests and build up from there.

Error attached

Yes, the cloud gateway can ping the Hyper V host. Support has reviewed the logs and saw no issues, but i am still talking to them.

Thanks, is this a single cloud gateway or a gateway pool?

This is a communication issue error, so the likely culprits are DNS or firewall if ping is working.

Thank you. Its always something small that you miss.

I have 2 NICs - one with a gateway and 1 without.

needed to define how to get to the network on the NIC with no gateway.

Yeah having this setup needs a static route for your non gateway NIC.  Hopefully that resolves your issue.

Thanks guys, you are all stars.

Hi @Nolzzz

the classic problem of multihomed servers.
Static route fix the problem as mentioned by  @Chris.Childerhose 

regards

Happy to help, don’t forget to mark the best response as the answer to help the next person please!

Heck yeah they are!

But a different answer has been marked! I think both are driving us in the right direction.

Yeah was sad to not see my answer. Oh well it is there for all.