David replied:
If your Windows clients are Win2000 or later, you don't have to use LPD at
all -- Microsoft actually bought a clue and put IPP support into Windows
natively. When you define the printer on the Windows client, select
Internet
Printing, and when prompted for the URI for the printer
I am having problems with printing from a Windows desktop to the printer
thru Linux/CUPS. When I define the printer in Windows it comes back with a
message that the printer
is not spelled correctly or is not found.
Searching thru the Marist Listserve Archive I see that CUPS by default does
I've never heard of cups-lpd.
It's a little shim that translates LPD and LPDng job submission requests to
IPP, allowing submitting jobs to a CUPS implementation from hosts where you
can only use LPR.
The SuSE CUPS RPM includes the executable, but you have to manually edit
/etc/services and
List,
I am working with SAMBA/CUPS for printing on SLES10 SP2 for the first time.
I have CUPS enabled and can print from the Linux guest to the printer as
LPD or IPP.
For now all I want to do is simple printing from Linux to the Printer which
is working and printing from Windows desktop to the
On 10/10/2008 at 3:48 PM, in message
[EMAIL PROTECTED], Terry
Spaulding [EMAIL PROTECTED] wrote:
-snip-
I am having problems with printing from a Windows desktop to the printer
thru Linux/CUPS. When I define the printer in Windows it comes back with a
message that the printer
is not spelled
