> When you say you checked/updated the Windows machine client config,
> exactly what file(s) did you look at? Reason I ask is I just completed
> an upgrade from v1.36 to v2.0.3 on about 80 clients (5 of them being
> Windows) and noticed that the config is now in a different place on my
> Windows boxes. It used to be in C:\bacula, now its in C:\Documents and
> Settings\All Users\Application Data\Bacula. I just tried setting my
> director to no password, and used a "" blank password in C:\Documents
> and Settings\All Users\Application Data\Bacula\bacula-fd.conf and
> everything seems to be working fine here.


It sounds like I'm doing the exact same thing as you described but it's still
not authenticating. I set the blank password, verified that the daemon/service
is listening by telneting to port 9102 on the client:

# telnet 192.168.69.18 9102
Trying 192.168.69.18...
Connected to mine.bangtherockstogether.net (192.168.69.18).
Escape character is '^]'.

but trying to connect the bconsole results in:

23-Mar 11:25 amanda-dir: *Console*.2007-03-23_11.25.33 Fatal error: Unable to
authenticate with File daemon on "192.168.69.18: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/rel-manual/faq.html#AuthorizationErrors for
help.


I dont have access to the windows machine frmo work right now but I can chare
the config for the client as it exists on my master fd. Here are the viable
excerpts (let me know if I'm missing something). PS I'm including real names
and IP's as this is all internal an non-Internet routed anyway:

>From bacula-dir.conf

Job {
  Name = "Mine"
  Client = mine-fd
  FileSet = "Mine Set"
  JobDefs = "BRT_Inc"
  Write Bootstrap = "/var/bacula/working/Mine.bsr"
}

Client {
  Name = mine-fd
  Address = 192.168.69.18
  FDPort = 9102
  Catalog = MyCatalog
  Password = ""
  File Retention = 30 days
  Job Retention = 6 months
  AutoPrune = yes
}

FileSet {
  Name = "Mine Set"
  Include {
    Options {
      IgnoreCase = yes
      signature = MD5
    }
    File = "C:/Test/"
  }
}


Now on the Windows client basically I edited all of the config to reflect the
exact same changes I have on my Linux machines changing only the local fd name
to mine-fd and then I manually edited the config because it had Password="%my
password%" or something to that effect which I changed to Password=""

I stopped and restarted the service on the windows client after changing the
config (which was a scratch install of 2.0.3 an in the pathes listed by
Michael in this email IE: C:\Documents and Settings\All Users\Application
Data\Bacula\bacula-fd.conf)


Now one thing I DID noticed was strange ... using Windows explorer I couldn't
browse to that folder however when I clicked "Save As" after making changes it
does actually save to that location. Not sure if this means anything.

Anyway, I'm planning on trying to add more debugging to the director on the
windows client this weekend to see what it shows or where it shows it. Right
now this still boggles me :-)  Keep in mind I haven't actually run Windows on
any of my machines since about 96, this is my Fiance's computer I'm trying to
back some stuff up for her.

Either way thanks again for all the suggestions and help. I'm still trying
things but this isn't a complicated installation or config so I'm probably
over-working the problem.

--
Lonny


-- 
"To mess up a Linux box, you need to work at it; to mess up your Windows box,
you just need to work ON it."


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to