I am running a bacula director (and storage daemon) on a machine in a private IP net. One of the clients is located in a public IP net (let's call it external-fd). The connection from server-dir/server-sd to external fd is NATed.
Like described on the bacula.org website in "dealing with firewalls" I use an FQDN for the server-dir/server-sd that resolves internally to the private IP address and externally to the external IP-Adress of the NAT router (that forwards the packets to the server-dir/server-sd). AND I HAVE TESTED IT: with telnet. Telnetting from external-fd to server-sd using the above mentionened FQDN and the port of the storage daemon (telnet storage.server.sd 9103) outputs exactly the same as telnetting internally to that port. Afaik, that means: bacula-fd on the external client should be able to connect to bacula-sd on the internal server. But it does not. Running a backup job for this client the director is quite a long time "waiting for Client ... to connect to Storage ..." and eventually gives up. Using netstat I can verify there is no connection from the client to 9103 on the server (or to the exernal IP of the private subnet at all). There must be something important I overlook, but I did not find anything helpful on the web anywhere. Any hint or help is appreciated. Dirk ------------------------------------------------------------------------------ The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
