PaperCut Hive - Desktops cannot print

[Edu-IT]

Has anyone come across this error before? I think this is what is preventing clients from connecting to the printers.

 

2025/08/11 14:07:45 pc-queue-handler.exe: STDERR|ERROR: Deployment failed: execute deployment: print client not ready to print: send request: Get http://localhost:9265/status: dial tcp [::1]:9265: connectex: No connection could be made because the target machine actively refused it. {"src":"deploy.go:152"

[Steve21]

Not specific to Papercut but most “actively refused” errors are normally firewall/port related

 

have you deployed all the settings for it?

 

steve

[Edu-IT]

It looks as though all the required firewall rules are in place as it creates them during the installation.

[Scifigirl]

Have you linked the printers to the users?

 

i don't think it works without the agent being installed by the user part (well we couldn't get it to) requires admin rights to install

[Edu-IT]

Thank you. That's the part that I realised last night, each user has to install the agent, to get the authentication token within their UserData.

Wasn't immediately clear.

 

Just noticing if a computer is sat idle, it seems to lose the connection after a while. Do the copiers need to stay awake 24x7 as I think they go to sleep currently.

[Scifigirl]

Ours don't - however it has been known to lose connection if a computer went to sleep/hibernate - reboots usually solve it.

 

Be careful of any profile config settings you have, unless your devices are one to one.  deleting profiles deletes the tokens so they have to go through the rigmarole of installing again

[Ratcliffepg]

If your devices are managed via Intune the process is slightly easier, if you deploy the add on "Desktop App deployment with Microsoft Intune", user then simply click on start printing via the email invite.

[jmak]

Do you have any "super -nodes" configured? That helped general stability a bit on our installation.

[krev]

Having the same issue here with a lot of devices, we have a super node configured. For end users, when printing it shows that either the handle is invalid, and crashes the app they are printing from, or the print queue shows as offline. There is some success with manually starting the pc-print-client executable and restarting the device.

[Scifigirl]

They do say, its best with 3 to 4 supernodes.  We also demote all other devices from being nodes as we were finding that the nodes that the print jobs were being held on were laptops and things that don't stay on - there for print jobs were being "lost" or delayed by hours before being replicated and printed.  Yes were are almost back to having a "print server"... almost negates the need.  Also not having the ability to delete nodes is quite annoying - especially if they are personal machines of staff who left

 

This stabilized our network a lot and now we don't lose things and can trouble shoot a lot easier.

Edited August 19, 2025 by Scifigirl
extra moan