Try to uninstall the client and re-install it, make sure to type the
director name exactly as its wrote in the bacula-dir.conf file on the server
(case sensitive). I use to have this problem and that was the solution for
me
Eitan
On Thu, Sep 3, 2009 at 7:30 PM, Syn, Joonho wrote:
> Yup! I ca
Ok so I figured it out at long last. I’m on a Vista client and config file I
thought Bacula was using was C:\Program Files\Bacula\bin\bacula-fd.conf. The
bacula service was actually starting with the command
“C:\Program Files\Bacula\bin\bacula-fd.exe /service –c
“C:\ProgramData\Bacula\bacula-
Yup! I can connect to 9102 on the client with no trouble at all.
On 9/2/09 11:00 PM, "Eitan Talmi" wrote:
Did you open port 9102 on the windows FW?
On Thu, Sep 3, 2009 at 3:09 AM, Syn, Joonho wrote:
The case matches up fine. The bwx-console has no problems connecting to the
director
Did you open port 9102 on the windows FW?
On Thu, Sep 3, 2009 at 3:09 AM, Syn, Joonho wrote:
> The case matches up fine. The bwx-console has no problems connecting to
> the director
>
>
>
> On 9/2/09 1:00 PM, "Eitan Talmi" wrote:
>
> I also had this problem, in may case the problem was th
The case matches up fine. The bwx-console has no problems connecting to the
director
On 9/2/09 1:00 PM, "Eitan Talmi" wrote:
I also had this problem, in may case the problem was that the director name is
case sensitive.
make sure that both on the server on the client they are exactly th
I also had this problem, in may case the problem was that the director name
is case sensitive.
make sure that both on the server on the client they are exactly the same
On Wed, Sep 2, 2009 at 9:34 PM, Syn, Joonho wrote:
> The FD on the windows client is 3.0.2 so I don't think it's version
> in
The FD on the windows client is 3.0.2 so I don't think it's version
incompatibility unless there 3.0.1 and 3.0.2 do not play nicely. I tried
disabling the wireless card but it doesn't seem to help either. I did run
the file director with debugging turned on and it appears that the password
hash it
At the server try to ping to your bacula server, make sure that it's
responding with the real IP and not 127.0.0.1.
Try to telnet from the server to the client at port 9102
Eitan
2009/9/1 Syn, Joonho
> Hi,
> I’m trying to add my first windows client to my test instance of bacula
> running o
Syn, Joonho wrote:
>
> Hi,
> I’m trying to add my first windows client to my test instance of
> bacula running on RHEL5 but I keep getting Authentication Failed
> errors. It claims that I have an incorrect password but I know this is
> not true. Since the client is a laptop I thought perhaps tha
Hi,
I'm trying to add my first windows client to my test instance of bacula running
on RHEL5 but I keep getting Authentication Failed errors. It claims that I
have an incorrect password but I know this is not true. Since the client is a
laptop I thought perhaps that bacula might be confused si
10 matches
Mail list logo
