Skip to main content

For the life of me I simply cannot get our Windows Virtual Print queues with Papercut working on MacOS (currently for us 15.6.1).

I get the dreaded ‘unable to connect to printer’ error.  and then its just stuck waiting.

 

Here is what I’m doing.

  1. I set up the printer locally using the advanced tab and add it as smb://print.domain.local/printer-queuename
  2. I select the universal “Mac Printer” driver I downloaded from Fuji Xerox site (currently v 2.6). 
  3. I do a test print. It works. But only once. It never works again. If I now add a second printer queue using the same method it doesn’t work. if I then go and delete the initial printer I added and re-add the steps I cannot print again that also doesn’t work.

 

I’ve also added the following script in the hopes that kerberos will play nice. No joy.

lpstat -p | awk '{print $2}' | while read printer; do
    echo "Setting Kerberos on ${printer}"
    lpadmin -p "${printer}" -o auth-info-required=negotiate
done

 

 

Has anyone else experienced this?

 

I am at a complete loss on how to proceed and it’s going to become a huge pinpoint if I roll out anymore Macs. Who would have thought printers would be the end of me.

 

Our orginisation also uses Papercut, however after “print nightmare” we connect to the follow me printer using LPD. LPD will pass the system username and doesn’t require a password (avoiding keychain issues) Papercut will associate the job with the correct user (for job release or monitoring), assuming your local mac username matches the network one. That being said, I haven’t looked at SMB printing recently.

We have it setup and working using Papercut print deploy and Virtual Queues, using the Papercut LDP service running on our Print Server.

Printers are setup as follows
Add printer > IP

Address: FQDN of print server
Protocol: Line Print Deamon - LDP
Queue: Share name on print server (Doesnt like spaces)
Name: Name of the printer share
Location: Whatever you want
Driver: Use offical Driver for the model of printer that you used to create the virtual queue

Then use the Print Deploy cloner tool to pull the printers into you server.

Thanks for the suggestions guys. 

I had a chat to paper cut support and they confirmed that smb is indeed legacy and after print nightmare you can forget about it. 

One of the suggestions made was to use the paper cut mobility print service. I’m going to give that a crack until we can procure print deploy licenses in the future. 

We are using Papercut MF. The clients are connecting using the PaperCut-Airprint driver. Our chrome book clients are the ones using the mobility print service.

Terms & ConditionsCookie settings