Sergei Dubarev
2004-Aug-25  19:27 UTC
[Samba] samba 3.0.3 + windows backup software = strange issue
Hello!
Sorry if I am wrong with the target list but here's a picture of an issue
that
we have with Samba 3.0.3 and standard Windows Backup software.
Actors: 1) Standard Windows Backup software that is bundled with the OS;
        2) Windows 2000 SP4 Russian and Windows XP SP2 English;
        3) Samba 3.0.3 running at Linux box in the Local Mode (i.e. all users 
are authenticated locally) -- please see the smb.conf file that is attached 
to this mail. 
Notes. 1) No clashing user names on Windows and Linux; no clashing workgroup 
or domain names; client machines and Linux box are on different workgroups.
       2) Log and config files are tarred and then bzipped into the single 
archive and attached to this message.
Below I will describe some test cases that we had today.
Case 1. Samba server with a public share on it ("public1"). Windows
2000 with
a local user ("builder") logged in. A public share from Linux box is
mapped
as a network drive. Copying files via Explorer is working fine. Starting 
Windows Backup software and trying to backup all of the files from the 
network drive is OK, too. (Please see the smb.log.ok2 file attached to this 
message).
Case 2. Samba server with a public share on it ("public1"). Windows
2000 with
a domain user ("wow") logged in. A public share from Linux box is
mapped as a
network drive. Copying files via Explorer is working fine. Starting Windows 
Backup software and trying to backup all of the files from the network drive 
is OK, too. (Please see the smb.log.ok file attached to this message).
Case 3. Samba server with a public share on it ("public1"). Windows XP
with a
domain user ("ivr") logged in. A public share from Linux box is mapped
as a
network drive. Copying files via Explorer is working fine. Starting Windows 
Backup software and trying to backup all of the files from the network drive 
leads to the Access Denied message; backup process does not even start, and 
backup software does not display a contents of a network drive. (Please see 
the smb.log.bad file attached to this message).
Case 4. Samba server with a public share on it ("public1"). Windows
2000 with
a domain user ("sergei") logged in. A public share from Linux box is
mapped
as a network drive. Copying files via Explorer is working fine. Starting 
Windows Backup software and trying to backup all of the files from the 
network drive leads to the Access Refused message; backup process does not 
even start, and backup software does not display a contents of a network 
drive.
It came out that for some reason a) backup software launched from a domain 
user account cannot contact network drive while Windows Explorer can, and b) 
not all of the domain accounts are influenced. Please note that domain 
accounts all have equal level of permissions.
Hope to hear from you soon. Thanks in advance.
P.S. Recently it was reported that similar issue may occur when copying backup 
files back to Linux box using standard Windows Backup software on Windows 
2000. I will try to get more results about this one soon.
-- 
Best regards,
Sergei Dubarev.
mailto:sergei@scenosaurus.org
ICQ UIN 130228091
--
Jeremy Allison
2004-Aug-25  19:49 UTC
[Samba] samba 3.0.3 + windows backup software = strange issue
On Wed, Aug 25, 2004 at 10:28:18PM +0300, Sergei Dubarev wrote:> Hello! > > Sorry if I am wrong with the target list but here's a picture of an issue that > we have with Samba 3.0.3 and standard Windows Backup software. > > Case 3. Samba server with a public share on it ("public1"). Windows XP with a > domain user ("ivr") logged in. A public share from Linux box is mapped as a > network drive. Copying files via Explorer is working fine. Starting Windows > Backup software and trying to backup all of the files from the network drive > leads to the Access Denied message; backup process does not even start, and > backup software does not display a contents of a network drive. (Please see > the smb.log.bad file attached to this message).This is a known bug we fixed for 3.0.6, I'd suggest upgrading. Cheers, Jeremy