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. betw
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
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
abou
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 s
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 kn
>> 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 Plan
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 probl
>> 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
On 2/1/2010 2:11 PM, Heitor Medrado de Faria wrote:
Thx for your fast reply Heitor, now:
> First of all - check the windows Firewall. Than...
It's open (9101:9103), I can connect from Bacula Server to Windows
Server 2003 R2 (telnet 10.128.50.10 9102):
Trying 10.128.50.10...
Connected to 10.128
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\ba
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 {
11 matches
Mail list logo
