This is the classic situation.  The configuration files are supplied below.

Please find my error.  I am starting to suspect the client binaries.

Server is Version: 7.0.5 on FreeBSD 9.3

Client is FreeBSD 10.1-RELEASE-p4 (actually, a pfSense installation) with 
bacula-client 7.0.5

from bacula-dir.conf:

Director {                            # define myself
  Name = bacula-dir
  DIRport = 9101                # where we listen for UA connections
...
}

Client {
  Name           = bast-fd
  Address        = bast.int.unixathome.org
  Catalog        = MyCatalog
  Password       = "password"

  File   Retention = 3 years
  Job    Retention = 3 years 
}

on bacula-dir server:

$ host bast.int.unixathome.org
bast.int.unixathome.org has address 10.55.0.1

on bast.int.unixathome.org:

$ ifconfig | grep 10.55.0.1
inet 10.55.0.1 netmask 0xffffff00 broadcast 10.55.0.255 


$ cat /usr/local/etc/bacula/bacula-fd.conf
Director {
  Name = bacula-dir
  Password = "password"
}

FileDaemon {                          # this is me
  Name = bast-fd
  FDport = 9102                  # where we listen for the director
  WorkingDirectory = /var/db/bacula
  Pid Directory = /var/run
  Maximum Concurrent Jobs = 20
}

# Send all messages except skipped files back to Director
Messages {
  Name = Standard
  director = bacula-dir = all, !skipped, !restored
}


From bconsole:

 $ bconsole 
Connecting to Director bacula.int.unixathome.org:9101
1000 OK: 1 bacula-dir Version: 7.0.5 (28 July 2014)
Enter a period to cancel a command.
*reload
*status client=bast-fd
Connecting to Client bast-fd at bast.int.unixathome.org:9102
Failed to connect to Client bast-fd.
====
You have messages.
*m
08-Feb 22:21 bacula-dir JobId 0: Fatal error: Unable to authenticate with File 
daemon at "bast.int.unixathome.org:9102". Possible causes:
Passwords or names not the same or
Maximum Concurrent Jobs exceeded on the FD or
FD networking messed up (restart daemon).
Please see 
http://www.bacula.org/en/rel-manual/Bacula_Freque_Asked_Questi.html#SECTION00260000000000000000
 for help.
*



From the client:

 /usr/pbi/bacula-amd64/bin/bacula-fd -u root -g wheel -v -c 
/usr/local/etc/bacula/bacula-fd.conf -f -d 100
bacula-fd: filed_conf.c:530-0 Inserting director res: pf22-packages-amd64-mon
bacula-fd: address_conf.c:264-0 Initaddr 0.0.0.0:9102 
pf22-packages-amd64-fd: jcr.c:128-0 read_last_jobs seek to 192
pf22-packages-amd64-fd: jcr.c:135-0 Read num_items=0
pf22-packages-amd64-fd: filed.c:250-0 filed: listening on port 9102
pf22-packages-amd64-fd: bnet_server.c:87-0 Addresses 0.0.0.0:9102 


### at this point, I issue the status client command in bconsole.  Then the 
following appears:

pf22-packages-amd64-fd: bnet.c:566-0 who=client host=Hostname not found 
port=9102
pf22-packages-amd64-fd: job.c:494-0 Got: Hello Director bacula-dir calling 1
pf22-packages-amd64-fd: job.c:280-0 <dird: Hello Director bacula-dir calling 1
pf22-packages-amd64-fd: job.c:303-0 Executing Dir Hello Director bacula-dir 
calling 1
 command.
pf22-packages-amd64-fd: job.c:306-0 Quit command loop. Canceled=0
pf22-packages-amd64-fd: job.c:417-0 Calling term_find_files
pf22-packages-amd64-fd: job.c:420-0 Done with term_find_files
pf22-packages-amd64-fd: job.c:423-0 Done with free_jcr





— 
Dan Langille
http://langille.org/






------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users