Follow-up:
I loaded Bacula client (5.0.2) on a Fedora 14 box which is behind the
firewall (EMMA) and is 1 IP address different from KIRA. I took down
iptables (since it is redundant and to minimize errors.
Same basic error:
"Fatal error: bsock.c:135 Unable to connect to Client: emma.sbanetweb.co
-- Forwarded message --
From: John Drescher
Date: Thu, Dec 30, 2010 at 9:26 AM
Subject: Re: [Bacula-users] Can't connect to Remote.
To: Wayne Spivak
On Thu, Dec 30, 2010 at 9:13 AM, Wayne Spivak wrote:
> Installed Bacula 5.0.2 on Fedora 14 (called Kira).
>
> Previously had it i