I checked. No the IP for the client in the bacula-dir.conf doesn't end
in "."
Just for clarification, here's my client's bacula-fd.conf. Are you
referring to the password in the section "Director Name = bacula-dir"?
---------------------<snip>----------------------------------
FileDaemon { # this is me
Name = clientdesktop-fd
FDport = 9102 # where we listen for the director
WorkingDirectory = "C:\\Documents and Settings\\All Users\\Application
Data\\Bacula\\Work"
Pid Directory = "C:\\Documents and Settings\\All Users\\Application
Data\\Bacula\\Work"
Maximum Concurrent Jobs = 2
}
#
# List Directors who are permitted to contact this File daemon
#
Director {
Name = bacula-dir
Address = 192.168.1.150
# Password = "@client_password@"
Password = "2XqxDu0dhh2RQXFxmqyPGfpuN49vcPr9rU9GmMuBd6kh"
}
#
# Restricted Director, used by tray-monitor to get the
# status of the file daemon
#
Director {
Name = clientdesktop-mon
Password = "NI/gCJe3XXimdkJO9icDylUjlNxNg7RX8Zk2BLY67wBy"
Monitor = yes
}
# Send all messages except skipped files back to Director
Messages {
Name = Standard
director = shephan-dir = all, !skipped, !restored
}
-----------------------<end snip>--------------------------------
John Drescher wrote:
> On 8/30/07, Roy Vestal <[EMAIL PROTECTED]> wrote:
>
>> I have a new installation of bacula and i'm trying to implement it for
>> about 10 windows clients.
>>
>> I can connect to the bacula server from the client with wxconsole but
>> when I run a job it tells me my fd password is failing. I've been
>> through the autherrors and Windows sections of the docs but I can't find
>> it. I verified no firewalls on either side.
>>
>> I used this FAQ as my guide:
>> http://www.bacula.org/dev-manual/Bacula_Freque_Asked_Questi.html#SECTION003760000000000000000
>>
>> when I try to connect from bconsole on the server I get the following:
>>
>> *Console*.2007-08-30_13.14.07 Fatal error: Unable to authenticate with
>> File daemon on "192.168.1.23.:9102". Possible causes:
>> Passwords or names not the same or
>> Maximum Concurrent Jobs exceeded on the FD or
>> FD networking messed up (restart daemon)
>>
>> I've been over and over the thing and I can't find it.
>>
>>
>
> Does the password in the client resource in bacula-dir.conf on the
> server match the password in the bacula-fd.conf file on the windows
> machine?
>
> Also I am not sure if this is a problem but I do not get a . after the
> address when things fail as you have here:
>
> "192.168.1.23.:9102"
>
> Do you have the clients address ending with a . in the bacula-dir.conf?
>
> John
>
>
--
---------------------------------
Roy Vestal
.-.
/v\ L I N U X
// \\ >Phear the Penguin<
/( )\
^^-^^
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
