Veeam Proxy server failing with SOAP connection error

bensonwalker
bensonwalker used Ask the Experts™
on
We're trying to set up a veeam proxy server/rep jobs for a new client. Due to an overlapping network between an existing client and the new client, we have their firebox translate the network to .30 when coming back and forth. This translation works in veeam (their servers show up), we can ping and pull up their drive shares from our side. The only place it's not working is when veeam goes across using the proxy server and tries to talk to the host at .30.250. We get the following error when starting the job using the proxy server...

Processing FS1 Error: Cannot get service content. Soap fault. TimeoutDetail: 'connect failed in tcp_connect()', endpoint: 'https://xxx.xxx.30.250:443/sdk' SOAP connection is not available. Connection ID: [xxx.xxx.30.250]. Failed to create NFC download stream. NFC path: [nfc://conn:xxx.xxx.30.250,nfchost:ha-host,stg:582f26be-c7f9cf95-50d7-2880231c4740@FS1/FS1.vmx].

We already tried editing the host file by adding the .30 address to it. Didn't help though. So my thinking is, can we add another nic card to the host, give it the .30 network and have it function along side the existing network? Will it work the way i want it to work? Is there something else we can try?

I get why veeam is holding onto the .30 address but there has to be some way around overlapping networks like this. I'm sure we're not the first company to run into this scenario.

Please let me know if you need additional info or logs. Thank you in advance.
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Mr TorturSystem Engineer

Commented:
Hi,
Not entirely clear for me... but it could be my bad english understandings ;-)

Who is the 30.250 machine ?

In order for your Veeam jobs to work using proxy :
- Veeam server must communicate with the hypervisor where the VM to backup/replicate lie
- proxy server must communicate with the hyperivsor too
We are able to fix this by adding the IP and DNS name of the client machine to the host file on our side where we run the veeam jobs.

Thank you for your response.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial