manamaga2512 Posted March 3, 2017 Posted March 3, 2017 Hi all, I am going out of my mind here as I have battling with this all week now. When users send a print job to our shared printer on our mac server, we get this "hold for authentication" Looking online only brings up things about keychain, all of which we have tried, to no avail. Even more confusing is why this has suddenly started happening because we didn't have this problem 3 weeks ago. Are there any Mac gurus out there who could offer some advice please? Many thanks.
TechieWils Posted March 3, 2017 Posted March 3, 2017 Do you have Papercut or some other print management software installed? If it's not that for you to click accept on the print I'm out of ideas, not a massive Mac person sorry.
bossman Posted March 3, 2017 Posted March 3, 2017 (edited) @manamaga2512 Found this: https://discussions.apple.com/thread/2306107?start=30 And this: https://www.macissues.com/2015/02/17/overcome-authentication-required-error-for-shared-printers-in-os-x/ And this: http://servalpaul.blogspot.co.uk/2015/01/mac-osx-hold-for-authentication-when.html Which leads to this: http://people.bu.edu/rbs/ThingsApple/Macintosh/Macintosh-printing.html Any Help? Edited March 3, 2017 by bossman
manamaga2512 Posted March 3, 2017 Author Posted March 3, 2017 We do use papercut but I have eliminated that as being the cause by trying to print directly to the printers IP address. No luck :-(
manamaga2512 Posted March 3, 2017 Author Posted March 3, 2017 Yep. Looked at all of those pages in the past week, other than going over them all again I'm running out of ideas. Thanks for that though.
Arthur Posted March 3, 2017 Posted March 3, 2017 we get this "hold for authentication" Have you tried adding all users to the _lpadmin printer group? i.e. sudo /usr/sbin/dseditgroup -o edit -t group -a everyone _lpadmin
manamaga2512 Posted March 5, 2017 Author Posted March 5, 2017 Didn't know about that (hence my shout out for a Mac guru :-), I will certainly give it a go on Monday.
manamaga2512 Posted March 5, 2017 Author Posted March 5, 2017 Couldn't wait until Monday so I remoted into a machine at work to try this out. Unfortunately no change though. Thanks anyway. Seems like the only thing to do is reimage.
Arthur Posted March 5, 2017 Posted March 5, 2017 Unfortunately no change though. Something else to try before you reimage... /usr/sbin/cupsenable "Printer_Name" /usr/sbin/cupsaccept "Printer_Name" To get the name of the printer, run: lpstat -p
manamaga2512 Posted March 6, 2017 Author Posted March 6, 2017 Thanks for that Arthur, but still no joy I'm afraid. It's going to be a couple of days of imaging me thinks.
bald_pig Posted March 6, 2017 Posted March 6, 2017 Were you trying those commands on the client machine, or the print server? I think you'd have to run them from the machine the printer is shared from, which looks like "osxdeploy" in your case.
manamaga2512 Posted March 6, 2017 Author Posted March 6, 2017 Aaah. Yes, I was doing them on the end user machines. I'll try the server now. Thanks.
manamaga2512 Posted March 6, 2017 Author Posted March 6, 2017 OK, ran those on our mac print server to no avail :-(
bossman Posted March 6, 2017 Posted March 6, 2017 We do use papercut but I have eliminated that as being the cause by trying to print directly to the printers IP address. No luck :-( This trouble shooting guide from Papercut seems to state otherwise as in direct printing to the printer: https://www.papercut.com/kb/Main/HoldforAuthentication You probably seen this already though
manamaga2512 Posted March 6, 2017 Author Posted March 6, 2017 Yeah seen that one thanks. Although I didn't have allow internet printing checked, so I tried that. 1
manamaga2512 Posted March 6, 2017 Author Posted March 6, 2017 One thing I have just thought of. Send a print job, wait for the 'hold for authentication' and then jump onto CUPS to see what's happening. I found the job in CUPS but noticed that a name of 'unknown' and a user of 'withheld'. So, and I don't know if I'm on the right tracks here. I'm thinking that the Mac is not sending the users details with the job, hence it's being held. Why would it stop sending user details though?
Arthur Posted March 6, 2017 Posted March 6, 2017 I'm thinking that the Mac is not sending the users details with the job, hence it's being held. Which authentication method is the printer currently using? Run the following command from Terminal on a client Mac and look for the option named "auth-info-required". lpoptions -p [color="#FF0000"]printer_name[/color] Change the text in red to the name of your printer shown when you run lpstat -v. If it's currently set to negotiate you could try authenticating using a username and password instead. e.g. lpadmin -p [color="#FF0000"]printer_name[/color] -o auth-info-required=username,password When you print you should be prompted for a username and password. Enter the credentials for a user who can connect to your Mac server. If that doesn't make any difference change it back using this command... lpadmin -p [color="#FF0000"]printer_name[/color] -o auth-info-required=negotiate
rfakes Posted March 7, 2017 Posted March 7, 2017 On the printer server, you do have "Share this printer on the network" ticked in System Prefs? Sorry to ask such a simple question but I have seen a similar thing before.
manamaga2512 Posted March 8, 2017 Author Posted March 8, 2017 Which authentication method is the printer currently using? Run the following command from Terminal on a client Mac and look for the option named "auth-info-required". lpoptions -p [color="#FF0000"]printer_name[/color] Change the text in red to the name of your printer shown when you run lpstat -v. If it's currently set to negotiate you could try authenticating using a username and password instead. e.g. lpadmin -p [color="#FF0000"]printer_name[/color] -o auth-info-required=username,password When you print you should be prompted for a username and password. Enter the credentials for a user who can connect to your Mac server. If that doesn't make any difference change it back using this command... lpadmin -p [color="#FF0000"]printer_name[/color] -o auth-info-required=negotiate When I ran the first command it didn't bring any authentication details up. I'm not at work now but will post a screenshot of the results tomorrow. Many thanks - - - Updated - - - On the printer server, you do have "Share this printer on the network" ticked in System Prefs? Sorry to ask such a simple question but I have seen a similar thing before. Yeah, first thing I checked :-)
manamaga2512 Posted March 8, 2017 Author Posted March 8, 2017 One thing we did try was to boot up our old Mac print server which worked flawlessly and still we got this hold for authentication message. I'm beginning to think that it's a local issue on each of the end client Mac's rather than server side. I've not had a chance to do much today as we have been rolling out new windows machines. I just hope we get more windows boxes soon because apple is just driving me up the wall lately. Unfortunately we don't have any external support that I can call on either :-(
manamaga2512 Posted March 8, 2017 Author Posted March 8, 2017 Thanks for all the help and advice so far by the way, it's much appreciated.
Arthur Posted March 8, 2017 Posted March 8, 2017 Unfortunately we don't have any external support that I can call on either :-( It might be worth joining the macadmins Slack group and posting your printer question in the #printers-n-cups channel. There are lots of very clever people on there that might be able to help.
manamaga2512 Posted March 10, 2017 Author Posted March 10, 2017 I'll be sure to check out that website, thanks. This morning, to eliminate anything we have (AD, JAMF, paper cut etc.) we unboxed a brand new iMac, followed the usual apple setup at first boot. Added a printer via it's IP address and sent a print job. We still got 'hold for authentication'. We didn't bind the machine to the domain, install the paper cut client or anything, so we have completely eliminated this being our Mac server issue or network. The iMac is on 10.12 Sierra. I beginning to think that this is a bug in OSX?
manamaga2512 Posted March 29, 2017 Author Posted March 29, 2017 Thought I'd update on this. Got in touch with Sharp (our MFD rental firm) and through working with them for a couple of days it was discovered that Mac didn't like the way we were installing the printer, or the drivers we were using. Rather than System Prefs>Printers & Scanners>Add Printer then waiting for the default list to populate with the shared printer and installing that. We had to use System Prefs>Printers & Scanners>IP then enter the IP address of the print server, then in the Queue field enter printers/name_of_printer Then give it a friendly name and them choose the correct drivers from the drop down menu! Easy when you know how :-/ Then the Principal decides to get rid of the iMacs and go back to Windows boxes!!! Grrrrrrr
mrnoisy Posted March 29, 2017 Posted March 29, 2017 Thanks for updating the call we have been having a similar issue with our Mac suites since moving to managed service and papercut, although it used to happen less frequently with canon/uniflow. I'll give the drivers a whirl as I know we did not push these out to the suites, might have just saved me a whole lot of Google Fu ! [emoji1310]
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now