title: Bacula - Director unable to authenticate with Storage daemon
body: <p>I'm trying to stay sane while configuring Bacula Server on my virtual CentOS Linux release 7.3.1611 to do a basic local backup job. </p>
  
  <p>I prepared all the configurations I found necessary in the conf-files and prepared the mysql database accordingly. </p>
  
  <p>When I want to start a job (local backup for now) I enter the following commands in bconsole:</p>
  
  <pre><code>*Connecting to Director 127.0.0.1:9101
  1000 OK: bacula-dir Version: 5.2.13 (19 February 2013)
  Enter a period to cancel a command.
  *label
  Automatically selected Catalog: MyCatalog
  Using Catalog "MyCatalog"
  Automatically selected Storage: File
  Enter new Volume name: MyVolume
  Defined Pools:
       1: Default
       2: File
       3: Scratch
  Select the Pool (1-3): 2
  </code></pre>
  
  <p>This returns </p>
  
  <pre><code>Connecting to Storage daemon File at 127.0.0.1:9101 ...
  Failed to connect to Storage daemon.
  Do not forget to mount the drive!!!
  You have messages.
  </code></pre>
  
  <p>where the message is: </p>
  
  <pre><code>12-Sep 12:05 bacula-dir JobId 0: Fatal error: authenticate.c:120 Director unable to authenticate with Storage daemon at "127.0.0.1:9101". Possible causes:
  Passwords or names not the same or
  Maximum Concurrent Jobs exceeded on the SD or
  SD networking messed up (restart daemon).
  Please see http://www.bacula.org/en/rel-manual/Bacula_Freque_Asked_Questi.html#SECTION00260000000000000000 for help.
  </code></pre>
  
  <p>I double and triple checked all the conf files for integrity and names and passwords. I don't know where to further look for the error. </p>
  
  <p>I will gladly post any parts of the conf files but don't want to blow up this question right away if it might not be necessary. Thank you for any hints.  </p>