Hello, I am stuck. I succeeded to make a backup from a WinXP Pro as it was inside the LAN. Then I moved it outside and adapted the IP addresses in all configs.
Now I can still connect from this client with wxconsole to the director on the server. But nothing can connect to bacula-fd. First I though of an firewall problem. But I think I check everything there. The situation is strange. I can telnet on the client to 127.0.0.1 at 9102. But telnet ClientIP 9102 gets no connection. The port scan of 127.0.0.1 shows port 9102 open. The port scan of 9102 of ClientIP shows no response. Kerio Firewall running on the client shows that bacula-fd is listening on all networkadapters on port 9102. I don't understand this explanation of the manual about the client resource of the fd.conf: FDAddresses = <IP-address-specification> Specify the ports and addresses on which the Director daemon will listen for Bacula Console connections. ... For me it look as if there would be something coded into windows bacula-fd that lets it only answer to certain IP ranges (eg ranges used for LANs). Is this true? What else can be a reason for this behaviour? BTW: The client is 1.37.38. Regards, Mick ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
