Veeam Proxy server failing with SOAP connection error

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.
LVL 1
bensonwalkerAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Mr TorturSystem EngineerCommented:
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
0
bensonwalkerAuthor Commented:
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.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Veeam

From novice to tech pro — start learning today.