[ale] Shared Samba printer, SuSE 9.0

[Dow Hurst]

The samba print queue needs to be raw since the Windows machine should send 
preprocessed printing thru the printer driver in Windows.  On the Suse desktop 
the cups backend usually takes in postscript and processes it to what the 
printer needs.  The windows printer driver does this already so the queue 
needs to be raw on the Samba printer share.  Also, Suse 9.0 has more security 
enabled on CUPs by default so Yast2 will configure it but the web interface is 
only good for monitoring.  You can modify the CUPs configuration files to 
change all this if you want.  You probably have to modify CUPS to allow 
printing from your machine.  This is something I need to deal with too!  I've 
got the book, the docs, but just haven't taken the time to do it yet.
Dow


BruceG wrote:
> I'm running SuSE 9.0 and have Samba running. I am logged on from a WIndows 
> client and can see my home directory and my printer. I can read and write 
> files to the home directory, so I know that part is working. I can also "see" 
> my shared printer.
> 
> When I go to print from my Windows client, I get no output at all! The printer 
> works fine in CUPS (I can print from OOo and other apps on the SuSE desktop) 
> - but somehow when I cam sharing it - nothing happens.
> 
> Where should I start to look to solve this? Anyone run into this problem 
> before, or is it just me?
> 
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://www.ale.org/mailman/listinfo/ale
> 

-- 
__________________________________________________________
Dow Hurst                  Office: 770-499-3428            *
Systems Support Specialist    Fax: 770-423-6744            *
1000 Chastain Rd. Bldg. 12                                 *
Chemistry Department SC428  Email:   dhurst at kennesaw.edu   *
Kennesaw State University         Dow.Hurst at mindspring.com *
Kennesaw, GA 30144                                         *
************************************************************
This message (including any attachments) contains          *
confidential information intended for a specific individual*
and purpose, and is protected by law.  If you are not the  *
intended recipient, you should delete this message and are *
hereby notified that any disclosure, copying, distribution *
of this message, or the taking of any action based on it,  *
is strictly prohibited.                                    *
************************************************************