[cups] Using CUPS client with Windows Print Server

Thu Jul 6 14:23:28 PDT 2017

As a rule users not are logging in and printing.  The app is creating the report(s) and printing using a script.  It's my understanding that the script is prepending the appropriate HP PCL to the file before printing.

Are you familiar with the lpadmin "-i interface" option?

I have some printers using "-i pcl.sh", where pcl.sh contains:

cat pcl.sh
#! /bin/bash
#  created 3/20/2017
# Command line arguments
job="$1"
user="$2"
title="$3"
numcopies="$4"
options="$5"
filename="$6"

# prefix output with HPJCL reset command
echo "^[&k2G"
cat "$filename"

If you wanted to roll your own I think you could parse "options" and chose a prefix.

Getting a "driver" that supports the options/printer should work but I have researched that option.

Are you using printers that support HP PCL?

Glen

-----Original Message-----
From: cups [mailto:cups-bounces at cups.org] On Behalf Of Prentice Bisbal
Sent: Thursday, July 06, 2017 8:52 AM
To: cups at cups.org
Subject: Re: [cups] Using CUPS client with Windows Print Server

Glen,

I am currently using the Windows print server over LPD  in a similar, 
but very unmangeable way. IPP is more modern protocol, and without 
knowing all the differences, I assume IPP is a "better" protocol (why 
else would it have been created?).

In your environment, can users specify different options from the 
command-line, like two-sided, landscape, etc? That's one of the issues 
we're having here, which is why I'd like to switch to IPP.

Prentice

On 07/05/2017 06:19 PM, Glen Gunselman wrote:
> I do not know how wise or unwise this may be but I am having luck using Windows print servers using LPD.
>
> I defined the printers to Oracle Linux 6.9 using the following syntax:
>
> lpadmin -p <local printer name> -v lpd://<domain name of Windows print server>/<Windows shared printer name>
>
> We just moved the application from Solaris 10 servers to Oracle Linux 6.9 servers about 2 months ago and I wanted to keep the application changes to a minimum.  We do not do a lot of printing but this is working well for us.
>
> HTH,
> Glen
>
>
> -----Original Message-----
> From: cups [mailto:cups-bounces at cups.org] On Behalf Of Prentice Bisbal
> Sent: Wednesday, June 28, 2017 3:55 PM
> To: cups at cups.org
> Subject: [cups] Using CUPS client with Windows Print Server
>
> Hi,
>
> I've setup CUPS servers and clients in the past. On the clients, I'd
> create a client.conf file with a single line: the ServerName directive
> which specified the name of the CUPS server.
>
> I'm now in an environment where we have a lot of Linux servers and
> workstations, but our main print server is a Windows Print Server
> running IIS/8.5. Our existing Linux systems all have their own CUPS
> server setup which duplicates the printers setup on the Windows Print
> Server. This is a lot of duplicate effort.
>
> I'd prefer to just use the Windows Print Server, since  it supports IPP,
> which I've asked the Windows Admins to enable. That way, someone else
> can manage the printers for me. ;)
>
> After having IPP enabled on the printer server, I created a client.conf
> file with the appropriate ServerName setting. After doing this 'lpstat
> -a' just hangs. An inspection of  the network traffic between the client
> and server shows that the server keeps informing the client that the
> object has moved:
>
>> Content-Type: text/html; charset=UTF-8
>> Location: http://print-srv/printers/
>> Server: Microsoft-IIS/8.5
>> Date: Wed, 28 Jun 2017 20:43:08 GMT
>> Content-Length: 149
>>
>> <head><title>Document Moved</title></head>
>> <body><h1>Object Moved</h1>This document may be found <a
>> HREF="http://print-srv/printers/">here</a></body>
>> 16:43:08.839665 IP pbisbal-lt-c7.pppl.gov.39246 >
>> print-srv1.pppl.gov.ipp: Flags [P.], seq 115927:116126, ack 47180, win
>> 65392, length 199
>> E..... at .@...
>> ....}.1.N.wQ....A.EP..p....POST / HTTP/1.1
>> Content-Length: 635
>> Content-Type: application/ipp
>> Host: print-srv1.pppl.gov:631
>> User-Agent: CUPS/1.6.3 (Linux 3.10.0-514.10.2.el7.x86_64; x86_64) IPP/2.0
>> Expect: 100-continue
> It appears that the client is trying to access the printer at the wrong
> path. Is there any way to get a CUPS client to work with Windows Print
> Server/IIS?
>
> Thanks,
> Prentice
> _______________________________________________
> cups mailing list
> cups at cups.org
> https://lists.cups.org/mailman/listinfo/cups
> _______________________________________________
> cups mailing list
> cups at cups.org
> https://lists.cups.org/mailman/listinfo/cups

_______________________________________________
cups mailing list
cups at cups.org
https://lists.cups.org/mailman/listinfo/cups