samba - Jan 2010 - Ubuntu Jaunty samba 3.3.2 print$ no write rights even though I do

I finally fixed my problem by removing samba completely removing samba and
reinstalling it. What I discovered is it appears to be an issue with rights.
When I reinstalled samba the /var/lib/samba had rights like this.

drwxrwxr-x+ 5 root root 4096 2010-01-11 23:27 samba 

On my original install where the 5 is it was a 6. After the reinstall the rights
the rights on /var/lib/samba was reset to 5 and I made Domain Admins have read
write execute rights on the folder with setfacl. Now everything is working.

-Glenn 

----- Original Message ----- 
From: "Glenn T. Arnold" <garnold at unrealsolutions.com> 
To: "Samba" <samba at lists.samba.org> 
Sent: Thursday, July 16, 2009 4:16:48 PM 
Subject: Re: [Samba] Ubuntu Jaunty samba 3.3.2 print$ no write rights even
though I do

Dale, 

Yes, I have the right assigned to my Domain Admins group and I just added it to
my account just encase there is a group rights problem. Here is my user id
rights.

net rpc rights list "Domain\myaccount" 
Enter root's password: 
SeMachineAccountPrivilege 
SeTakeOwnershipPrivilege 
SeBackupPrivilege 
SeRestorePrivilege 
SeRemoteShutdownPrivilege 
SePrintOperatorPrivilege 
SeAddUsersPrivilege 
SeDiskOperatorPrivilege 


Thanks for the suggestion! 
-Glenn 

----- Original Message ----- 
From: "Dale Schroeder" <dale at BriannasSaladDressing.com> 
To: "Glenn T. Arnold" <garnold at unrealsolutions.com> 
Cc: "Samba" <samba at lists.samba.org> 
Sent: Thursday, July 16, 2009 3:58:08 PM GMT -05:00 US/Canada Eastern 
Subject: Re: [Samba] Ubuntu Jaunty samba 3.3.2 print$ no write rights even
though I do

Glenn, 

Have you granted your user Print Operator privileges? 

net rpc rights grant <user> SePrintOperatorPrivilege -U root 

http://us3.samba.org/samba/docs/man/Samba-HOWTO-Collection/NetCommand.html#id2601337

Dale 


Glenn T. Arnold wrote: 

Initially when I posted my access problems to print$ I was using the new
registry based smb.conf I had my whole configuration in the registry. Now I move
my printers and print$ back to the text based smb.conf and I copied the standard
ubuntu debian [printers] and [print$] out of the original ubuntu package
smb.conf and the only modification that I made was under the [print$] I change
read only to no instead of yes. I can not write to the share. Simply renaming
print$ section to print I can access the share and write to it with no problems.
Any more suggestions? I need to get this resolved. Here is my smb.conf now:
[global] 
# configbackend = registry 
include = registry 
[printers] 
comment = All Printers 
browseable = no 
path = /var/spool/samba 
printable = yes 
guest ok = no 
read only = yes 
create mask = 0700 

[print$] 
comment = Printer Drivers 
path = /var/lib/samba/printers 
browseable = yes 
read only = no 
guest ok = no 

Thanks 
-Glenn 

----- Original Message ----- 
From: "Glenn T. Arnold" <garnold at unrealsolutions.com> To:
samba at lists.samba.org Sent: Wednesday, July 8, 2009 1:17:21 PM GMT -05:00
US/Canada Eastern
Subject: Re: [Samba] Ubuntu Jaunty samba 3.3.2 print$ no write rights even
though I do; -)

I did the suggested updates to app armor and this did not solve the problem. 

-Glenn 

----- Original Message ----- 
From: "Glenn T. Arnold" <garnold at unrealsolutions.com> To:
"Harry Jede" <walk2sun at arcor.de> Cc: samba at lists.samba.org
Sent: Monday, July 6, 2009 10:05:14 AM GMT -05:00 US/Canada Eastern
Subject: Re: [Samba] Ubuntu Jaunty samba 3.3.2 print$ no write rights even
though I do; -)

Well, I did read the fine documentation and the documentation for this current
situation it was no help. The reason I am using the registry for the smb.conf is
memory savings, instance changes of smb.conf going into effect, and maybe future
clustering. Also, I will state if using the samba registry method is not the
proper way of doing things then why would the Samba developers add this feature
into Samba? ;-) The reason I set the share with the current rights, is to
troubleshoot the problem and prove that my file rights were correct. When I
setup the print$ share "the proper way" it is still read-only even
though I had writelist in effect. I currently have 1200 pc connect to a
samba-ldap servers with the proper setup with no problems. I will investigate
the app armor settings

Thanks 
-Glenn 

----- Original Message ----- 
From: "Harry Jede" <walk2sun at arcor.de> To: samba at
lists.samba.org Sent: Friday, July 3, 2009 3:22:19 PM GMT -05:00 US/Canada
Eastern
Subject: Re: [Samba] Ubuntu Jaunty samba 3.3.2 print$ no write rights even
though I do; -)

On Thursday, 2. Juli 2009 wrote Glenn T. Arnold: 

I just made my print$ share settings to match my print drivers share 
which should work same This is what you believe. 

and I still cannot create folders or files on 
the print$ share, but I can all day on the print drivers share. Would 
someone explain why this is happening? Here is my share settings. 

[HKEY_LOCAL_MACHINE\SOFTWARE\Samba\smbconf\print$] 
"path"="/var/lib/samba/printers" 
"comment"="Printer Drivers" 
"read only"="no" 


[HKEY_LOCAL_MACHINE\SOFTWARE\Samba\smbconf\printer drivers] 
"path"="/var/lib/samba/printers" 
"read only"="no" Why are you doing this? 

I think you should reread the excellent Samba docu again. 

Thanks 
-Glenn 

----- Original Message ----- 
From: "Glenn T. Arnold" <garnold at unrealsolutions.com> To:
"samba" <samba at lists.samba.org> Sent: Thursday, July 2, 2009
3:29:29 PM GMT -05:00 US/Canada Eastern
Subject: Re: [Samba] Ubuntu Jaunty samba 3.3.2 print$ no write rights 
even though I do;-) 

Harry, 

You did give me an idea though. For grins I just set rights to 0777 
even on the extended acls and I still get access denied when trying 
to upload print drivers. Here is the updated rights on 
/var/lib/samba/printers. You make your own changes. That's really fine. 
-- 
To unsubscribe from this list go to the following URL and read the 
instructions: https://lists.samba.org/mailman/options/samba