I posted this to the newbie list and didn't receive any suggestions. 
Anyone care to take a stab at my problem?

Thanks,
Kathy

-------- Original Message --------
Subject: [newbie] cups and windows shared printer - stumped
Date: Tue, 04 Dec 2001 14:25:01 -0500
From: Kathy Montgomery <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Organization: University at Albany
To: [EMAIL PROTECTED]

I've been trying for ages (or what seems like ages) to get CUPS to print
to a Windows 2000 shared printer.  I am stumped.  I tried to use kups to
configure the printer (since people reported success with kups), but to
no avail.

The following lines appear in my /var/log/cups/error_log file when I try
to print to my default printer, an HP Laserjet 4L:

I [04/Dec/2001:14:00:34 -0500] Job 14 queued on 'hp4l' by 'root'.
I [04/Dec/2001:14:00:34 -0500] Started filter
/usr/lib/cups/filter/pstops (PID 3085) for job 14.
I [04/Dec/2001:14:00:34 -0500] Started filter
/usr/lib/cups/filter/pstoraster (PID 3086) for job 14.
I [04/Dec/2001:14:00:34 -0500] Started filter
/usr/lib/cups/filter/rastertoprinter (PID 3087) for job 14.
E [04/Dec/2001:14:00:34 -0500] PID 3087 stopped with status 1!
I [04/Dec/2001:14:00:34 -0500] Started backend /usr/lib/cups/backend/smb
(PID 3088) for job 14.
E [04/Dec/2001:14:00:34 -0500] Fatal error: Unable to load PPD file
"/etc/cups/ppd/hp4l.ppd"!

The file to which the error messages refer exists and is mode 644.  The
printer is physically attached to the Windows machine.  I have no
problem mounting a shared Windows directory on the Linux machine using
my Windows network username and password.  The command "smbclient -L
machine-name -U user" says the printer is indeed there.

I've no clue what to try next.  Any pointers?

Thanks,
Kathy

--
For God has not given us a spirit of fear, but of power and of love and
of a sound mind. - 2 Timothy 1:7
Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com

Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com

Reply via email to