Hi, On 5/11/2007 7:41 PM, Peter Crighton wrote: > I've had Bacula 2.0.3 running for a week on my Centos 4.4 server > backing up files on the server successfully. > > Yesterday I decided to install Bacula on a Windows XP machine as a > client. I created a job on the server to backup a test folder on the > Windows machine and once I'd sorted the passwords and names out it > backed up the files.
Good. > So I added a job that should have run this morning, but that completed > with an error. Now wxconsole on the Windows client cannot connect to > the director on the Linux server and the director cannot talk to the > client. > > I've double checked the passwords and they are still correct so what's > the likely problem(s)? Ok, we'll assume that, although checking a third time won't hurt :-) > The Windows machine has been rebooted overnight. Ah! > The Bacula client icon in the taskbar states idle and the status > window lists the one successful job. Good... so we can assume the FD is actually running. Anyway, just to make sure, you can use the windows cmd prompt and use sc query bacula-fd and net stop bacula-fd net start bacula-fd to force a restart of the FD. > The wxconsole error is: > > Welcome to bacula wx-console 2.0.3 (06 March 2007)! > Using this configuration file: C:\Documents and Settings\All > Users\Application Data\Bacula\wx-console.conf > Connecting... > Connected > Director authorization problem. > Most likely the passwords do not agree. > If you are using TLS, there may have been a certificate validation > error during the TLS handshake. > Please see > http://www.bacula.org/rel-manual/faq.html#AuthorizationErrors for > help. > ERR=1999 Authorization failed. > > > After the failed connection there is a new message in bconsole: > > 11-May 18:30 Server-dir: ERROR in authenticate.c:382 Unable to > authenticate console "*UserAgent*" at client:192.168.1.10:36131 Good. This tells us that the network connection from the client to the DIR did work (I assume you ran wxconsole on the windows client giving you trouble). > > The result is the same for both the Windows administrator (under which > I installed the software) and a "limited" user. Ok. > Config files with passwords replaced by *** except for first two chars > [passwords were cut and pasted to set the windows conf file up to > ensure no errors]. I'll not discuss the files now as the basic connectivity seems to work, and you don't TLS as far as I can see. That leaves only a few possible problem areas: Network: - Is your windows firewall on the client set up to allow all Bacula-related traffic? - Any routers or firewalls in between the DIR and the client? - Did your IP addresses change in between? I notice that you use host names only in your configuration, which is probably not the best solution in a setting where you can't absolutely trust the name resolution. Configuration: - Have you checked that the configuration file wx-console uses? This one must be configured to match the DIR configuration to allow console connections. (This, I think, is the most likely reason for the problem - You didn't post that configuration file, but the error you reported refers to wx-console only.) When you run bconsole on the server, can you connect to the client using a command like 'sta client=office-fd'? Arno -- IT-Service Lehmann [EMAIL PROTECTED] Arno Lehmann http://www.its-lehmann.de ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
