[cups] Using CUPS client with Windows Print Server

Thu Jun 29 10:45:22 PDT 2017

Michael,

Thanks. That wasn't what I wanted to hear, but it was what I expected. I 
was afraid the only real solution was going to be to mirror the Windows 
print queues on a Linux based CUPS server. Thanks for the confirmation.

On 06/28/2017 08:30 PM, Michael Sweet wrote:
> Prentice,
>
> Unfortunately, Windows' support for IPP is still quite primitive and certainly does not support the CUPS extension "CUPS-Get-Printers" or "CUPS-Get-Default", both of which are required for a CUPS client to talk directly to a server.
>
> Your best solution in this case is to have one Linux server that mirrors the queues on the Windows server, and have the CUPS clients point to it.
>
>
>> On Jun 28, 2017, at 4:54 PM, Prentice Bisbal <pbisbal at pppl.gov> wrote:
>>
>> 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
> _________________________________________________________
> Michael Sweet, Senior Printing System Engineer
>
> _______________________________________________
> cups mailing list
> cups at cups.org
> https://lists.cups.org/mailman/listinfo/cups