Re: [BackupPC-users] Win 10 issue with NT_STATUS_BAD_NETWORK_NAME
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 ---- WorkgroupMaster ---- 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 . DR0 Tue Mar 1 20:34:09 2016 .. DR0 Tue Mar 1 20:34:09 2016 Default DHR0 Tue Feb 9 14:30:16 2016 Default.migratedD0 Tue Feb 9 14:27:54 2016 desktop.ini AHS 174 Fri Oct 30 00:21:27 2015 Public DR0 Tue Feb 9 14:41:32 2016 robynr D0 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$ >> [...] The exception is my own desktop system; BackupPC is using the >> default C$ share without any problem. > Which user are you using to connect in this case? Is that user a member of > a privileged group? In the case of my own desktop, jeffb is also setup as the administrative user on the Win7 box. Using the same procedures as above I can connect to the Users share. But in this case I can also connect to the C$ share. I also tested the F$ and G$ shares listed and could connect and list their directories also. I could also connect to the IPC$ share, but then got an NT_STATUS_ACCESS_DENIED response when trying to get a directory listing. bash-4.1$ smbclient -L jab-prec3610 -U jeffb Enter jeffb's password: Domain=[JAB-PREC3610] OS=[Windows 7 Professional 7601 Service Pack 1] Server=[Windows 7 Professional 6.1] Sharename Type Comment - --- ADMIN$ Disk Remote Admin C$ Disk Default share F$ Disk Default share G$ Disk Default share IPC$IPC Remote IPC Users Disk Domain=[JAB-PREC3610] OS=[Windows 7 Professional 7601 Service Pack 1] Server=[Windows 7 Professional 6.1] Server Comment ---- WorkgroupMaster ---- bash-4.1$ bash-4.1$ smbclient //jab-prec3610/Users -U jeffb Enter jeffb's password: Domain=[JAB-PREC3610] OS=[Windows 7 Professional 7601 Service Pack 1] Server=[Windows 7 Professional 6.1] smb: \> dir .
Re: [BackupPC-users] Win 10 issue with NT_STATUS_BAD_NETWORK_NAME
On 5/26/2016 1:51 PM, Jeff Boyce wrote: > > > On 5/26/2016 12:18 PM, Michael Stowe wrote: >> On 2016-05-26 13:46, Jeff Boyce wrote: >>> On 5/26/2016 4:57 AM, Michael Stowe wrote: >>>> 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 -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 >>> ---- >>> >>> WorkgroupMaster >>> ---- >>> >>> 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 >> >> At the risk of stating the obvious, if you must declare a workgroup >> to retrieve a listing of shares, then it's likely that you must also >> declare a workgroup to gain access to the shares. (Windows is usually >> quite casual about workgroups, except when it isn't, so you might >> just want to confirm you either don't need it for the listing, or add >> it for the connection.) >> >> NT_STATUS_ACCESS_DENIED comes from a few places, note that you're >> getting a failure to connect to the tree, so it's unlikely to be a >> folder permission error, it's more likely something earlier in the >> process, like authentication. This could be as simple as supplying >> the incorrect password, to an older version of smbclient which is >> fine with supplying the share list but refuses to negotiate SMB with >> W10, which requires stronger hashes. >> >> smbclient has changed its options and syntax a few times over time; I >> note that the -N switch does not appear in your backuppc command >> line, which is probably correct, since in more recent versions of >> smbclient, this apparently causes it to stop sending the password... >> But I also do not see a password on that command line. If you didn't >> cleanse it wh
Re: [BackupPC-users] Win 10 issue with NT_STATUS_BAD_NETWORK_NAME
On 5/26/2016 12:18 PM, Michael Stowe wrote: > On 2016-05-26 13:46, Jeff Boyce wrote: >> On 5/26/2016 4:57 AM, Michael Stowe wrote: >>> 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 >> ---- >> >> WorkgroupMaster >> ---- >> >> 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 > > At the risk of stating the obvious, if you must declare a workgroup to > retrieve a listing of shares, then it's likely that you must also > declare a workgroup to gain access to the shares. (Windows is usually > quite casual about workgroups, except when it isn't, so you might just > want to confirm you either don't need it for the listing, or add it > for the connection.) > > NT_STATUS_ACCESS_DENIED comes from a few places, note that you're > getting a failure to connect to the tree, so it's unlikely to be a > folder permission error, it's more likely something earlier in the > process, like authentication. This could be as simple as supplying > the incorrect password, to an older version of smbclient which is fine > with supplying the share list but refuses to negotiate SMB with W10, > which requires stronger hashes. > > smbclient has changed its options and syntax a few times over time; I > note that the -N switch does not appear in your backuppc command line, > which is probably correct, since in more recent versions of smbclient, > this apparently causes it to stop sending the password... But I also > do not see a password on that command line. If you didn't cleanse it > when you posted (which wouldn't be a terrible idea, obviously) then > I'd look there first, because that may mean it's not being sent, which > would explain that error. > > I am now doing an assessment of all the clients setup in backuppc and seeing some minor variations between clients, and what is working and what isn't. I am now noticing that I have another Win7 box that is giving the same NT_ STATUS_ACCES
Re: [BackupPC-users] Win 10 issue with NT_STATUS_BAD_NETWORK_NAME
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} = '';
>> $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 Comm
[BackupPC-users] Win 10 issue with NT_STATUS_BAD_NETWORK_NAME
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} = '';
$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
--
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@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] Off-site backup options (slightly OT)
Greetings - I am running BackupPc to backup 8 desktop systems (mostly Windows) in my office to a CentOS 6 VM on my in-house server. It currently takes about 150GB of storage space. I would like to replicate (on a daily basis) the backup to an off-site system for disaster recovery purposes. I have searched through the archives and read much discussion about this, which generally concludes that using rsync to replicate the backup is not appropriate. Tim Massey's post of 2/22/2011 sums up the options pretty clearly. * For most people, rsync does not work to replicate a backup server effectively. Period. I think *no* one would suggest this as a reliable ongoing method of replicating a BackupPC server. Ever. * The best methods for this boil down to two camps: 1) Run two BackupPC servers and have both back up the hosts directly No replication at all: it just works. 2) Use some sort of block-based method of replicating the data * Block-based replication boils down to two methods 1) Use md or dm to create a RAID-1 array and rotate members of this array in and out 2) Use LVM to create snapshots of partitions and dd the partition to a different drive (I guess 3) Stop BackupPC long enough to do a dd of the partition *without* lVM) My backup pool is located on a separate LVM partition and I have some spare disk space, so I can do LVM snapshots. But my primary question is that I am looking for recommendations for a 3rd party off-site storage vendor that is set up to accept dd'ing a LVM snapshot to a partitioned space. I am completely open to all options here, as I have not worked with any off-site storage vendors previously. Please cc me directly as I only receive the digest version of the mailing list, which appears to be only sent out about once a month. Thanks. Jeff -- Jeff Boyce Meridian Environmental www.meridianenv.com -- Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/ ___ 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] Need guidance for backing up remote Windows PC
- Original Message - From: "Holger Parplies" To: "Les Mikesell" ; Cc: "General list for user discussion, questions and support" Sent: Wednesday, March 20, 2013 3:11 PM Subject: Re: [BackupPC-users] Need guidance for backing up remote Windows PC > Hi, > > Les Mikesell wrote on 2013-03-20 16:19:23 -0500 [Re: [BackupPC-users] Need > guidance for backing up remote Windows PC]: >> On Wed, Mar 20, 2013 at 4:00 PM, Jeff Boyce >> wrote: >> > [...] >> > Local Network >> > Sequoia = Samba (and WINS server) and OpenVPN server (192.168.112.50) >> > Taxa = DNSmasq (dns and dhcp server) (192.168.112.51) >> > Bacteria = BackupPC server (192.168.112.52) >> > Network IP = 192.168.112.0/24 > > ok. > >> > Remote Windows Box >> > Computer Name = jks-e6500 >> > Remote LAN IP = unknown >> > Remote WAN IP = dynamic >> > OpenVPN Common Name = jkssequoiaclient > > All of these don't matter for the question at hand. > >> > OpenVPN IP = static, 10.9.8.10 >> > OpenVPN routed network > >> [...] >> If you manage local dns you can add the target name with the VPN IP >> and everything should work the same as locally. Alternatively, you >> could set ClientNameAlias to the VPN IP in the backuppc config. > > In particular, you can choose whatever name for the client suits your > purposes. Usually, you will want to use just one name for one machine, but > since you've used a different one in the OpenVPN certificate, I thought > I'd > mention it. The name in the certificate is really only used for selecting > the > clients/ file (in OpenVPN), which usually defines the IP used. It does > *not* > magically set up some sort of name resolution for that name. I would have > used > "jks-e6500" to match the host name, but it doesn't really make any > difference. > > Adding something like > > 10.9.8.10 jks-e6500 > > to a hosts-type file (/etc/hosts on the BackupPC server or better a hosts > file > served by your DNSmasq server) should do the trick. > > Talking of hosts files, the DHCP flag in BackupPC's hosts file should be 0 > :-). > >> > My thinking is that since the remote Windows box can connect and browse >> > the >> > Samba shares on Sequoia via the VPN, then obviously Samba knows how to >> > communicate with this remote client. > > At the TCP level, the Samba server doesn't really need to know anything. > There's an incoming connection from an IP it can route reply packets to. > Fine. Samba itself might require more, in order to determine whether to > allow access or not. The remote machine might register itself with the > Samba WINS server. But it's the remote machine that initiates the > connection. > >> No, that's not entirely obvious unless the backuppc server is also the >> VPN server. Sometimes VPN servers are configured to NAT to their >> ethernet interfaces to provide LAN connectivity for the remote >> clients. > > That's a good point. If that were the case, you'd need to rethink things. > >> In your case you need routing from the backuppc server to >> the client IP which may or may not be present. Can you connect with >> smbclient to the 10.9.8.10 IP? > > If your VPN server is not NATting and it's not the default gateway, then > you'd > need either a host or probably better a network route (on your BackupPC > server): > > # route add -host 10.9.8.10 gw sequoia > or > # route add -net 10.9.8.0/24 gw sequoia > > Additionally, if sequoia was not previously routing traffic, you might > need to > > # echo 1 > /proc/sys/net/ipv4/ip_forward > > (on sequoia) which you'd want to do automatically on reboot by adding (or > uncommenting) > > net.ipv4.ip_forward=1 > > in /etc/sysctl.conf. For IPv6, see the comments in sysctl.conf. > > Regards, > Holger > Greetings - I have had to move on to some other more pressing issues temporarily, but I think the guidance you guys have given me will get me to the next stage of implementing this and running some tests. Thanks. Jeff -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar ___ 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] Need guidance for backing up remote Windows PC
Greetings - I am trying to figure out if my objective is possible. I want to be able to backup a remote Window box that connects to the local network via OpenVPN. I have scanned through the archives and have seen some discussion of similar things, but nothing that really gives me good overall direction on whether it will work, or how to get it to work, with my network configuration. I am using BackupPC to backup the local Windows boxes, and would like to add a remote one. I am not that concerned about the time it would take to complete a backup over the WAN, as I can configure it to work at night. Local Network Sequoia = Samba (and WINS server) and OpenVPN server (192.168.112.50) Taxa = DNSmasq (dns and dhcp server) (192.168.112.51) Bacteria = BackupPC server (192.168.112.52) Network IP = 192.168.112.0/24 Remote Windows Box Computer Name = jks-e6500 Remote LAN IP = unknown Remote WAN IP = dynamic OpenVPN Common Name = jkssequoiaclient OpenVPN IP = static, 10.9.8.10 OpenVPN routed network I have BackupPC configured to connect to the local Window boxes via SMB, as I didn't care for the cygwin and rsync implementation on windows when I used it in the past. Besides, I already have Samba configured and running just fine, so why not just use it. I seem to have both DNS and netbios name resolution working properly for the local LAN, but don't know how the remote box fits into that when it connects to Samba via a VPN network. My thinking is that since the remote Windows box can connect and browse the Samba shares on Sequoia via the VPN, then obviously Samba knows how to communicate with this remote client. Somehow I need to understand how that is occurring (what name or what IP address is Samba referencing for the remote box?) and make that information known to the BackupPC server (possibly via the DNSmasq server?) so that it could initiate a backup. Any suggestions on a general approach to evaluating how to achieve my objective would be appreciated. Please CC me directly as I only get the mailing list via the daily digest. Thanks. Jeff Boyce Meridian Environmental www.meridianenv.com -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar ___ 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] Issue with SELinux context
Greetings - I have been testing BackupPC on a guest VM on my CentOS 6.3 box. I have the backups being stored on a separate partition using LVM so that I can expand the space in the future as needed. My initial testing of the system was good, and yesterday I expanded the logical volume for the storage space. After rebooting the VM, I noticed that SELinux needed to do a relabel. I didn't think much of it until a couple hours later when I went to look at BackupPC and could not see the previous test backups that had been created, or the log files. When selecting Browse Backups, I get this error. Error: Backup number for host jab-opti755 does not exist. When selecting Log File, I get this error. Can't open log file A little Googling initially led me to recreate the backup file for each host using the /usr/share/BackupPC/bin/BackupPC_fixupBackupSummary script that is provided. This did not solve the problem, as I still get the same errors as above. Then remembering the SELinux relabel, I turned SELinux off temporarily (setenforce 0). Now I could see the host backups and log files with no errors. Turning SELinux back on again, and the errors returned. So knew that it was just an improper SELinux context somewhere. So to summarize, here is the information I have: Backups are being stored on separate partition, not standard for BackupPC: /bkupdata Standard BackupPC storage location: /var/lib/BackupPC SELinux context on standard BackupPC storage location: [root@bacteria BackupPC]# pwd /var/lib/BackupPC [root@bacteria BackupPC]# ls -Z drwxr-x---. backuppc backuppc system_u:object_r:var_lib_t:s0 cpool drwxr-x---. backuppc backuppc system_u:object_r:var_lib_t:s0 pc drwxr-x---. backuppc backuppc system_u:object_r:var_lib_t:s0 pool drwxr-x---. backuppc backuppc system_u:object_r:var_lib_t:s0 trash Current SELinux context on my BackupPC storage location: [root@bacteria bkupdata]# pwd /bkupdata [root@bacteria bkupdata]# ls -Z drwxr-x---. backuppc root system_u:object_r:default_t:s0 cpool drwx--. root root system_u:object_r:default_t:s0 lost+found drwxr-x---. backuppc root system_u:object_r:default_t:s0 pc drwxr-x---. backuppc root system_u:object_r:default_t:s0 pool drwxr-x---. backuppc root system_u:object_r:default_t:s0 trash And one of the test hosts at this location: [root@bacteria jab-opti755]# pwd /bkupdata/pc/jab-opti755 [root@bacteria jab-opti755]# ls -Z drwxr-x---. backuppc backuppc system_u:object_r:default_t:s0 0 drwxr-x---. backuppc backuppc system_u:object_r:default_t:s0 1 drwxr-x---. backuppc backuppc system_u:object_r:default_t:s0 2 drwxr-x---. backuppc backuppc system_u:object_r:default_t:s0 3 drwxr-x---. backuppc backuppc system_u:object_r:default_t:s0 4 drwxr-x---. backuppc backuppc system_u:object_r:default_t:s0 5 -rw-r-. backuppc backuppc system_u:object_r:default_t:s0 backups -rw-r-. backuppc backuppc system_u:object_r:default_t:s0 backups.old -rw-r-. backuppc backuppc system_u:object_r:default_t:s0 backups.save -rw-r-. backuppc backuppc system_u:object_r:default_t:s0 LOCK -rw-r-. backuppc backuppc system_u:object_r:default_t:s0 LOG.032013 -rw-r-. backuppc backuppc system_u:object_r:default_t:s0 XferLOG.0.z -rw-r-. backuppc backuppc system_u:object_r:default_t:s0 XferLOG.1.z -rw-r-. backuppc backuppc system_u:object_r:default_t:s0 XferLOG.2.z -rw-r-. backuppc backuppc system_u:object_r:default_t:s0 XferLOG.3.z -rw-r-. backuppc backuppc system_u:object_r:default_t:s0 XferLOG.4.z -rw-r-. backuppc backuppc system_u:object_r:default_t:s0 XferLOG.5.z -rw-r-. backuppc backuppc system_u:object_r:default_t:s0 XferLOG.bad.z.old In reviewing my SELinux contexts listed above, I noticed that the group assignment for the directories under /bkupdata is root. I have subsequently changed them to backuppc, and shutdown the backuppc service, shutdown and restarted the http service, then restarted the backuppc service. The same errors persist after this change, so the issue was not just with an incorrect group setting. So my question is: What is the proper SELinux context for the BackupPC storage directories when those directories are not in the standard location. I would assume that the SELinux Type context would not be "var_lib_t" because it is not located in /var/lib, but don't really know for sure, and if not what should it be? I don't know what it was before the SELinux relabel (and everything worked properly before the relabel). If I knew what the right SELinux context should be I could probably fix it fairly easily, but would take anyone's recommendations on that approach also. What I don't want to do is just leave SELinux enforcing turned off. I am currently digging through my SELinux logs to try to interpret and understand them. Please CC me directly with any replies as I only get the (infrequent) daily digest. Thanks. Jeff Boyce Me
[BackupPC-users] Connection failed, nt status bad network name - Solved
s showed a lot of discussion about removing the -N flag from the SmbClientFullCmd line in the main configuration file. Since many of the discussions were several years old, and primarily addressing Ubuntu and Debian distributions I was a little skeptical that it would work, since I am running CentOS6. But, I made that one change to remove the -N flag from the smbclient command, and my backup now starts, It looks like maybe the smbclient -N flag should be removed from the stock configuration file if it is affecting all the distributions. Also I would suggest to the developers to change the error output that indicates that ping is not successful, when ping is actually working, and the problem is something else. It could prevent a lot of wild goose chases. Thanks. Jeff Boyce Meridian Environmental www.meridianenv.com -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar ___ 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] Connection failed, nt status bad network name
- Original Message - From: "Les Mikesell" To: "Jeff Boyce" Cc: "General list for user discussion, questions and support" Sent: Friday, March 08, 2013 4:05 PM Subject: Re: [BackupPC-users] Connection failed, nt status bad network name > On Fri, Mar 8, 2013 at 5:57 PM, Jeff Boyce wrote: >> >>> Try using smbclient to connect to the shares you are trying to back >>> up, using the same names and credentials. You might get better error >>> messages in an interactive mode. >>> >> >> I am not familiar with smbclient options and example usage. Will have to >> look this up more, but a basic query gives the same error as BackupPC. >> >> [root@bacteria ~]# smbclient -L jab-opti755 >> Enter root's password: >> session setup failed: NT_STATUS_LOGON_FAILURE > > You probably don't have a 'root' user on the windows box. Try: > smbclient '//jab-opti755/c$' -UAdministrator > or something that matches your shares. > [root@bacteria ~]# smbclient '//jab-opti755/c$' -UAdministrator Enter Administrator's password: Anonymous login successful Domain=[WORKGROUP] OS=[Windows Vista (TM) Ultimate 6002 Service Pack 2] Server=[Windows Vista (TM) Ultimate 6.0] tree connect failed: NT_STATUS_ACCESS_DENIED Ok, that one didn't work. But if I switch to the user that is common between Bacteria and jab-opti755, I can connect and see the desired share that I want to backup. What does this tell me? Where do I go from here? [jeffb@bacteria root]$ smbclient '//jab-opti755/f$' Enter jeffb's password: Domain=[JAB-OPTI755] OS=[Windows Vista (TM) Ultimate 6002 Service Pack 2] Server=[Windows Vista (TM) Ultimate 6.0] smb: \> smb: \> smb: \> dir $RECYCLE.BIN DHS0 Sat Feb 23 16:58:00 2013 01 Cull Files DA0 Mon Mar 4 15:00:22 2013 010 DVD TempWrite DA0 Mon Mar 4 12:43:14 2013 011 ExportedEmail DA0 Sun Feb 24 12:16:51 2013 012 QBTimerDA0 Sun Feb 24 12:06:24 2013 013 Email D0 Fri Mar 8 15:57:22 2013 02 Office Home TransferDA0 Sun Feb 24 11:04:21 2013 03 Office Projects DA0 Sun Feb 24 11:04:13 2013 04GISData DA0 Sun Feb 24 11:39:09 2013 05GISArchiveData DA0 Sun Feb 24 12:05:05 2013 06 Office ReferenceDA0 Tue Mar 5 10:10:49 2013 07 Home Projects DA0 Sun Feb 24 12:07:03 2013 08 OpenSource DA0 Mon Feb 25 16:16:32 2013 09 CD-DVD TempWriteDA0 Mon Mar 4 12:49:25 2013 System Volume Information DHS0 Sat Feb 23 16:57:54 2013 48078 blocks of size 4194304. 24409 blocks available >> My Samba config does not include a name resolve order setting. And >> looking >> at the original Samba config that came with the CentOS 6 installation, >> there >> was not one in that either. I checked my old Samba Server (RHEL 3) and >> it >> was in the original config for that one, but commented out. Is this >> maybe >> my problem, do I need to include the following line in my Samba config to >> complete a proper configuration? >> >> name resolve order = wins lmhosts bcast host > > None of that should matter if your DNS works. > > -- > Les Mikesell > lesmikes...@gmail.com > Jeff Jeff Boyce Meridian Environmental -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ 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] Connection failed, nt status bad network name
- Original Message - From: "Les Mikesell" To: "General list for user discussion, questions and support" Cc: "Jeff Boyce" Sent: Friday, March 08, 2013 3:28 PM Subject: Re: [BackupPC-users] Connection failed, nt status bad network name > On Fri, Mar 8, 2013 at 3:35 PM, Jeff Boyce wrote: >> >> I am setting up BackupPC for the first time and it is failing to connect >> to >> the first test client. The error that BackupPC is giving me is shown >> below. >> >> Error: >> tree connect failed: NT_STATUS_BAD_NETWORK_NAME >> >> Then later I see this at the top of the Host Summary Page: >> Pings to jab-opti755 have failed 23 consecutive times. > > Do the target's have their host firewalls enabled? > >> My hypothesis, is that I do not have proper NetBios name resolution (or >> caching) occurring within my network. > > If you have fixed IP's and they are in DNS it shouldn't matter. > >> >> However, from Bacteria I can't get a listing of NetBios names. >> >> [root@bacteria ~]# findsmb > > Will this show netbios name? > nmblookup -A 192.168.112.125 > Yes, this appears to show netbios name. [root@bacteria ~]# nmblookup -A 192.168.112.125 Looking up status of 192.168.112.125 JAB-OPTI755 <00> - M WORKGROUP <00> - M JAB-OPTI755 <20> - M WORKGROUP <1e> - M >> If there is any additional information that is needed to help pinpoint >> the >> problem, or identify a solution, let me know. My knowledge of NetBios >> naming is pretty limited, so I am looking for some expert guidance to >> resolve this issue. > > Try using smbclient to connect to the shares you are trying to back > up, using the same names and credentials. You might get better error > messages in an interactive mode. > I am not familiar with smbclient options and example usage. Will have to look this up more, but a basic query gives the same error as BackupPC. [root@bacteria ~]# smbclient -L jab-opti755 Enter root's password: session setup failed: NT_STATUS_LOGON_FAILURE I have been reviewing Chapter 10 (Network Browsing) of the Samba documents, and here is something that caught my attention. I am not sure if this is something relevant to my issue, so I am hoping someone can enlighten me. My Samba config does not include a name resolve order setting. And looking at the original Samba config that came with the CentOS 6 installation, there was not one in that either. I checked my old Samba Server (RHEL 3) and it was in the original config for that one, but commented out. Is this maybe my problem, do I need to include the following line in my Samba config to complete a proper configuration? name resolve order = wins lmhosts bcast host Jeff Jeff Boyce Meridian Environmental www.meridianenv.com -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ 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] Connection failed, nt status bad network name
11 DHCP Server . . . . . . . . . . . : 192.168.112.51 DHCPv6 IAID . . . . . . . . . . . : 251666843 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-18-BB-89-74-00-21-9B-32-4F-E7 DNS Servers . . . . . . . . . . . : 192.168.112.51 Primary WINS Server . . . . . . . : 192.168.112.50 NetBIOS over Tcpip. . . . . . . . : Enabled In general, my Samba file server appears to be doing everything properly for the file server. Windows desktops are able to connect and browse Samba shares. The same Samba configuration has been in place for more than a year, without a problem. Also my DNSmasq/DNS server seems to be working for a while now without any problems. As I mentioned above, I believe that there is something mis-configured on my network such that NetBios names are not being resolved or cached, so that Bacteria (BackupPC) can use them properly. If there is any additional information that is needed to help pinpoint the problem, or identify a solution, let me know. My knowledge of NetBios naming is pretty limited, so I am looking for some expert guidance to resolve this issue. Please CC me directly with any responses, as I only get the daily digest of the mailing list. Thanks. Jeff Boyce Meridian Environmental www.meridianenv.com -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ 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/
