I've been running in to strife trying to set up enerprise manager, and I am beginning to wonder if it is a configuration issue, or a software limitation.
I'm trying to set up enterprise manager as follows:
Enterprise server 10.0.0.100
|
NAT Router 203.100.x.x
|
INTERNET
|
NAT router 184.100.x.x
|
Veeam B&R Client 192.168.100.10
So basically, I'm trying to monitor Veeam installs on a client over the net.
I have port 9392 forwarded on the client-side router, and I can telnet to 9392 from the enterprise server, however when I try to add the client to the enterprise server I get the following:
Connection to "Veeam Backup Service" is not available.
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 192.168.100.10:9392 (System.Net.Sockets.SocketException)
I set up a test environment on two systems on separate WAN links, set up through generic NAT routers (with and without DMZ set at both ends), and had the same result every time. Frustrated, I wiresharked the enterprise server, and found that the server was initiating communication using the WAN IP, then after a few seconds starts trying to communicate with the LAN IP (192.168.100.10) obviously gets no response, then throws the error after a minute or so of re-trying.
Is this a genuine limitation of the product? Why is it passing the internal IP for communication? Is there a setting somewhere I can change to let the client/server know it is behind a NAT firewall?
Thanks guys
