On 6/1/2016 11:56 AM, Jeff Boyce wrote:
>
> On 5/31/2016 4:28 PM, Holger Parplies wrote:
>> Hi,
>>
>> Jeff Boyce wrote on 2016-05-31 13:40:20 -0700 [Re: [BackupPC-users] Win 10
>> issue with NT_STATUS_BAD_NETWORK_NAME]:
>>> On 5/26/2016 1:51 PM, Jeff Boyce wrote:
>>> [......]
>>> Ok I solved all my backup issues, so this post will give a summary of
>>> what worked for me and hopefully help others.
>>> [...]
>>> I was unable to connect to the default C$ share for conducting the
>>> backup. [...]
>>>
>>> So in *almost* all of my desktop boxes that are backing up to BackupPC
>>> they are using these same settings and the Users share. I am not sure
>>> what is going on internally in the Windows networking that doesn't allow
>>> smbclient to connect to the default C$ share, but I am sure that
>>> something within Windows is stopping it.
>> stupid question: is it possible to connect to an administrative share with
>> user (i.e. non-admin) credentials?
> For all of my office Windows desktop systems the users are setup as
> administrative users, so I don't have any non-admin users to test what I
> think you are asking. robynr is an admin user on the Win10 box below.
> But as shown below I list the shares on a new Win10 box, then access the
> Users share, then try accessing the ADMIN$ share with the same
> credentials. I get the same results when trying the C$ share as with
> the ADMIN$ share shown below. But I am not sure if this is where you
> were going with your question.
>
> [root@bacteria ~]# su -s /bin/bash backuppc
> bash-4.1$
> bash-4.1$ smbclient -L rdr-lat6540 -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
> --------- -------
> bash-4.1$
> bash-4.1$ smbclient //rdr-lat6540/Users -U robynr
> Enter robynr's password:
> Domain=[RDR-LAT6540] OS=[Windows 10 Pro 10586] Server=[Windows 10 Pro 6.3]
> smb: \> dir
> . DR 0 Tue Mar 1 20:34:09 2016
> .. DR 0 Tue Mar 1 20:34:09 2016
> Default DHR 0 Tue Feb 9 14:30:16 2016
> Default.migrated D 0 Tue Feb 9 14:27:54 2016
> desktop.ini AHS 174 Fri Oct 30 00:21:27 2015
> Public DR 0 Tue Feb 9 14:41:32 2016
> robynr D 0 Tue May 31 07:54:32 2016
>
> 57635 blocks of size 4194304. 28478 blocks available
> smb: \> quit
> bash-4.1$
> bash-4.1$ smbclient //rdr-lat6540/ADMIN$ -U robynr
> Enter robynr's password:
> Domain=[RDR-LAT6540] OS=[Windows 10 Pro 10586] Server=[Windows 10 Pro 6.3]
> tree connect failed: NT_STATUS_ACCESS_DENIED
> bash-4.1$
I don't think ADMIN$ is a normal file share. You should be using C$ to
get access to the files for backup. What happens when you try to
connect to C$?
--
Bowie
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
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/
|
