Cannot print to network printer when Everyone or Authenticated Users group removed

Matthew Armstrong 21 Reputation points

I have a small network printer setup on our Server 2016 print server. I've got it locked down so that only a specific group is able to print to it. To ensure that no one else can print to it, I've removed the Everyone group, however with this group gone printing to this printer is no longer possible. Sending a test print from my workstation or even from the print server fails. The right drivers are installed and the printer gets installed on my workstation successfully. I can view all of the printer details and properties.

When looking in event viewer, I'm seeing

The document Print Document, owned by [redacted], failed to print on printer [redacted]. Try to print the document again, or restart the print spooler.
Data type: RAW. Size of the spool file in bytes: 243815. Number of bytes printed: 243815. Total number of pages in the document: 1. Number of pages printed: 0. Client computer: [Redacted]. Win32 error code returned by the print processor: 1726. The remote procedure call failed.

I've got myself added to the group which is allowed to print so I can test before deploying the printer. As soon as the Everyone or Authenticated Users groups are put back, the printer works just fine.

Workstation is up to date and the printer is installed correctly.

Any help is greatly appreciated.

Windows Server Printing
Windows Server Printing
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Printing: Printer centralized deployment and management, scan and fax resources management, and document services
497 questions
No comments
{count} votes

Accepted answer
  1. Anonymous

    Hi, I’ve noted that error “Win32 error code returned by the print processor: 1726. The remote procedure call failed." Can I know how did you set up the printers on the print server? You may run gpresult /h C:\report.html to check what GPO policy is applied on the client, and check the detailed GPO information on DC. Also, please provide the model of the printer. For now, please try to perform these steps for restart the print spooler. 1. At the bottom left of the screen and right click or tap and hold the Start button and left click on Run from the menu that appears. ![91563-image.png][1] 2. Type services.msc in the Open box then click or tap OK (highlighted below).![91564-image.png][2] 3. Scroll down the list and click or tap on Print Spooler. ![91581-image.png][3] 4. Click or tap on Restart the service.![91582-image.png][4] 5. Windows will attempt to start the service.![91583-image.png][5] 6. Once the Print Spooler status is Running (example below).![91518-image.png][6]The Print Spooler service is started. If the answer is helpful, please click "Accept Answer" and upvote it. Best Regards, [1]: /api/attachments/91563-image.png?platform=QnA [2]: /api/attachments/91564-image.png?platform=QnA [3]: /api/attachments/91581-image.png?platform=QnA [4]: /api/attachments/91582-image.png?platform=QnA [5]: /api/attachments/91583-image.png?platform=QnA [6]: /api/attachments/91518-image.png?platform=QnA

    No comments

1 additional answer

Sort by: Most helpful
  1. Matthew Armstrong 21 Reputation points

    Thank you, a restart of the print spooler resolved the issue.