Re: [Bacula-users] Client problem on Windows Server 2003 R2
First of all - check the windows Firewall. Than...
}
FileDaemon { # this is me
Name = 10.128.50.10-fd
You should no write a ip as your client name.
FDport = 9102 # where we listen for the director
WorkingDirectory = C:\Temp\bacula
Pid Directory = C:\WINDOWS
}
And this is the client definition at bacula-dir.conf
Client {
Name = FD.10.128.60.10
Your client name is not equal to the name on bacula-fd.conf. It must be
exactly the same name.
Regards,
Heitor Faria
www.bacula.com.br
--
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Client problem on Windows Server 2003 R2
You should not write a ip as your client name. Is that a problem? All my clients (Linux until now) have IP address as name and I haven't problems before. Also it's not a IP address because the name is 10.128.50.10-fd this is a string to me (I don't know for Bacula :( ) Its not a problem But I just think its not practical and maybe considered a security flaw. Your client name is not equal to the name on bacula-fd.conf. It must be exactly the same name. Again, I have this done with all my old clients the problem come up right now while I'm trying to configure this Windows Client. But the names are not equal... I think it cannot work that way. Note: Bacula Server is version 3.0.2 and Client Version is 3.0.3, is that a problem? It may be a problem... Not sure. -- The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Client problem on Windows Server 2003 R2
On 2/1/2010 2:23 PM, Heitor Medrado de Faria wrote: Its not a problem But I just think its not practical and maybe considered a security flaw. Maybe, OK, i'll take into account. But the names are not equal... I think it cannot work that way. I changes the name to be equal and the problem still. -- ReynierPM -- The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Client problem on Windows Server 2003 R2
But the names are not equal... I think it cannot work that way. I changes the name to be equal and the problem still. Restarted all daemons? Maybe you should equalize the director and client versions... -- The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Client problem on Windows Server 2003 R2
Heitor Medrado de Faria pisze: You should not write a ip as your client name. Is that a problem? All my clients (Linux until now) have IP address as name and I haven't problems before. Also it's not a IP address because the name is 10.128.50.10-fd this is a string to me (I don't know for Bacula :( ) Its not a problem But I just think its not practical and maybe considered a security flaw. Your client name is not equal to the name on bacula-fd.conf. It must be exactly the same name. Again, I have this done with all my old clients the problem come up right now while I'm trying to configure this Windows Client. But the names are not equal... I think it cannot work that way. The Name of FileDaemon in bacula-fd.conf and the name of Client in bacula-dir.conf do not have to be the same. http://bacula.org/5.0.x-manuals/en/main/main/Customizing_Configuration_F.html#SECTION00154 Regards. gani -- The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Client problem on Windows Server 2003 R2
ganiuszka wrote: Heitor Medrado de Faria pisze: You should not write a ip as your client name. Is that a problem? All my clients (Linux until now) have IP address as name and I haven't problems before. Also it's not a IP address because the name is 10.128.50.10-fd this is a string to me (I don't know for Bacula :( ) Its not a problem But I just think its not practical and maybe considered a security flaw. Your client name is not equal to the name on bacula-fd.conf. It must be exactly the same name. Again, I have this done with all my old clients the problem come up right now while I'm trying to configure this Windows Client. But the names are not equal... I think it cannot work that way. The Name of FileDaemon in bacula-fd.conf and the name of Client in bacula-dir.conf do not have to be the same. http://bacula.org/5.0.x-manuals/en/main/main/Customizing_Configuration_F.html#SECTION00154 Regards. gani Hã??? In most cases, the password corresponds to a particular name, so both the name and the password must match to be authorized. -- The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Client problem on Windows Server 2003 R2
On 2/1/2010 2:39 PM, ganiuszka wrote: The Name of FileDaemon in bacula-fd.conf and the name of Client in bacula-dir.conf do not have to be the same. Sure, I test with differents names and it works, just install 3.0.2 client. Maybe the problems was the version of client, I'm not so sure about it Anyway thx a lot for yours time -- Cheers ReynierPM -- The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Client problem on Windows Server 2003 R2
Heitor Medrado de Faria pisze: ganiuszka wrote: Heitor Medrado de Faria pisze: You should not write a ip as your client name. Is that a problem? All my clients (Linux until now) have IP address as name and I haven't problems before. Also it's not a IP address because the name is 10.128.50.10-fd this is a string to me (I don't know for Bacula :( ) Its not a problem But I just think its not practical and maybe considered a security flaw. Your client name is not equal to the name on bacula-fd.conf. It must be exactly the same name. Again, I have this done with all my old clients the problem come up right now while I'm trying to configure this Windows Client. But the names are not equal... I think it cannot work that way. The Name of FileDaemon in bacula-fd.conf and the name of Client in bacula-dir.conf do not have to be the same. http://bacula.org/5.0.x-manuals/en/main/main/Customizing_Configuration_F.html#SECTION00154 Regards. gani Hã??? In most cases, the password corresponds to a particular name, so both the name and the password must match to be authorized. In most cases... Look at the diagram. Did you try this configuration? Regards gani -- The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Client problem on Windows Server 2003 R2
Hi Reynier, some weeks ago, there's a discussion on the list about strange
error between -dir -fd -sd on windows.
Did you win2k3 have ip6 too (or be a 64bits)
The bug if I remembering is about connection initiate on ipv4 and return is
waiting on ipv6 something salad like this.
Try a search. between december and now.
On 02/01/2010 08:03 PM, ReynierPM wrote:
Hi every:
I'm trying to add a new Windows Client (the first) to my Bacula but I'm
get problems while trying to communicate from Bacula Server to Client.
This is my client configuration:
Director {
Name = serverbacula-dir
Password = oGsNf04dulgd4ga9
}
FileDaemon { # this is me
Name = 10.128.50.10-fd
FDport = 9102 # where we listen for the director
WorkingDirectory = C:\Temp\bacula
Pid Directory = C:\WINDOWS
}
And this is the client definition at bacula-dir.conf
Client {
Name = FD.10.128.60.10
Address = 10.128.50.10
FDPort = 9102
Catalog = MyCatalog
Password = oGsNf04dulgd4ga9
File Retention = 15 days
Job Retention = 15 days
}
This is the error message:
01-Feb 14:00 serverbacula-dir JobId 0: Fatal error: Unable to
authenticate with File daemon at 10.128.50.10: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/en/rel-manual/Bacula_Freque_Asked_Questi.html#SECTION00376
for help.
What's wrong here?
--
Bruno Friedmann
--
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
