Author: Laurent MANCHON <lmanchon AT univ-montp2 DOT fr>
Date: Wed, 06 Jun 2012 16:16:32 +0200
--hi, bacula returns this error message: 06-juin 14:56 Bacula-dir JobId 1569 : Warning: bsock.c:129 impossible to connect at Storage daemon on 192.168.1.15:9103. ERR=Connection failed i think i have
Author: Konstantin Khomoutov <flatworm AT users.sourceforge DOT net>
Date: Wed, 6 Jun 2012 18:51:27 +0400
[...] Before blaming your firewall settings and make us decypher them, you really ought to check these two things: 1) SD on 192.168.1.15 is really listening on 192.168.1.15:9103 or on 0.0.0.0:9103 (t
Author: hymie! <hymie AT lactose.homelinux DOT net>
Date: Wed, 06 Jun 2012 10:38:03 -0400
I'm not an iptables expert, but your rules seem **very** complex for a machine whose IP address begins with 192.168 . You didn't specify if these are the iptables rules on your bacula server, or on t
Author: Konstantin Khomoutov <flatworm AT users.sourceforge DOT net>
Date: Wed, 6 Jun 2012 19:21:45 +0400
[...] Correction: I copied and pasted an example of failed connection. If SD is listening on the target socket, you should be connected and get nothing back. -- Live Security Virtual Conference Exclu
Author: hymie! <hymie AT lactose.homelinux DOT net>
Date: Wed, 06 Jun 2012 15:56:20 -0400
"From outside" ? Umm, you do understand who 192.168.X.X addresses work, right? So you can telnet from the Bacula director to the Bacula storage daemon on port 9103. At that point, I need to defer to