Re: [Samba] 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" To: "Samba" 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" To: "Glenn T. Arnold" Cc: "Samba" 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 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" To: samba@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" To: "Harry Jede" Cc: samba@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" To: samba@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_LO
Re: [Samba] Ubuntu Jaunty samba 3.3.2 print$ no write rights even though I do; -)
Jeremy, I do not think you got my log files, because I went through the log and I did not see the error you are referencing. When I went through the logs I did see references to print$ in the logs. What is a the proper way to post a log? I got bounced by the Samba List server when I paste the information in a post. I sent the log gziped did not get a bounce message, but I am not sure you got the log files. The file that I sent gzip was named print$level10.tar.gz Here is what I found under the two log files for print$ [2009/07/16 16:33:14, 2] param/loadparm.c:do_section(7498) Processing section "[print$]" [2009/07/16 16:33:14, 8] param/loadparm.c:add_a_service(5830) add_a_service: Creating snum = 1 for print$ [2009/07/16 16:33:14, 10] param/loadparm.c:hash_a_service(5877) hash_a_service: hashing index 1 for service name print$ -Glenn - Original Message - From: "Jeremy Allison" To: "Glenn T. Arnold" Cc: "Jeremy Allison" , samba@lists.samba.org Sent: Thursday, July 16, 2009 6:01:44 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 Thu, Jul 16, 2009 at 05:31:21PM -0400, Glenn T. Arnold wrote: > Here is the level 10 log files I sent the first one as attachments which look > like did not make it through. I don't see any attempts to open the print$ share in these logs. I do see an error : netlogon_creds_server_check: challenge : 14D0450551344C93 calculated: BAB7D8066C1D3129 netlogon_creds_server_check: credentials check failed. _netr_ServerAuthenticate3: netlogon_creds_server_check failed. Rejecting auth request from client WIN7 machine account WIN7$ Is this a Win7 machine ? 3.3.2 doesn't have the fixes for Win7 netlogon credentials in it (hardly suprising as Win7 wasn't even a twinkle in Microsoft's release schedule when 3.3.2 was shipped :-). Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Ubuntu Jaunty samba 3.3.2 print$ no write rights even though I do; -)
On Thu, Jul 16, 2009 at 05:31:21PM -0400, Glenn T. Arnold wrote: > Here is the level 10 log files I sent the first one as attachments which look > like did not make it through. I don't see any attempts to open the print$ share in these logs. I do see an error : netlogon_creds_server_check: challenge : 14D0450551344C93 calculated: BAB7D8066C1D3129 netlogon_creds_server_check: credentials check failed. _netr_ServerAuthenticate3: netlogon_creds_server_check failed. Rejecting auth request from client WIN7 machine account WIN7$ Is this a Win7 machine ? 3.3.2 doesn't have the fixes for Win7 netlogon credentials in it (hardly suprising as Win7 wasn't even a twinkle in Microsoft's release schedule when 3.3.2 was shipped :-). Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Ubuntu Jaunty samba 3.3.2 print$ no write rights even though I do; -)
On Thu, Jul 16, 2009 at 03:11:00PM -0400, 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: Please post a debug level 10 log of the client trying to write. This should make things clearer. Jeremy -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
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" To: "Glenn T. Arnold" Cc: "Samba" 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 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" To: samba@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" To: "Harry Jede" Cc: samba@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" To: samba@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" To: "samba" 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
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 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" To: samba@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" To: "Harry Jede" Cc: samba@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" To: samba@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" To: "samba" 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
Re: [Samba] Ubuntu Jaunty samba 3.3.2 print$ no write rights even though I do; -)
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" To: samba@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" To: "Harry Jede" Cc: samba@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" To: samba@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" > To: "samba" > 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. -- Gruss Harry Jede -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
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" To: "Harry Jede" Cc: samba@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" To: samba@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" > To: "samba" > 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. -- Gruss Harry Jede -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
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" To: samba@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" > To: "samba" > 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. -- Gruss Harry Jede -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Ubuntu Jaunty samba 3.3.2 print$ no write rights even though I do; -)
On Friday, 3. Juli 2009 wrote Ray Anderson: > Glenn T. Arnold wrote: > > 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. > > Harry, > > Check your apparmor setttings: > > /etc/apparmor.d/abstractions/samba I am using GNU/Linux. There is no apllication called "apparmor". BTW I donn't have any problems with samba, Glenn has the problems. -- Harry Jede -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
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" > To: "samba" > 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. -- Gruss Harry Jede -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: Re: [Samba] Ubuntu Jaunty samba 3.3.2 print$ no write rights even though I do;-)
Glenn T. Arnold wrote: 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. Harry, Check your apparmor setttings: /etc/apparmor.d/abstractions/samba Mine looks like this: abstractions/samba:2: /etc/samba/smb.conf r, abstractions/samba:3: /usr/share/samba/*.dat mr, abstractions/samba:4: /var/lib/samba/**.tdb mrw, abstractions/samba:5: /var/log/samba/cores/* w, abstractions/samba:6: /var/log/samba/log.* w, abstractions/samba:7: /var/run/samba/*.tdb mrw, Seems you'd need to add /var/lib/samba/printers/* mrw or similar. Ray -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Ubuntu Jaunty samba 3.3.2 print$ no write rights even though I do;-)
I just made my print$ share settings to match my print drivers share which should work same 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" Thanks -Glenn - Original Message - From: "Glenn T. Arnold" To: "samba" 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. r...@server01:/var/lib/samba# getfacl printers/* # file: printers/COLOR # owner: root # group: Domain\040Admins user::rwx group::rwx group:Domain\040Admins:rwx mask::rwx other::rwx default:user::rwx default:group::rwx default:group:Domain\040Admins:rwx default:mask::rwx default:other::rwx # file: printers/IA64 # owner: root # group: Domain\040Admins user::rwx group::rwx group:Domain\040Admins:rwx mask::rwx other::rwx default:user::rwx default:group::rwx default:group:Domain\040Admins:rwx default:mask::rwx default:other::rwx # file: printers/showtrueconfig # owner: root # group: root user::rwx group::rwx group:Domain\040Admins:rwx mask::rwx other::rwx # file: printers/W32ALPHA # owner: root # group: Domain\040Admins user::rwx group::rwx group:Domain\040Admins:rwx mask::rwx other::rwx default:user::rwx default:group::rwx default:group:Domain\040Admins:rwx default:mask::rwx default:other::rwx # file: printers/W32MIPS # owner: root # group: Domain\040Admins user::rwx group::rwx group:Domain\040Admins:rwx mask::rwx other::rwx default:user::rwx default:group::rwx default:group:Domain\040Admins:rwx default:mask::rwx default:other::rwx # file: printers/W32PPC # owner: root # group: Domain\040Admins user::rwx group::rwx group:Domain\040Admins:rwx mask::rwx other::rwx default:user::rwx default:group::rwx default:group:Domain\040Admins:rwx default:mask::rwx default:other::rwx # file: printers/W32X86 # owner: root # group: Domain\040Admins user::rwx group::rwx group:Domain\040Admins:rwx mask::rwx other::rwx default:user::rwx default:group::rwx default:group:Domain\040Admins:rwx default:mask::rwx default:other::rwx # file: printers/WIN40 # owner: root # group: Domain\040Admins user::rwx group::rwx group:Domain\040Admins:rwx mask::rwx other::rwx default:user::rwx default:group::rwx default:group:Domain\040Admins:rwx default:mask::rwx default:other::rwx # file: printers/x64 # owner: root # group: Domain\040Admins user::rwx group::rwx group:Domain\040Admins:rwx mask::rwx other::rwx default:user::rwx default:group::rwx default:group:Domain\040Admins:rwx default:mask::rwx default:other::rwx r...@server01:/var/lib/samba# -Glenn - Original Message - From: "Harry Jede" < walk2...@arcor.de > To: samba@lists.samba.org Sent: Thursday , July 2, 2009 2:53:41 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 Donnerstag, 2. Juli 2009 wrote Glenn T. Arnold: > Here is the rights on the /var/lib/samba/printers directory > > r...@server01:/var/lib/samba# getfacl printers -R > # file: printers > # owner: root > # group: Domain\040Admins > user::rwx > group::r-x # grant Domain\040Admins write access group::rwx > group:Domain\040Admins:rwx > mask::rwx > other::r-x > default:user::rwx > default:group::r-x > default:group:Domain\040Admins:rwx > default:mask::rwx > default:other::r-x -- Harry Jede -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -Glenn ----- Original Message ----- From: "Glenn T. Arnold" To: "samba" Sent: Thursday, July 2, 2009 2:49:27 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 found in the samba log for my machine the following error: [2009/07/02 13:13:34, 0] groupdb/mapping.c:pdb_create_builtin_alias(802) pdb_create_builtin_alias: Could not add group mapping entry for alias 545 (NT_STATUS_GROUP_EXISTS) Any input on this would be appreciated! I researching this error now. -Glenn ----- Original Message - From: &
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. r...@server01:/var/lib/samba# getfacl printers/* # file: printers/COLOR # owner: root # group: Domain\040Admins user::rwx group::rwx group:Domain\040Admins:rwx mask::rwx other::rwx default:user::rwx default:group::rwx default:group:Domain\040Admins:rwx default:mask::rwx default:other::rwx # file: printers/IA64 # owner: root # group: Domain\040Admins user::rwx group::rwx group:Domain\040Admins:rwx mask::rwx other::rwx default:user::rwx default:group::rwx default:group:Domain\040Admins:rwx default:mask::rwx default:other::rwx # file: printers/showtrueconfig # owner: root # group: root user::rwx group::rwx group:Domain\040Admins:rwx mask::rwx other::rwx # file: printers/W32ALPHA # owner: root # group: Domain\040Admins user::rwx group::rwx group:Domain\040Admins:rwx mask::rwx other::rwx default:user::rwx default:group::rwx default:group:Domain\040Admins:rwx default:mask::rwx default:other::rwx # file: printers/W32MIPS # owner: root # group: Domain\040Admins user::rwx group::rwx group:Domain\040Admins:rwx mask::rwx other::rwx default:user::rwx default:group::rwx default:group:Domain\040Admins:rwx default:mask::rwx default:other::rwx # file: printers/W32PPC # owner: root # group: Domain\040Admins user::rwx group::rwx group:Domain\040Admins:rwx mask::rwx other::rwx default:user::rwx default:group::rwx default:group:Domain\040Admins:rwx default:mask::rwx default:other::rwx # file: printers/W32X86 # owner: root # group: Domain\040Admins user::rwx group::rwx group:Domain\040Admins:rwx mask::rwx other::rwx default:user::rwx default:group::rwx default:group:Domain\040Admins:rwx default:mask::rwx default:other::rwx # file: printers/WIN40 # owner: root # group: Domain\040Admins user::rwx group::rwx group:Domain\040Admins:rwx mask::rwx other::rwx default:user::rwx default:group::rwx default:group:Domain\040Admins:rwx default:mask::rwx default:other::rwx # file: printers/x64 # owner: root # group: Domain\040Admins user::rwx group::rwx group:Domain\040Admins:rwx mask::rwx other::rwx default:user::rwx default:group::rwx default:group:Domain\040Admins:rwx default:mask::rwx default:other::rwx r...@server01:/var/lib/samba# -Glenn - Original Message - From: "Harry Jede" < walk2...@arcor.de > To: samba@lists.samba.org Sent: Thursday , July 2, 2009 2:53:41 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 Donnerstag, 2. Juli 2009 wrote Glenn T. Arnold: > Here is the rights on the /var/lib/samba/printers directory > > r...@server01:/var/lib/samba# getfacl printers -R > # file: printers > # owner: root > # group: Domain\040Admins > user::rwx > group::r-x # grant Domain\040Admins write access group::rwx > group:Domain\040Admins:rwx > mask::rwx > other::r-x > default:user::rwx > default:group::r-x > default:group:Domain\040Admins:rwx > default:mask::rwx > default:other::r-x -- Harry Jede -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -Glenn - Original Message - From: "Glenn T. Arnold" To: "samba" Sent: Thursday, July 2, 2009 2:49:27 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 found in the samba log for my machine the following error: [2009/07/02 13:13:34, 0] groupdb/mapping.c:pdb_create_builtin_alias(802) pdb_create_builtin_alias: Could not add group mapping entry for alias 545 (NT_STATUS_GROUP_EXISTS) Any input on this would be appreciated! I researching this error now. -Glenn - Original Message - From: "Glenn T. Arnold" To: "samba" Sent: Thursday, July 2, 2009 2:09:15 PM GMT -05:00 US/Canada Eastern Subject: [Samba] Ubuntu Jaunty samba 3.3.2 print$ no write rights even though I do;-) I am setting up a OpenLdap PDC with file and print services on Ubuntu Jaunty. Jaunty ships with samba 3.3.2. I configured samba to just use the registry back in which I think is pretty cool! What happend when I use the Add print wizard to add my Windows XP drivers I get the famous "unable to install driver access denied" message. I can ssh into the box with my user id and create files in the /var/lib/samba/printers folder with no problem. I have gave the Domain Admins and root all privileges to manage the domain see bellow. r...@server01:/var/lib/samba/printers# net rpc rights list root Enter root's password: SeMachineAccountPrivileg
Re: [Samba] Ubuntu Jaunty samba 3.3.2 print$ no write rights even though I do; -)
On Donnerstag, 2. Juli 2009 wrote Glenn T. Arnold: > Here is the rights on the /var/lib/samba/printers directory > > r...@server01:/var/lib/samba# getfacl printers -R > # file: printers > # owner: root > # group: Domain\040Admins > user::rwx > group::r-x # grant Domain\040Admins write access group::rwx > group:Domain\040Admins:rwx > mask::rwx > other::r-x > default:user::rwx > default:group::r-x > default:group:Domain\040Admins:rwx > default:mask::rwx > default:other::r-x -- Harry Jede -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Ubuntu Jaunty samba 3.3.2 print$ no write rights even though I do;-)
I found in the samba log for my machine the following error: [2009/07/02 13:13:34, 0] groupdb/mapping.c:pdb_create_builtin_alias(802) pdb_create_builtin_alias: Could not add group mapping entry for alias 545 (NT_STATUS_GROUP_EXISTS) Any input on this would be appreciated! I researching this error now. -Glenn - Original Message - From: "Glenn T. Arnold" To: "samba" Sent: Thursday, July 2, 2009 2:09:15 PM GMT -05:00 US/Canada Eastern Subject: [Samba] Ubuntu Jaunty samba 3.3.2 print$ no write rights even though I do;-) I am setting up a OpenLdap PDC with file and print services on Ubuntu Jaunty. Jaunty ships with samba 3.3.2. I configured samba to just use the registry back in which I think is pretty cool! What happend when I use the Add print wizard to add my Windows XP drivers I get the famous "unable to install driver access denied" message. I can ssh into the box with my user id and create files in the /var/lib/samba/printers folder with no problem. I have gave the Domain Admins and root all privileges to manage the domain see bellow. r...@server01:/var/lib/samba/printers# net rpc rights list root Enter root's password: SeMachineAccountPrivilege SeTakeOwnershipPrivilege SeBackupPrivilege SeRestorePrivilege SeRemoteShutdownPrivilege SePrintOperatorPrivilege SeAddUsersPrivilege SeDiskOperatorPrivilege net rpc rights list "Domain Admins" Enter root's password: SeMachineAccountPrivilege SeTakeOwnershipPrivilege SeBackupPrivilege SeRestorePrivilege SeRemoteShutdownPrivilege SePrintOperatorPrivilege SeAddUsersPrivilege SeDiskOperatorPrivilege Here is the rights on the /var/lib/samba/printers directory r...@server01:/var/lib/samba# getfacl printers -R # file: printers # owner: root # group: Domain\040Admins user::rwx group::r-x group:Domain\040Admins:rwx mask::rwx other::r-x default:user::rwx default:group::r-x default:group:Domain\040Admins:rwx default:mask::rwx default:other::r-x # file: printers/W32X86 # owner: root # group: Domain\040Admins user::rwx group::r-x group:Domain\040Admins:rwx mask::rwx other::r-x default:user::rwx default:group::r-x default:group:Domain\040Admins:rwx default:mask::rwx default:other::r-x # file: printers/W32ALPHA # owner: root # group: Domain\040Admins user::rwx group::r-x group:Domain\040Admins:rwx mask::rwx other::r-x default:user::rwx default:group::r-x default:group:Domain\040Admins:rwx default:mask::rwx default:other::r-x # file: printers/showtrueconfig # owner: root # group: root user::rw- group::r-x #effective:r-- group:Domain\040Admins:rwx #effective:rw- mask::rw- other::r-- # file: printers/W32MIPS # owner: root # group: Domain\040Admins user::rwx group::r-x group:Domain\040Admins:rwx mask::rwx other::r-x default:user::rwx default:group::r-x default:group:Domain\040Admins:rwx default:mask::rwx default:other::r-x # file: printers/x64 # owner: root # group: Domain\040Admins user::rwx group::r-x group:Domain\040Admins:rwx mask::rwx other::r-x default:user::rwx default:group::r-x default:group:Domain\040Admins:rwx default:mask::rwx default:other::r-x # file: printers/W32PPC # owner: root # group: Domain\040Admins user::rwx group::r-x group:Domain\040Admins:rwx mask::rwx other::r-x default:user::rwx default:group::r-x default:group:Domain\040Admins:rwx default:mask::rwx default:other::r-x # file: printers/IA64 # owner: root # group: Domain\040Admins user::rwx group::r-x group:Domain\040Admins:rwx mask::rwx other::r-x default:user::rwx default:group::r-x default:group:Domain\040Admins:rwx default:mask::rwx default:other::r-x # file: printers/WIN40 # owner: root # group: Domain\040Admins user::rwx group::r-x group:Domain\040Admins:rwx mask::rwx other::r-x default:user::rwx default:group::r-x default:group:Domain\040Admins:rwx default:mask::rwx default:other::r-x # file: printers/COLOR # owner: root # group: Domain\040Admins user::rwx group::r-x group:Domain\040Admins:rwx mask::rwx other::r-x default:user::rwx default:group::r-x default:group:Domain\040Admins:rwx default:mask::rwx default:other::r-x I created a second share called printer drivers to prove I have rights to write to the /var/lib/samba/printers folder from a windows xp. Which I can create and copy files and folders with no problems through the print drivers share, but when I connect to the /var/lib/samba/printers folder through print$ I get access denied. But, I can add workstations to the domain with no problems, I can change security on the printer I am trying to upload a print driver with no problems. If you run smbstatus you can see when I connect with root that it only shows read only rights here is my smbstatus ouptput . Locked files: Pid Uid DenyMode Access R/W Oplock SharePath Name Time
[Samba] Ubuntu Jaunty samba 3.3.2 print$ no write rights even though I do;-)
I am setting up a OpenLdap PDC with file and print services on Ubuntu Jaunty. Jaunty ships with samba 3.3.2. I configured samba to just use the registry back in which I think is pretty cool! What happend when I use the Add print wizard to add my Windows XP drivers I get the famous "unable to install driver access denied" message. I can ssh into the box with my user id and create files in the /var/lib/samba/printers folder with no problem. I have gave the Domain Admins and root all privileges to manage the domain see bellow. r...@server01:/var/lib/samba/printers# net rpc rights list root Enter root's password: SeMachineAccountPrivilege SeTakeOwnershipPrivilege SeBackupPrivilege SeRestorePrivilege SeRemoteShutdownPrivilege SePrintOperatorPrivilege SeAddUsersPrivilege SeDiskOperatorPrivilege net rpc rights list "Domain Admins" Enter root's password: SeMachineAccountPrivilege SeTakeOwnershipPrivilege SeBackupPrivilege SeRestorePrivilege SeRemoteShutdownPrivilege SePrintOperatorPrivilege SeAddUsersPrivilege SeDiskOperatorPrivilege Here is the rights on the /var/lib/samba/printers directory r...@server01:/var/lib/samba# getfacl printers -R # file: printers # owner: root # group: Domain\040Admins user::rwx group::r-x group:Domain\040Admins:rwx mask::rwx other::r-x default:user::rwx default:group::r-x default:group:Domain\040Admins:rwx default:mask::rwx default:other::r-x # file: printers/W32X86 # owner: root # group: Domain\040Admins user::rwx group::r-x group:Domain\040Admins:rwx mask::rwx other::r-x default:user::rwx default:group::r-x default:group:Domain\040Admins:rwx default:mask::rwx default:other::r-x # file: printers/W32ALPHA # owner: root # group: Domain\040Admins user::rwx group::r-x group:Domain\040Admins:rwx mask::rwx other::r-x default:user::rwx default:group::r-x default:group:Domain\040Admins:rwx default:mask::rwx default:other::r-x # file: printers/showtrueconfig # owner: root # group: root user::rw- group::r-x #effective:r-- group:Domain\040Admins:rwx #effective:rw- mask::rw- other::r-- # file: printers/W32MIPS # owner: root # group: Domain\040Admins user::rwx group::r-x group:Domain\040Admins:rwx mask::rwx other::r-x default:user::rwx default:group::r-x default:group:Domain\040Admins:rwx default:mask::rwx default:other::r-x # file: printers/x64 # owner: root # group: Domain\040Admins user::rwx group::r-x group:Domain\040Admins:rwx mask::rwx other::r-x default:user::rwx default:group::r-x default:group:Domain\040Admins:rwx default:mask::rwx default:other::r-x # file: printers/W32PPC # owner: root # group: Domain\040Admins user::rwx group::r-x group:Domain\040Admins:rwx mask::rwx other::r-x default:user::rwx default:group::r-x default:group:Domain\040Admins:rwx default:mask::rwx default:other::r-x # file: printers/IA64 # owner: root # group: Domain\040Admins user::rwx group::r-x group:Domain\040Admins:rwx mask::rwx other::r-x default:user::rwx default:group::r-x default:group:Domain\040Admins:rwx default:mask::rwx default:other::r-x # file: printers/WIN40 # owner: root # group: Domain\040Admins user::rwx group::r-x group:Domain\040Admins:rwx mask::rwx other::r-x default:user::rwx default:group::r-x default:group:Domain\040Admins:rwx default:mask::rwx default:other::r-x # file: printers/COLOR # owner: root # group: Domain\040Admins user::rwx group::r-x group:Domain\040Admins:rwx mask::rwx other::r-x default:user::rwx default:group::r-x default:group:Domain\040Admins:rwx default:mask::rwx default:other::r-x I created a second share called printer drivers to prove I have rights to write to the /var/lib/samba/printers folder from a windows xp. Which I can create and copy files and folders with no problems through the print drivers share, but when I connect to the /var/lib/samba/printers folder through print$ I get access denied. But, I can add workstations to the domain with no problems, I can change security on the printer I am trying to upload a print driver with no problems. If you run smbstatus you can see when I connect with root that it only shows read only rights here is my smbstatus ouptput . Locked files: Pid Uid DenyMode Access R/W Oplock SharePath Name Time -- 12885 0 DENY_NONE 0x100081 RDONLY NONE /var/lib/samba/printers . Thu Jul 2 13:13:34 2009 12885 0 DENY_NONE 0x100081 RDONLY NONE /var/lib/samba/printers . Thu Jul 2 13:13:34 2009 12471 1 DENY_NONE 0x100081 RDONLY NONE /var/lib/samba/printers . Thu Jul 2 13:06:46 2009 12471 1 DENY_NONE 0x100081 RDONLY NONE /var/lib/samba/printers . Thu Jul 2 13:06:46 2009 12471 1 DENY_NONE 0x100081 RDONLY NONE /var/lib/samba/printers . Thu Jul 2 13:35:05 2009 12471 1 DENY_NONE 0x100081 RDONLY NONE /home/gtarnold . Thu Jul 2 13:39:55 2009 Below is my smb
