Hi,

NetWorker can work with NAT. In your case, you need to create a static NAT for the NetWorker server from the client side. If you launch an nsrexecd not as a service / daemon, but just run it like "nsrexecd -D9", you will notice that a backup request comes from an IP address, which is, in fact, an inner firewall leg. The client tries to answer that address and comes to the firewall itself. So, you need to create a static NAT for the NetWorker server and define this address in the "hosts" file of the backup client.

I've added at hosts inside the client the information:
"10.0.10.100 networkerserverR".

Inside the client configuration of the Networker Server, alias, I added:"networkerserver / networkerserverR" - only for the server.

After that, from the client side was possible to start the backup and the recover, now without errors using the GUI.

But starting the backup from the networker server, the backup simply doesn´t start. there's the "connection timeout message".

I´ve tried to do the same for the client ( added the port that is used for the route to communicate to the client and added to the alias, inside networker)

rpcinfo and ping works without error.

Still no news, I opened a case at EMC Support. But´s common to find customers that have a environment working with NAT. In this case, how do you handle that ?

I don't remember last time I worked with NAT and NW to be honest.

Well... worked.
The network (LAN) administrator created a route that allow-me to perform the backup and recover between different networks. I asked him what he changed and he told me that create one by one route from networker server ( the backup server ) to the client servers inside the router. So networker could start communication without problem.