subject:"\[BackupPC\-users\] problem with samba"

Re: [BackupPC-users] problem with samba

2017-11-24 Thread Craig Barratt via BackupPC-users

>
> [root@barak ~]# smbclient //hayun-34/gis -U micha -E -d 3 -c tarmode full


I believe you need to pass a single argument to -c, so either quote it, or
add a backslash:

[root@barak ~]# smbclient //hayun-34/gis -U micha -E -d 3 -c 'tarmode full'

What is $Conf{SmbClientFullCmd} set to on this client, and on a client that
works?  It should be something like:

$Conf{SmbClientFullCmd} = '$smbClientPath $host\\$shareName $I_option
-U $userName -E -d 1 -c tarmode\\ full -Tc$X_option - $fileList';


Craig

On Wed, Nov 22, 2017 at 8:47 AM, Micha Silver  wrote:

> Thanks for your responses, but...
>
> On 11/21/2017 05:53 PM, Les Mikesell wrote:
>
> On Tue, Nov 21, 2017 at 8:54 AM, Евгений  
>  wrote:
>
> Kinit for micha@ARAVA to access hayun-34 failed: Cannot find KDC for
> requested realm
>
> This is about Kerberos.
> Have you configured kerberos properly? Is it working when you request ticket
> (kinit command)?
> I am not sure smbclient should use kerberos authentification by tickets by
> default... can not check it for now.
>
> The windows host that I am backing up is part of a windows domain. Nothing
> has changed on that side.
>
> I believe smbclient will read the values from your /etc/samba/smb.conf
> file at startup unless you have pointed it elsewhere with the -s
> option.   If you are also running a samba server you may have
> configured options that are incompatible with the backuppc client use.
>But that still doesn't explain a difference between full and
> incremental runs.
>
> That's what has me confused. And this problem started right after an
> update to samba on the BackupPC server.
> In addition, BackupPC is successfully doing both fulls and incrementals
> from other (windows) servers.
> ??
>
>
> --
> Micha Silver
> Ben Gurion Univ.
> Sde Boker, Remote Sensing Lab
> cell: +972-523-665918
>
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> BackupPC-users mailing list
> BackupPC-users@lists.sourceforge.net
> List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
> Wiki:http://backuppc.wiki.sourceforge.net
> Project: http://backuppc.sourceforge.net/
>
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

Re: [BackupPC-users] problem with samba

2017-11-22 Thread Micha Silver


  
  
Thanks for your responses, but...

On 11/21/2017 05:53 PM, Les Mikesell
  wrote:


  On Tue, Nov 21, 2017 at 8:54 AM, Евгений  wrote:

  

  Kinit for micha@ARAVA to access hayun-34 failed: Cannot find KDC for
requested realm



This is about Kerberos.
Have you configured kerberos properly? Is it working when you request ticket
(kinit command)?
I am not sure smbclient should use kerberos authentification by tickets by
default... can not check it for now.

  

The windows host that I am backing up is part of a windows domain.
Nothing has changed on that side.


  
I believe smbclient will read the values from your /etc/samba/smb.conf
file at startup unless you have pointed it elsewhere with the -s
option.   If you are also running a samba server you may have
configured options that are incompatible with the backuppc client use.
   But that still doesn't explain a difference between full and
incremental runs.

That's what has me confused. And this problem started right after an
update to samba on the BackupPC server.
In addition, BackupPC is successfully doing both fulls and
incrementals from other (windows) servers.
??


  




-- 
Micha Silver
Ben Gurion Univ.
Sde Boker, Remote Sensing Lab
cell: +972-523-665918
  


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

Re: [BackupPC-users] problem with samba

2017-11-21 Thread Les Mikesell

On Tue, Nov 21, 2017 at 8:54 AM, Евгений  wrote:
>> Kinit for micha@ARAVA to access hayun-34 failed: Cannot find KDC for
>> requested realm
>
> This is about Kerberos.
> Have you configured kerberos properly? Is it working when you request ticket
> (kinit command)?
> I am not sure smbclient should use kerberos authentification by tickets by
> default... can not check it for now.

I believe smbclient will read the values from your /etc/samba/smb.conf
file at startup unless you have pointed it elsewhere with the -s
option.   If you are also running a samba server you may have
configured options that are incompatible with the backuppc client use.
   But that still doesn't explain a difference between full and
incremental runs.

-- 
  Les Mikesell
lesmikes...@gmail.com

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

Re: [BackupPC-users] problem with samba

2017-11-21 Thread Евгений

> Kinit for micha@ARAVA to access hayun-34 failed: Cannot find KDC for requested realm This is about Kerberos.Have you configured kerberos properly? Is it working when you request ticket (kinit command)?I am not sure smbclient should use kerberos authentification by tickets by default... can not check it for now.  20.11.2017, 17:16, "Micha Silver" :Hello Craig,Thanks for responding.Here's what I did (I increased debug level on smbclient a bit for more verbose output):[root@barak ~]# nmblookup hayun-34192.168.1.158 hayun-34<00>[root@barak ~]# smbclient --versionVersion 4.6.2[root@barak ~]# smbclient //hayun-34/gis -U micha -E -d 3 -c tarmodelp_load_ex: refreshing parametersInitialising global parametersrlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)Processing section "[global]"added interface eno1 ip=192.168.1.8 bcast=192.168.1.255 netmask=255.255.255.0added interface virbr0 ip=192.168.122.1 bcast=192.168.122.255 netmask=255.255.255.0Client started (version 4.6.2).Connecting to 192.168.1.158 at port 445got OID=1.3.6.1.4.1.311.2.2.30got OID=1.2.840.48018.1.2.2Enter ARAVA\micha's password:  (connects OK)But when I add options to tarmode...[root@barak ~]# smbclient //hayun-34/gis -U micha -E -d 3 -c tarmode fulllp_load_ex: refreshing parametersInitialising global parametersrlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)Processing section "[global]"added interface eno1 ip=192.168.1.8 bcast=192.168.1.255 netmask=255.255.255.0added interface virbr0 ip=192.168.122.1 bcast=192.168.122.255 netmask=255.255.255.0Client started (version 4.6.2).resolve_lmhosts: Attempting lmhosts lookup for name hayun-34<0x20>resolve_wins: WINS server resolution selected and no WINS servers listed.resolve_hosts: Attempting host lookup for name hayun-34<0x20>Connecting to 192.168.1.158 at port 445got OID=1.3.6.1.4.1.311.2.2.30got OID=1.2.840.48018.1.2.2Kinit for micha@ARAVA to access hayun-34 failed: Cannot find KDC for requested realmGENSEC backend 'gssapi_spnego' registeredGENSEC backend 'gssapi_krb5' registeredGENSEC backend 'gssapi_krb5_sasl' registeredGENSEC backend 'spnego' registeredGENSEC backend 'schannel' registeredGENSEC backend 'naclrpc_as_system' registeredGENSEC backend 'sasl-EXTERNAL' registeredGENSEC backend 'ntlmssp' registeredGENSEC backend 'ntlmssp_resume_ccache' registeredGENSEC backend 'http_basic' registeredGENSEC backend 'http_ntlm' registeredGot challenge flags:Got NTLMSSP neg_flags=0x62898215NTLMSSP: Set final flags:Got NTLMSSP neg_flags=0x62088215NTLMSSP Sign/Seal - Initialising with flags:Got NTLMSSP neg_flags=0x62088215SPNEGO login failed: Logon failuresession setup failed: NT_STATUS_LOGON_FAILURENo prompt for password, it just fails. Obviously this is a samba problem, not strictly BackupPC, but any suggestions are welcome. And, as I said, from the web interface, incrementals from the Win7 host are working, but fulls are not.Thanks, Micha On 20/11/17 02:35, Craig Barratt via BackupPC-users wrote:Micha, I've tested Samba 4.7.0 and it works; I don't think the tar options have changed. The NT_STATUS_LOGON_FAILURE error shouldn't be bogus.  But I can't explain why incrementals work. Can you experiment with running smbclient manually to see what options do and don't work? Craig On Thu, Nov 16, 2017 at 1:27 PM, Micha Silver  wrote:About a month ago samba was updated to version 4.6 on my BackupPC server (version 3.3) and since then I can't do a full backup of Win7 machines. Incrementals work, but not the fulls. I get NT_STATUS_LOGON_FAILURE, but I think that's bogus. I have an idea that the problem is the "tarmode" part of the smbclient command. It seems that "tarmode verbose full" is not supported any longer. The only tarmode options that the new smbclient recognizes are full, inc, reset and noreset.Any suggestions what the smbclient command should be now with the newer samba version?Thanks -- 
Micha Silver
Ben Gurion Univ.
Sde Boker, Remote Sensing Lab
+972-523-665918 --Check out the vibrant tech community on one of the world's mostengaging tech sites, Slashdot.org! http://sdm.link/slashdot___BackupPC-users mailing listBackupPC-users@lists.sourceforge.netList:    https://lists.sourceforge.net/lists/listinfo/backuppc-usersWiki:    http://backuppc.wiki.sourceforge.netProject: http://backuppc.sourceforge.net/  --
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
 -- 
Ben Gurion Univ
Sde Boker

Re: [BackupPC-users] problem with samba

2017-11-20 Thread Micha Silver


  
  
Hello Craig,
  Thanks for responding.
  Here's what I did (I increased debug level on smbclient a bit for
  more verbose output):

[root@barak ~]# nmblookup hayun-34
  192.168.1.158 hayun-34<00>
  
[root@barak ~]# smbclient --version
Version 4.6.2

  [root@barak ~]# smbclient //hayun-34/gis -U micha -E -d 3
-c tarmode 
  lp_load_ex: refreshing parameters
  Initialising global parameters
  rlimit_max: increasing rlimit_max (1024) to minimum
Windows limit (16384)
  Processing section "[global]"
  added interface eno1 ip=192.168.1.8 bcast=192.168.1.255
netmask=255.255.255.0
  added interface virbr0 ip=192.168.122.1
bcast=192.168.122.255 netmask=255.255.255.0
  Client started (version 4.6.2).
  Connecting to 192.168.1.158 at port 445
  got OID=1.3.6.1.4.1.311.2.2.30
  got OID=1.2.840.48018.1.2.2
  Enter ARAVA\micha's password: 
 (connects OK)
  
  But when I add options to tarmode...

[root@barak ~]# smbclient //hayun-34/gis -U
micha -E -d 3 -c tarmode full
  lp_load_ex: refreshing parameters
  Initialising global parameters
  rlimit_max: increasing rlimit_max (1024) to minimum
Windows limit (16384)
  Processing section "[global]"
  added interface eno1 ip=192.168.1.8 bcast=192.168.1.255
netmask=255.255.255.0
  added interface virbr0 ip=192.168.122.1
bcast=192.168.122.255 netmask=255.255.255.0
  Client started (version 4.6.2).
  resolve_lmhosts: Attempting lmhosts lookup for name
hayun-34<0x20>
  resolve_wins: WINS server resolution selected and no WINS
servers listed.
  resolve_hosts: Attempting host lookup for name
hayun-34<0x20>
  Connecting to 192.168.1.158 at port 445
  got OID=1.3.6.1.4.1.311.2.2.30
  got OID=1.2.840.48018.1.2.2
  Kinit for micha@ARAVA to access hayun-34 failed: Cannot
find KDC for requested realm
  GENSEC backend 'gssapi_spnego' registered
  GENSEC backend 'gssapi_krb5' registered
  GENSEC backend 'gssapi_krb5_sasl' registered
  GENSEC backend 'spnego' registered
  GENSEC backend 'schannel' registered
  GENSEC backend 'naclrpc_as_system' registered
  GENSEC backend 'sasl-EXTERNAL' registered
  GENSEC backend 'ntlmssp' registered
  GENSEC backend 'ntlmssp_resume_ccache' registered
  GENSEC backend 'http_basic' registered
  GENSEC backend 'http_ntlm' registered
  Got challenge flags:
  Got NTLMSSP neg_flags=0x62898215
  NTLMSSP: Set final flags:
  Got NTLMSSP neg_flags=0x62088215
  NTLMSSP Sign/Seal - Initialising with flags:
  Got NTLMSSP neg_flags=0x62088215
  SPNEGO login failed: Logon failure
  session setup failed: NT_STATUS_LOGON_FAILURE
  
   No prompt for
  password, it just fails. Obviously this is a samba problem, not
  strictly BackupPC, but any suggestions are welcome. And, as I
  said, from the web interface, incrementals from the Win7 host are
  working, but fulls are not.
  
  Thanks, Micha
 


On 20/11/17 02:35, Craig Barratt via
  BackupPC-users wrote:


  Micha,


I've tested Samba 4.7.0 and it works; I don't think the tar
  options have changed.


The NT_STATUS_LOGON_FAILURE error shouldn't be bogus.  But
  I can't explain why incrementals work.


Can you experiment with running smbclient manually to see
  what options do and don't work?


Craig
  
  
On Thu, Nov 16, 2017 at 1:27 PM, Micha
  Silver 
  wrote:
  

  About a month ago samba was updated to version 4.6 on my
  BackupPC server (version 3.3) and since then I can't do a
  full backup of Win7 machines. Incrementals work, but not
  the fulls. I get NT_STATUS_LOGON_FAILURE, but I think
  that's bogus. I have an idea that the problem is the
  "tarmode" part of the smbclient command. It seems that
  "tarmode verbose full" is not supported any longer. The
  only tarmode options that the new smbclient recognizes are
  full, inc, reset and noreset. 
  Any suggestions what the smbclient command should be now
  with the newer samba version?
  Thanks
  
  -- 
Micha Silver
Ben Gurion Univ.
Sde Boker, Remote Sensing Lab
+972-523-665918


--
Check out the vibrant tech community on one of the world's
most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

Re: [BackupPC-users] problem with samba

2017-11-19 Thread Craig Barratt via BackupPC-users

Micha,

I've tested Samba 4.7.0 and it works; I don't think the tar options have
changed.

The NT_STATUS_LOGON_FAILURE error shouldn't be bogus.  But I can't explain
why incrementals work.

Can you experiment with running smbclient manually to see what options do
and don't work?

Craig

On Thu, Nov 16, 2017 at 1:27 PM, Micha Silver  wrote:

> About a month ago samba was updated to version 4.6 on my BackupPC server
> (version 3.3) and since then I can't do a full backup of Win7 machines.
> Incrementals work, but not the fulls. I get NT_STATUS_LOGON_FAILURE, but I
> think that's bogus. I have an idea that the problem is the "tarmode" part
> of the smbclient command. It seems that "tarmode verbose full" is not
> supported any longer. The only tarmode options that the new smbclient
> recognizes are full, inc, reset and noreset.
> Any suggestions what the smbclient command should be now with the newer
> samba version?
> Thanks
>
> --
> Micha Silver
> Ben Gurion Univ.
> Sde Boker, Remote Sensing Lab
> +972-523-665918
>
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> BackupPC-users mailing list
> BackupPC-users@lists.sourceforge.net
> List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
> Wiki:http://backuppc.wiki.sourceforge.net
> Project: http://backuppc.sourceforge.net/
>
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

[BackupPC-users] problem with samba

2017-11-16 Thread Micha Silver


  
  
About a month ago samba was updated to version 4.6 on my BackupPC
server (version 3.3) and since then I can't do a full backup of Win7
machines. Incrementals work, but not the fulls. I get
NT_STATUS_LOGON_FAILURE, but I think that's bogus. I have an idea
that the problem is the "tarmode" part of the smbclient command. It
seems that "tarmode verbose full" is not supported any longer. The
only tarmode options that the new smbclient recognizes are full,
inc, reset and noreset. 
Any suggestions what the smbclient command should be now with the
newer samba version?
Thanks

-- 
Micha Silver
Ben Gurion Univ.
Sde Boker, Remote Sensing Lab
+972-523-665918
  


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

Re: [BackupPC-users] problem with samba

Re: [BackupPC-users] problem with samba

Re: [BackupPC-users] problem with samba

Re: [BackupPC-users] problem with samba

Re: [BackupPC-users] problem with samba

Re: [BackupPC-users] problem with samba

[BackupPC-users] problem with samba

7 matches

Site Navigation

Mail list logo

Footer information