On 5/26/2016 4:57 AM, Michael Stowe wrote:
> On 2016-05-25 17:14, Jeff Boyce wrote:
>> Greetings -
>>
>> I recently converted a Win7 box to a Win10 box. Ever since this
>> change the Win10 box has failed to backup. I have another Win7 box with
>> the same configuration for BackupPC as the Win10 box, except a different
>> user and password, and this Win7 box is still working. This indicates to
>> me that there was some change in the networking stuff of Win10 that has
>> caused my problem, but I don't have a clue to what it might be. I am
>> running BackupPC 3.3.1 on a CentOS 6 box, using SMB as the transfer
>> method.
>>
>> The config and error log for the broken Win10 box:
>> /etc/BackupPC/pc/rdr-lat6540.pl
>> $Conf{BackupFilesOnly} = {
>> 'C' => [
>> '\\users\\robynr\\AppData\\Local\\Microsoft\\Windows Live Mail'
>> ]
>> };
>> $Conf{SmbSharePasswd} = 'xxxxxxxx';
>> $Conf{SmbShareUserName} = 'robynr';
>> $Conf{SmbShareName} = [
>> 'C'
>> ];
>>
>> Host name resolution works. Bacteria is the BackupPC box.
>> [root@bacteria ~]# perl -e 'print(gethostbyname("rdr-lat6540") ? "ok/n"
>> : "not found/n");'
>> ok/n
>>
>> Abbreviated Error Log
>> 2016-05-25 14:12:36 full backup started for share C
>> 2016-05-25 14:12:38 Got fatal error during xfer (tree connect failed:
>> NT_STATUS_BAD_NETWORK_NAME)
>> 2016-05-25 14:12:43 Backup aborted (tree connect failed:
>> NT_STATUS_BAD_NETWORK_NAME)
>>
>> Detailed Error Log
>> Running: /usr/bin/smbclient \\\\rdr-lat6540\\C -U robynr -E -d 1 -c
>> tarmode\ full -Tc - \\users\\robynr\\AppData\\Local\\Microsoft\\Windows\
>> Live\ Mail
>> full backup started for share C
>> Xfer PIDs are now 19313,19312
>> Domain=[RDR-LAT6540] OS=[Windows 10 Pro 10586] Server=[Windows 10 Pro
>> 6.3]
>> This backup will fail because: tree connect failed:
>> NT_STATUS_BAD_NETWORK_NAME
>> tree connect failed: NT_STATUS_BAD_NETWORK_NAME
>> Domain=[RDR-LAT6540] OS=[Windows 10 Pro 10586] Server=[Windows 10 Pro
>> 6.3]
>> tree connect failed: NT_STATUS_BAD_NETWORK_NAME
>> tarExtract: Done: 0 errors, 0 filesExist, 0 sizeExist, 0 sizeExistComp,
>> 0 filesTotal, 0 sizeTotal
>> Got fatal error during xfer (tree connect failed:
>> NT_STATUS_BAD_NETWORK_NAME)
>> Backup aborted (tree connect failed: NT_STATUS_BAD_NETWORK_NAME)
>> Not saving this as a partial backup since it has fewer files than the
>> prior one (got 0 and 0 files versus 0)
>>
>> I have been searching the mailing list archives and other sources online
>> for 2 days to try and diagnose this. The error messages don't seem
>> clear enough to me. I have the exact same configuration on a Win7 box
>> that is working. The only possibility that I see online is reference to
>> the SMB protocols changing between Win7 and Win10 that has some issues
>> with network discovery, but nothing specific to BackupPC. Is there
>> anyone that has BackupPC backing up Win10 clients that might be able to
>> shed some light on this?
>>
>> Please cc me directly as I only receive the daily digest of this list
>> (which is more like once every couple weeks). Thanks.
>>
>> Jeff
>>
>> --
>>
>> Jeff Boyce
>> Meridian Environmental
>
> It must be said: there are a lot of potential causes for
> NT_STATUS_BAD_NETWORK_NAME, so what solves one issue may not solve
> another. However, I do recommend you start with the obvious thing
> that the error message is telling you, mainly that W10 does not have a
> share named C.
>
> Perhaps simple sharing is turned on, perhaps the share name has been
> transliterated to something else. You might want to try the
> troubleshooting step of listing the actual share names:
>
> /usr/bin/smbclient -L //rdr-lat6540
>
>
Well, it took a little variation of the smbclient command to get to what
you are looking for, but here are the results.
bash-4.1$ smbclient -L rdr-lat6540 -W workgroup -U robynr
Enter robynr's password:
Domain=[RDR-LAT6540] OS=[Windows 10 Pro 10586] Server=[Windows 10 Pro 6.3]
Sharename Type Comment
--------- ---- -------
ADMIN$ Disk Remote Admin
C$ Disk Default share
IPC$ IPC Remote IPC
print$ Disk Printer Drivers
Users Disk
Domain=[RDR-LAT6540] OS=[Windows 10 Pro 10586] Server=[Windows 10 Pro 6.3]
Server Comment
--------- -------
Workgroup Master
--------- -------
So noticing that my that share on rdr-lat6540 is listed as C$ and not
just C, as in my configuration file. I made the appropriate changes in
the configuration file and now I get a different error. So I guess I am
making progress, but it might be sideways instead of forward. Now my
full error is:
Running: /usr/bin/smbclient \\\\rdr-lat6540\\C\$ -U robynr -E -d 1 -c tarmode\
full -Tc - \\users\\robynr\\AppData\\Local\\Microsoft\\Windows\ Live\ Mail
full backup started for share C$
Xfer PIDs are now 8068,8067
Domain=[RDR-LAT6540] OS=[Windows 10 Pro 10586] Server=[Windows 10 Pro 6.3]
tree connect failed: NT_STATUS_ACCESS_DENIED
Domain=[RDR-LAT6540] OS=[Windows 10 Pro 10586] Server=[Windows 10 Pro 6.3]
tree connect failed: NT_STATUS_ACCESS_DENIED
tarExtract: Done: 0 errors, 0 filesExist, 0 sizeExist, 0 sizeExistComp, 0
filesTotal, 0 sizeTotal
Got fatal error during xfer (No files dumped for share C$)
Backup aborted (No files dumped for share C$)
Not saving this as a partial backup since it has fewer files than the prior one
(got 0 and 0 files versus 0)
I would guess that the NT_STATUS_ACCESS_DENIED error is a permissions or
sharing problem on the Win10 box, but I am not seeing what it might be.
I have file and printer sharing turned on for the C$ share, and the
firewall is currently turned off while testing this. What else should I
be looking at?
Jeff
--
Jeff Boyce
Meridian Environmental
------------------------------------------------------------------------------
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
|
