[cups] Using CUPS client with Windows Print Server

Thu Jul 6 08:37:04 PDT 2017

Hello,

We've been experimenting with using a "print server" Mac that connects to
our shared Windows print queues via smb printing and then "shares" these
printers so other macs on the network can use the Mac OS native method to
connect to the Windows printers. The Mac that is sharing the Windows
printers is also in our MS AD domain. Access to the printers is restricted
to domain users. A normal Mac just adds the printer using the control panel
with the "default" option to browse for shared printers. On first print,
the user is prompted for their MS AD username and password. We are also
using DNS-SD or wide-area bonjour so the Mac clients find the Mac print
server printers even across VLAN boundaries.

I do have a question: How does CUPS handle the case where the client Mac is
using a different driver/PPD than the Mac print server? Does it use what's
installed on the client or server?

Thanks,

James Ketterer

Director of IT Infrastructure
DePauw University, 602 S. College, Julian Math and Science

Room 127, Greencastle IN 46135
JamesKetterer at depauw.edu  | www.depauw.edu

On Thu, Jul 6, 2017 at 9:52 AM, Prentice Bisbal <pbisbal at pppl.gov> wrote:

> 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
>