Hi guys, I am at a loss with this feature of samba in that it is soo hit or miss if the client drivers will upload or not depending on samba version used. Can someone confirm that this feature does indeed work in the latest samba release? i have tried many setups be it ldap or tdbsam, made sure all more groupmappings are correct, folders and permissions are correct, etc, Yet when i go to upload the printer driver the progress window appears to be doing something, the logs show me writing to the print$ share and when it gets to the end i get a nice message stating access denied... To confirm that its not a permission on the filesystem it self if i chmod 000 the path of the print$ when i try and upload the driver it wont even attempt to upload, windows will simply state that the operation is not possible. I am using the root account to upload the drivers, i make sure that im in the domain admins group(pdbedit shows primary group SID-512), i have tried this with enable privs on and off with the root account being a part of the printer manage privs all of which i have no success! What makes this even more concerning is that at some sites with previous versions of samba i was able to upload the printer drivers with no drama what so ever however after upgrading to the latest version when i goto upload a new driver or add a printer to the existing network to upload a new driver the same problem occurs above. I have tried many distros and followed the examples on samba.org, read the instructions, the tips, the trix, everything.... This feature has worked for me in the past and funny enough at one stage the drivers would only upload if i was using winxp to do the uploading on win2k networks. Now it would seem that regardless of what i am doing this feature is broken, unless someone else from a fresh install can shed some light on this. Distros used : gentoo, debian, freebsd Thankyou for time, Kind Regards, Chris Anders Network Engineer Anders Networks Mobile - 0421 580 017 Email - chris@anders.net.au Web - http://www.anders.net.au --- This message contains confidential information and is intended only f or the individual named. If you are not the named addressee you s hould not disseminate, distribute or copy this e-mail. Please notify t he sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission ca n not be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. If verification is required please request a hard-copy version.
Hi guys, As a test i built a fresh freebsd system, downloaded samba 3.0.10 followed the instructions as per the site, and not to my amazement everything worked fine and the printer drivers installed without a hitch. I then ran a make uninstall and downloaded the latest stable version of samba 3.0.22 follow the instruction as per the site, and not to my amazement uploading printer drivers failed even tho you can see the files being created in the path defined under print$ the only main diference i can see is that i can specifically define printer admin = root in version 3.0.10 while in 3.0.22 i have nothing but enable privs to work with and domain admins group, is there something else i am missing ? It would seem samba 3.0.22 obviously believes root does not have the permissions to update what is needed in the printers.tdb files for this to work..?? Both setups are using VERY basic smb.confs (the default smb.conf that comes with samba but added the [print$] share) Kind Regards, Chris Anders Network Engineer Anders Networks Mobile - 0421 580 017 Email - chris@anders.net.au Web - http://www.anders.net.au --- This message contains confidential information and is intended only f or the individual named. If you are not the named addressee you s hould not disseminate, distribute or copy this e-mail. Please notify t he sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission ca n not be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. On 04/04/2006, at 9:24 AM, Chris Anders wrote:> Hi guys, > > I am at a loss with this feature of samba in that it is soo hit or > miss if the client drivers will upload or not depending on samba > version used. > > Can someone confirm that this feature does indeed work in the > latest samba release? > > i have tried many setups be it ldap or tdbsam, made sure all more > groupmappings are correct, folders and permissions are correct, etc, > Yet when i go to upload the printer driver the progress window > appears to be doing something, the logs show me writing to the print > $ share and when it gets to the end i get a nice message stating > access denied... > > To confirm that its not a permission on the filesystem it self if i > chmod 000 the path of the print$ when i try and upload the driver > it wont even attempt to upload, windows will simply state that the > operation is not possible. > > I am using the root account to upload the drivers, i make sure that > im in the domain admins group(pdbedit shows primary group SID-512), > i have tried this with enable privs on and off with the root > account being a part of the printer manage privs all of which i > have no success! > > What makes this even more concerning is that at some sites with > previous versions of samba i was able to upload the printer drivers > with no drama what so ever however after upgrading to the latest > version when i goto upload a new driver or add a printer to the > existing network to upload a new driver the same problem occurs above. > > I have tried many distros and followed the examples on samba.org, > read the instructions, the tips, the trix, everything.... This > feature has worked for me in the past and funny enough at one stage > the drivers would only upload if i was using winxp to do the > uploading on win2k networks. Now it would seem that regardless of > what i am doing this feature is broken, unless someone else from a > fresh install can shed some light on this. > > Distros used : gentoo, debian, freebsd > > Thankyou for time, > > > > Kind Regards, > > > Chris Anders > Network Engineer > > Anders Networks > Mobile - 0421 580 017 > Email - chris@anders.net.au > Web - http://www.anders.net.au > > --- > This message contains confidential information and is intended only > f or the individual named. If you are not the named addressee you s > hould not disseminate, distribute or copy this e-mail. Please > notify t he sender immediately by e-mail if you have received this > e-mail by mistake and delete this e-mail from your system. E-mail > transmission ca n not be guaranteed to be secure or error-free as > information could be intercepted, corrupted, lost, destroyed, > arrive late or incomplete, or contain viruses. The sender therefore > does not accept liability for any errors or omissions in the > contents of this message, which arise as a result of e-mail > transmission. If verification is required please request a hard- > copy version. > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/listinfo/samba
Gerald (Jerry) Carter
2006-Apr-14 13:19 UTC
[Samba] uploading client printer drivers broken ?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Chris Anders wrote:> Hi guys, > > I am at a loss with this feature of samba in that it is soo hit or miss > if the client drivers will upload or not depending on samba version used. > > Can someone confirm that this feature does indeed work in the latest > samba release?It's never hit and miss according to my tests. There have been any regressions in this code that I'm aware of in a really long time (couple of years).> To confirm that its not a permission on the filesystem it self if i > chmod 000 the path of the print$ when i try and upload the driver it > wont even attempt to upload, windows will simply state that the > operation is not possible.chmod 000 removes all permissions. Are you sure this is what you did? If so, you probably meant to do chmod 777. cheers, jerry ====================================================================I live in a Reply-to-All world. ----------------------- Samba ------- http://www.samba.org Centeris ----------- http://www.centeris.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEP6IHIR7qMdg1EfYRAlvvAJ9Xpl3p6WZPNFuP1+JKPWZBQuXCwACaAuCV FiN0IuMEFj+4YlmnJJT+HC0=liAa -----END PGP SIGNATURE-----