|
Below is what I have on the client in the : "C:\Program Files\Bacula"
# "Global" File daemon configuration specifications
#
FileDaemon { # this is me
Name = w14219-pc-fd
FDport = 9102 # where we listen for the director
WorkingDirectory = "C:\\Program Files\\Bacula\\working"
Pid Directory = "C:\\Program Files\\Bacula\\working"
# Plugin Directory = "C:\\Program Files\\Bacula\\plugins"
Maximum Concurrent Jobs = 10
}
#
# List Directors who are permitted to contact this File daemon
#
Director {
Name = bacula-01-dir
Password = "77cb2cf4"
}
#
# Restricted Director, used by tray-monitor to get the
# status of the file daemon
#
Director {
Name = bacula-01-mon
Password = "77cb2cf4"
Monitor = yes
}
# Send all messages except skipped files back to Director
Messages {
Name = Standard
director = bacula-dir = all, !skipped, !restored
}
I attached the 3 .conf files from the bacula server to see if anyone can point out where I am dorked.
Also, I can telnet from the bacula-01 server to:
telnet w14219-pc 9102
telnet 10.2.1.147 9102 <--- w14219-pc
telnet bacula-01 9102
telnet 10.2.1.96 9102 <--- bacula-01
I cannot telnet from the bacula server to:
telnet 127.0.0.1 9102
I cannot telnet from the windows machine to any 9102 port, is that the problem?
Thanks
On Wed, Mar 16, 2011 at 1:27 PM, Mike Hendrie <mike AT hendrienet DOT com> wrote:
I did replace all of the localhosts and 127.0.0.1 locations with the DNS'd server name.
Mike
On Wed, Mar 16, 2011 at 12:53 PM, John Drescher <drescherjm AT gmail DOT com> wrote:
2011/3/16 Mike Hendrie <mike AT hendrienet DOT com>:
> I will check that.
>
> I was using the commented out default client in the bacula-dir.conf, but
> updated the content with the new windows computer name. Then on the windows
> computer, I updated the director username and password, and the monitor
> username and password.
>
> I will take a closer look at the file.
>
When you setup your storage did you replace 127.0.0.1 or localhost
with the external ip address. Some overly protective distributions
deliver default configurations that make bacula only work on the
bacula server itself since the any machine outside the bacula server
can not make connections to the server via 127.0.0.1..
John
bacula-dir.conf
Description: Binary data
bacula-fd.conf
Description: Binary data
bacula-sd.conf
Description: Binary data
------------------------------------------------------------------------------
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d _______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
| 