On Wed, 27 Jan 2010, Dirk H. Schulz wrote:
> 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.
In this instance, I would be inclined to start a tcpdump like that below on
both the -fd and -sd, start your backup and see where exactly the -fd tries
to connect to.
tcpdump -ni ethX tcp port 9103
The first question I suppose is to see what IP address the -fd is actually
using to connect. The second is does the tcp handshake happen correctly
and if so what happens then. Perhaps the -fd is connecting to the wrong
IP, or it could be a firewall issue, or something else...?
Gavin
------------------------------------------------------------------------------
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
