Ok, I think finally understand what Marty is trying to say. Marty, there
are many people on this list who have been using samba for years and
understand it very well and how it interacts with amanda, and if we
couldn't understand the gist of your initial question, don't blame our
lack of understanding of the english language. :-)
Marty says his samba setup works, but because of the fallback from wins to
broadcast the lookup takes longer than amanda is willing to wait. Amanda
times out and as far as amanda is concerned, smbclient failed. I'm not
even sure what the implications of this are or how to make it work more
efficiently, I'm just interpreting what he stated.
Marty, is this correct?
Now, this said, I still think the problem is with samba. You should 'fix'
your samba setup so that it doesn't take so long to do a lookup.
Todd
On Wed, 4 Apr 2001, David Lloyd wrote:
> Marty!
>
> I suggest you put your asbestos, flame resistant suit on...
>
> > Again: THIS IS NOT AMANDA'S FAULT! IT IS SMBCLIENT'S FAULT!
>
> You obviously cannot understand what I am saying, or you have not
> followed this thread. If you cannot understand English I will have this
> translated into any other language that I have a character set for:
>
> SMBCLIENT CAN CONTACT MY WINDOWS 2000 SERVER. IT DOES NOT FAIL. IT WORKS
> VIA BROADCAST AND AMANDA FAILS TO SEE THAT IT WORKS.
>
> Or to reword this:
>
> SAMBA IS ABLE TO CONTACT MY WINDOWS 2000 SERVER; SMBCLIENT CAN CONTACT
> IT. HOWEVER, IT DOES THIS VIA BROADCAST AND AMANDA FAILS.
>
> As far as I'm concerned SMB is working correctly. It is setup to use
> wins, wins fails and it therefore contacts my Windows 2000 server by
> broadcast and connects. Perfectly.
>
> So how is it smbclient's fault when smbclient works? I can't understand
> your English...
>
> DSL
>
--
Todd Pfaff \ Email: [EMAIL PROTECTED]
Computing and Information Services \ Voice: (905) 525-9140 x22920
ABB 132 \ FAX: (905) 528-3773
McMaster University \
Hamilton, Ontario, Canada L8S 4M1 \
