On 10/30/07, Sean Carolan <[EMAIL PROTECTED]> wrote:
> I've combed the documentation, mailing list, and Google but have not
> found an answer to this problem. No matter what I do, I cannot get
> the BackupPC server to connect to Windows clients.
Here's what I did to fix this, in case anyone else
I've combed the documentation, mailing list, and Google but have not
found an answer to this problem. No matter what I do, I cannot get
the BackupPC server to connect to Windows clients. Here is my setup:
BackupPC server runs CentOS 5
Samba client installed from source, version 3.0.26
Server tes
On Friday 28 September 2007 14:16, Regis Gras wrote:
> Craig Barratt wrote:
> >Regis writes:
> >>I'am using BackupPC-2.1.0
> >>
> >>With the same config.pl,
> >>Start Full Backup works fine
> >>Start Inc Backup fails every time with the message
> >> NT_STATUS_LOGON_FAILURE
> >
> >I believe there wa
Craig Barratt wrote:
>Regis writes:
>
>
>
>>I'am using BackupPC-2.1.0
>>
>>With the same config.pl,
>>Start Full Backup works fine
>>Start Inc Backup fails every time with the message NT_STATUS_LOGON_FAILURE
>>
>>
>
>I believe there was a version (or set of samba versions) that had
>this bug
ights are normally good.
Thank you in advance for your help.
Regards,
Romain
Tony Molloy <[EMAIL PROTECTED]>
Envoyé par : [EMAIL PROTECTED]
28/09/2007 14:18
A
backuppc-users@lists.sourceforge.net
cc
Objet
Re: [BackupPC-users] NT_STATUS_LOGON_FAILURE
On Friday 28 Septembe
On Friday 28 September 2007 12:23, Regis Gras wrote:
> Craig Barratt wrote:
> >Regis writes:
> >>I'am using BackupPC-2.1.0
> >>
> >>With the same config.pl,
> >>Start Full Backup works fine
> >>Start Inc Backup fails every time with the message
> >> NT_STATUS_LOGON_FAILURE
> >
> >I believe there wa
Craig Barratt wrote:
>Regis writes:
>
>
>
>>I'am using BackupPC-2.1.0
>>
>>With the same config.pl,
>>Start Full Backup works fine
>>Start Inc Backup fails every time with the message NT_STATUS_LOGON_FAILURE
>>
>>
>
>I believe there was a version (or set of samba versions) that had
>this bug
Regis writes:
> I'am using BackupPC-2.1.0
>
> With the same config.pl,
> Start Full Backup works fine
> Start Inc Backup fails every time with the message NT_STATUS_LOGON_FAILURE
I believe there was a version (or set of samba versions) that had
this bug. I think it was 3.0.23 or so.
There was
I'am using BackupPC-2.1.0
With the same config.pl,
Start Full Backup works fine
Start Inc Backup fails every time with the message NT_STATUS_LOGON_FAILURE
Could some one help me ?
--
==
| Régis Gras | http://dcm.ujf
Ryan Ross ece.ucsb.edu> writes:
>
> Over the weekend smbclient updated to 3.0.23 on my Fedora Core 4 system.
> Since
> that time, I have not been able to backup our Windows server. I have not
> changed the config.pl at all, and it has been working fine for months. Ever
> since that samba upd
Since the build for the original RPM already includes --with-smbmount
and --with-acl-support, perhaps the problem lies in the
--with-smbwrapper part?
Here's a way to build your own RPMs with the change and test it. (I have
not tested the RPMs yet, but they do build just fine.) Note that I did
Hello Bill,
At 10:56 AM -0400 7/23/06, Bill Hudacek wrote:
>I've created bug #3954 at https://bugzilla.samba.org/show_bug.cgi?id=3954
>
>Now we'll see if it resonates with anyone else. I can only imagine that
>millions of BackupPC users are noticing this today, or they will
>tomorrow :-)
I have
I've created bug #3954 at https://bugzilla.samba.org/show_bug.cgi?id=3954
Now we'll see if it resonates with anyone else. I can only imagine that
millions of BackupPC users are noticing this today, or they will
tomorrow :-)
If the Samba developers can't/won't address the problem, I'll set up
Les Mikesell wrote:
> On Tue, 2006-07-18 at 21:57, Bill Hudacek wrote:
>
> Is there some subtle difference in your $Conf{SmbClientFullCmd} and
> $Conf{SmbClientIncrCmd} entries? Can you execute something
> resembling the expanded incremental command manually with
> smbclient?
>
Thanks, Les, fo
Craig Barratt wrote:
> Smbclient uses a file timestamp for setting the incremental date.
> That file is /usr/local/backuppc/data/pc/dc1/timeStamp.level0
> which gets removed after the backup. So you should replace
> that with some other file that can be empty:
>
> touch timeStamp.level0
>
>
Ryan Ross writes:
> When I run
> [backuppc etc]$ /usr/bin/smbclient dc1\\G -U ece -E -N -d 1 -c tarmode\
> full -TcN /usr/local/backuppc/data/pc/dc1/timeStamp.level0 -
>
> I get one line back:
> Error setting newer-than time
>
> I don't think I'm using smbclient correctly, but I am just cop
When I run
[backuppc etc]$ /usr/bin/smbclient dc1\\G -U ece -E -N -d 1 -c tarmode\
full -TcN /usr/local/backuppc/data/pc/dc1/timeStamp.level0 -
I get one line back:
Error setting newer-than time
I don't think I'm using smbclient correctly, but I am just copy and pasting
from the XferLOG.
W
On Tue, 2006-07-18 at 21:57, Bill Hudacek wrote:
> Minor update. Reading code shows that BackupPC does indeed set the
> environment variable PASSWD.
>
> So, if the samba docs have not changed, does that mean the actual
> running code has not changed? I'm not convinced, but I have no data at
>
Minor update. Reading code shows that BackupPC does indeed set the
environment variable PASSWD.
So, if the samba docs have not changed, does that mean the actual
running code has not changed? I'm not convinced, but I have no data at
this point. Looking over the 3.0.23 release notes, there ar
[sorry, victor, reply-but-not-to-list gets me too often...]
Víctor A. Rodríguez wrote:
>
> Nope :-P it's because backuppc tells to smbclient "do not ask for
passwords"
> (-N) then it tries to login as user "ece" with the password supplied
in the
> PASSWD variable.
>
> So, try to do :
>
> When I run just
> [backuppc etc]$ /usr/bin/smbclient \dc1G -U ece -E -N -d 1 -c tarmode
> full
>
> I get this back: (I replaced some values with CORRECT)
> Anonymous login successful
> Domain=[CORRECT] OS=[CORRECT] Server=[CORRECT]
> tree connect failed: NT_STATUS_ACCESS_DENIED
>
> Not sure why i
On Tue, 2006-07-18 at 08:14 -0700, Ryan Ross wrote:
> Over the weekend smbclient updated to 3.0.23 on my Fedora Core 4 system.
> Since
> that time, I have not been able to backup our Windows server. I have not
> changed the config.pl at all, and it has been working fine for months. Ever
> since
Over the weekend smbclient updated to 3.0.23 on my Fedora Core 4 system. Since
that time, I have not been able to backup our Windows server. I have not
changed the config.pl at all, and it has been working fine for months. Ever
since that samba update however, I get this message:
Running: /usr/
23 matches
Mail list logo
