Re: [Bacula-users] Client problem on Windows Server 2003 R2

2010-02-01 Thread Heitor Medrado de Faria
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

Re: [Bacula-users] Client problem on Windows Server 2003 R2

2010-02-01 Thread Heitor Medrado de Faria
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

Re: [Bacula-users] Client problem on Windows Server 2003 R2

2010-02-01 Thread ReynierPM
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

Re: [Bacula-users] Client problem on Windows Server 2003 R2

2010-02-01 Thread Heitor Medrado de Faria
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:

Re: [Bacula-users] Client problem on Windows Server 2003 R2

2010-02-01 Thread ganiuszka
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

Re: [Bacula-users] Client problem on Windows Server 2003 R2

2010-02-01 Thread Heitor Medrado de Faria
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

Re: [Bacula-users] Client problem on Windows Server 2003 R2

2010-02-01 Thread ReynierPM
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

Re: [Bacula-users] Client problem on Windows Server 2003 R2

2010-02-01 Thread ganiuszka
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

Re: [Bacula-users] Client problem on Windows Server 2003 R2

2010-02-01 Thread Bruno Friedmann
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.