I'm having a bit of trouble getting a Samba printer set up.-- So you have installed the ppd-file found on the driver cd.
What I have is a postscript capable HP laserjet. It actually has IPP/HTTP and stuff on it. I need queueing to work, so my clients can't print to it directly, so what I want to do is:
Get the printer set up on a central CUPs server: done. Printing quality is perfect from Unix machines. Thank you postscript!
Have samba print to that printer as well, this, I have working, but it's not pretty. The quality is horrible, and im not sure why. Things are grainy, blocky, etc. This is printing from a Windows computer (with teh HP laserJet PS drivers installed). Samba is messing up my image quality! Not sure what is causing that.
Why do you not use the "cupsaddsmb" command to install the Windows PostScript driver which come from cups? If you only use the PostScript driver with your Windows clients, you are finished.
I also can't seem to get the Add Printer Drivers wizard to work right. I followed the instructions in the 3.0 howto as best as I could. My samba "admin" user, is named "samba", he has a uid 0. It's stored in LDAP. It works for joining computers to the domain.
What security style do you use in Samba?
I added "samba" to printer admin, and when I try to loginto a Windows computer, as this user, and add a driver, I get: Access Denied.
I'm not sure what I'm being denied access too! This user has uid 0.
What is written in the samba log files when you try to access the print$-share?
There should be a line in the file log.your-pc-name which looks like
"your-pcname (your ip address) connect to service print$ initially as user samba (uid=0, gid=your-group-id) (pid xyz)"
If this line is missing, your are not recognized as print admin by samba.
After setting all this up, can I expect queue's to be consistant? I need
to see, in the Windows queue, unix jobs submitted directly to cups. On
the cup's queue, I'd like to see window's jobs. Also, can samba be made
to spool to cups AS it's receiving from the client? We regularly print
out 900 page jobs, which take 30 pages to print from the client to the
server. If the client has to sit there and spool all 900 pages before
the job can even start, we've doubled our print time! As of now, Windows
will start printing INSTATLY upon receiving data from the client, this
may be more like "buffering" than "spooling".
Thanks for the prompt assistance.
If you access the cups spool queues with samba, you will see all print jobs (the ones from windows and those from Unix/Linux)
I think (not yet tested) that the printing starts after cups has received the complete print job from samba.
Carsten
-- Carsten Buechner EDAG-Wolfsburg | Phone: +49-05361-799181 Schweriner Str. 4 | FAX: +49-05361-799134 38444 Wolfsburg | eMail: [EMAIL PROTECTED]
-- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
