Did you open port 9102 on the windows FW?
On Thu, Sep 3, 2009 at 3:09 AM, Syn, Joonho <joo...@a9.com> 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" <eit...@gmail.com> 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 the same
>
>
> On Wed, Sep 2, 2009 at 9:34 PM, Syn, Joonho <joo...@a9.com> wrote:
>
> 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 was expecting was not matching with what it received..Which is odd
> because the passwords match! I tried saving the file as different file
> types of text document (unicode, ms-dos text, text) none of which helped
> either...
>
>
> On 8/31/09 5:08 PM, "Cedric Tefft" <logicl...@gmail.com> wrote:
>
> > 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 that bacula
> >> might be confused since it has a wireless and wired interface but this
> >> is not the case since I hard-coded the IP into the bacula-dir.conf.
> >> I’ll paste the bacula-dir.conf and the bacula-fd.conf from the client.
> >>
> >>
> > Version incompatibility?? I see your director is v3.0.1. What version of
> > the FD are you running on the Windows box? If it is not at least 3.0 you
> > might need to upgrade.
> >
> > A couple more things to try: run the FD on the Windows box with
> > debugging turned on (try adding "-d 200" to the command-line). The
> > debugging output may be more helpful.
> > Also, just for grins, I would try temporarily disabling the Windows
> > box's other network card -- whichever one bacula is not connecting to.
> > This shouldn't make any difference, but if nothing changes it will
> > eliminate a number of possibilities.
> >
> > - Cedric
> >
>
>
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus
> on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now. http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
>
>
>
>
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
