On Wed, 2006-09-20 at 09:06 -0500, Randy Easley wrote: > __________________________________________________________________________________________________________________________ > > > On Tue, 2006-09-19 at 16:29 -0500, Randy Easley wrote: > > > I cannot print from a winXp machine to a Fedora server? Smb.conf > has > > > public = yes and guest ok = yes. On the same workgroup with no > domain. > > > I can clearly see the file shares which are also public. > > > Log files show WERR_ACCESS_DENIED over and over. > > > > > ---- > > make sure that the 'user' printing (there is a user even if it is a > 'guest' - it would be whichever user guest is being mapped to) has > write privileges to the 'spool' directory that you created in smb.conf > > see > > http://samba.org/samba/docs/man/Samba-HOWTO-Collection/CUPS-printing.html#cups-exam-simple > > in the example shown above... > > chmod 777 /var/spool/samba -R ---- I do not understand? (Ignorance) > > If you have public and guest set to yes why couldn’t ANY windows PC > print to a linux printer? Here is the error in smbd.log > > Printing/nt_printing.c:nt_printing_init(383) > > nt_printing_init: error checking published printers: > WERR_ACCESS_DENIED > > Thanks again ---- Because all of samba activities are mapped to a specific user - even those of 'public' or 'guest' are mapped to a posix (Linux in this instance) account. You can verify this by doing... testparm -sv |grep guest It should point out that even if it isn't configured in smb.conf, by default 'guest' is mapped to a 'nobody' account which by default isn't likely to have write access to your print spool directory for samba which is why access is going to be denied. I suppose you can either continue to not understand or try the suggestion that I offered or even better yet, read through the documentation in the link I provided - the official Samba How To - which allows you to understand all of this for yourself. Craig
