I have been running into the authentication error at times when I am
POSITIVE everything is set up correctly. The box I am having trouble
with now is a win2003 server. It had a working client on it, and
communicated happily with a bacula director. I set up a new bacula
server on Ubuntu, and it
Can you post your fd config file from your win2003 server. You can blank out the passwords if you want.John
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated
Can you post your fd config file from your win2003 server. You can blank
out
the passwords if you want.
#
# Default Bacula File Daemon Configuration file
#
# For Bacula release 1.38.10 (08 June 2006) -- cygwin 1.5.18(0.132/4/2)
#
# There is not much to change here except perhaps the
# File
This looks familiar, maybe a similar posting from a few weeks back.
I had a similar problem and it was caused by the client name in the fd
conf and the director files not matching perfectly. I had fqdn on the
client, but only the server name on the director.
I use host files on bacula
I figured it out. The name of the director was wrong, but the way the
error message was worded made me think it was all related to the file
daemon.
Sorry for the wasted post.
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
