The Windows IPP service bypasses the standard Windows printing process and this can cause problems with the PaperCut user client print popups (e.g. account selection or authentication popups).
The Windows IPP service runs in IIS and when it accepts jobs over HTTP it then inserts the jobs into the standard Windows printer queue. When it does this it loses some important meta-data from the print job that PaperCut uses to determine where to send the popup. (This important meta-data includes the client workstation name/IP-address and the user that printed the document).
For example, jobs that are submitted through the Windows IPP service report the following attributes:
Client/Workstation: the print server name/IP Username: the IIS username The PaperCut user client uses this meta-data (client IP and username) to determine where the job was printed from, and where to deliver the popup notification.
We recommend not using the Windows IPP service for printing when you use the user client popups.
Articles in this section
- PaperCut MF - New SSL certificate (macOS)
- New KB article template
- Xerox embedded devices - Incorrect login screen issues
- Handling hidden characters in card numbers
- Scan to multiple email destinations
- PaperCut NG/MF Security Bulletin (March 2026)
- PaperCut Hive and Pocket Compatibility Tool
- Enabling ARM64 support in PaperCut NG/MF Print Deploy
- Incorrect stapling when printing multiple copies via a Find-Me queue using HP PCL drivers
- Resetting the PaperCut Hive or Pocket app (Android & iOS)
Comments
0 comments
Please sign in to leave a comment.