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.com-fd
on 192.68.0.30:9102. ERR=Interrupted system call"

As for your answer I am unsure how to facilitate this.

Regards,

Wayne

Happy New Year...

---------- Forwarded message ----------
From: John Drescher <drescherjm AT gmail DOT com>
Date: Thu, Dec 30, 2010 at 9:26 AM
Subject: Re: [Bacula-users] Can't connect to Remote.
To: Wayne Spivak <WSpivak AT sbanetweb DOT com>


On Thu, Dec 30, 2010 at 9:13 AM, Wayne Spivak <WSpivak AT sbanetweb DOT com> 
wrote:
> Installed Bacula 5.0.2 on Fedora 14 (called Kira).
>
<snip>

Can the remote machine initiate transfers to the bacula-sd? Remember
it is the filedaemon that initiates the connection to the storage.

John



------------------------------------------------------------------------------
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and, 
should the need arise, upgrade to a full multi-node Oracle RAC database 
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users