On Apr 3, 2001, David Lloyd <[EMAIL PROTECTED]> wrote:
>> 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.
Amanda just runs smbclient. If Amanda says the backup failed, it's
because smbclient said so. Perhaps you're running one version of
smbclient by hand, but Amanda is running another, misconfigured
version? Perhaps you're passing some command-line flag to smbclient
that Amanda doesn't pass? Whatever the case is, it's smbclient that
is failing to contact the Windows machine. Amanda plays absolutely no
role here other than telling smbclient to create a tar-file off the
Windows box.
> So how is it smbclient's fault when smbclient works? I can't understand
> your English...
Perhaps I don't speak or write English well enough to get the message
through. It can't possibly be Amanda's fault. Get the exact command
line that Amanda runs (they're logged in /tmp/amanda/*.debug) and try
them. If they fail to work, you'll have more material to investigate
the problem. If they work, then you probably have a timing problem
(such as having the backup account forbidden from logging in at the
time of the backup or something).
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me
