On 2019-08-29 19:55, Bob McClure Jr wrote:
On Thu, Aug 29, 2019 at 10:48:45PM +, Michael Stowe wrote:
On 2019-08-29 14:47, Michael Stowe wrote:
> On 2019-08-29 13:02, Bob McClure Jr wrote:
>
>> I'm at wit's end -- a short trip. I have a very simple setup of a Linux server (CentOS 6)
running BackupPC to back up a Win 10 Pro machine. BackupPC is BackupPC-3.3.1-5.el6.x86_64 from the EPEL
repo. On the Win 10 box, I created a normal user "backuppc" with a password, and then put him
in the local "Backup Operators" group. I'm using SMB for the backup method.
>>
>> # smbclient '//nate/C$' -U backuppc -c pwd Enter backuppc's password:
Domain=[NATE] OS=[Windows 10 Pro 18362] Server=[Windows 10 Pro 6.3] tree connect
failed: NT_STATUS_ACCESS_DENIED
>>
>> And of course, the backups fail. I've done a Web search from the Win 10
aspect, the samba aspect, and the BackupPC aspect, and have come up dry.
>>
>> Here is the hosts file:
>>
>> host dhcp user moreUsers nate 0 bob
>
> You can debug this entirely at the command line; you're likely to find "-d
debuglevel" helpful as it can help you pinpoint exactly what's going wrong.
>
> As another response alluded to, this is often due to smbclient not supporting
recent enough protocol versions; ratcheting up the debug level should allow you to
see the negotiation. If this is indeed the case, this can be mitigated by
upgrading smbclient (preferred) or allowing Win10 to fall back to older versions.
I'd still recommend that as a debugging method, but one other
potential
cause is that Win10 now disables remote access to the administrative
shares by default. They can be specifically re-enabled, but without
doing so, would generate an access denied error no matter what
credentials were used.
I tried the debug level at 3 (the highest recommended for mere
mortals) and found nothing educational.
I rebooted my workstation to CentOS 7 and tried smbclient and it, too,
failed, so I guess it's the remote access problem. Does that mean
rsync won't do any better than smb or does rsync get past the remote
restrictions?
Any clues on how to enable remote access? I'm not concerned about
security since we're behind a good firewall.
Cheers,
This is how to enable remote shares:
https://u2182357.ct.sendgrid.net/wf/click?upn=rBK8reUlX8Sxr7Iz1fV-2F7fB0NECgtVa3tQh4O52BIRkc9-2FxI35iS9RIffWOpxMiHDlA6Rik7ZqM5ULeaWsMfPcBwDahMJxrjwfA-2Bq1J0hWE-3D_OypFYCWzG5ApGW-2FFpGTxc4RCS9eud0Dl1htN5rYoUZ8To4zeNUFBkAGI3hzer91CG4cTrGD7J6lbr2S8rKruFJaFr3HD6Acrq1e6JDqWs-2FonTyT-2FvpG6YsaxO0wo23nI447AMCTK6PKUWErD5zqkMRMsxa8Ddmwq8fsQ-2FvPNPOCEsHs91K0AtI7-2F5WSzLZQTq8MtcMjojhu-2F1yJMraKlBa7tG7PrVsU4scW1-2Fpdy0lM-3D
This is how to enable older versions of the smb protocol:
https://u2182357.ct.sendgrid.net/wf/click?upn=rBK8reUlX8Sxr7Iz1fV-2F7Qgbyc8hNp-2BwXA9Wwf3uSMz-2Ff-2FFndnY61cbQ417VQmoH-2B0F2LWOyHDRpeiOS8m292oOfPzsb7Fbw-2BpFvCQ4SMmEqFawMqNFqVrHVPS2yX10mpJmRVkJybwWX3dKfBOsk-2F0Rpp6D736v4IoJiA6yBb1p9HsUWLqx4w-2BSM0-2BPMezbtgEewkV997QtEiwhrNT6Vxw-3D-3D_OypFYCWzG5ApGW-2FFpGTxc4RCS9eud0Dl1htN5rYoUZ8To4zeNUFBkAGI3hzer91CG4cTrGD7J6lbr2S8rKruFEIXTbsXfWZtSB0lat-2FM56v2zfxbuFYPR-2BhlM0MH36fnZPUnFTGBGGlFHyw6-2FQjUfS5XMT-2FrAJDDXA4Tcz63xPF1i7gPRaiWybANdab5VDe-2BZaFo-2FUr7NqRmjBN6xZ7J-2B4iPExEafxfpUjDBwMuLm7c-3D
Though to answer your question rsync doesn't rely (or is aware of in any
way) the default shares, and it doesn't use the smb protocol, so you
wouldn't have these problems. You may have a different set of problems,
mainly revolving around getting permissions and modules right, and (if
you use it) properly engaging shadowing. That said, SMB can't use
shadowing at all, so I see rsync as a major improvement in many ways and
use it for all my windows systems.
___
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/
