This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(131.20000000000002, 97%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJX%3C/text%3E%3C/svg%3E)
I installed a ricoh network printer in Print Server (Windows Server 2019) using "Microsoft IPP Class Driver".
When print a pdf from cups, the job send to queue successfully, but jammed.
When checking the network traffic, I notice that Windows Print Server is continuously sending [Get-Printer-Attributes] IPP Request, which will not happen when printing a test page. By the way, cups client only send [Get-Printer-Attributes] IPP Request to Windows Print Server twice after [Print-Job ] IPP Request.
In the follow image, 10.167.152.25 is printer's IP and 10.167.152.161 is Windows Print Server's.
IMO, Windows Print Server should not send request to printer with no limit, and should show error info clearly.
And any idea to resolve the problem?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(96, 76%, 19%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDK%3C/text%3E%3C/svg%3E)
"Microsoft IPP Class Driver" uses IPP 2.0. Unfortunately, the IIS based IPP print server provided with Windows Server (even the very latest version 2022) still uses IPP 1.0 (which was never ratified as an IPP standard and was considered experimental in 1999).
Even with Win11 clients, I don't think there is any proper way to use "Microsoft IPP Class Driver" based print queues on Windows Server, let alone with a CUPS client.
Not sure if or when Microsoft will provide an IPP 2.0 or later print server with Windows Server
Have you tried other file type ? And can you see the request was received in another side? I want to confim it is a network issue or related to spooler service
The IPP class driver is meant for home printing for direct queues. You can't connect to a shared queue yet which uses the IPP class driver even with Windows clients
Microsoft has just announced Windows Protected Print Mode (WPP) which is new design that represents one of the largest changes to the Windows Print stack in more than 20 years. Both Windows Server and Windows client use the inbox Microsoft IPP class driver.
As it uses RPC between Windows client and server, it won't help with a CUPS client.