Q: Printer job "On hold (authentication required)"
-
Nov 14, 2012 2:31 PMby marconelli,After trying so many other suggestions to no avail, this one worked for me. Just to be clear: use "guest" as the login name and "guest" as the password. Thank you so much for posting this solution. (It still amazes me that nothing else seems to work, even the actual and correct login names and passwords for my Windows workgroup!)
Marc
-
Feb 26, 2013 6:17 AMby antst,In my case it doesn't show popup authorization dialog, even if I resume job. (refresh icon).
It does with different account, but with my normal one - not anymore (it used to work as it should).
It just freezes print queue window.
all I have in logs is:
2/26/13 3:14:01.321 PM PrinterProxy[596]: *** WARNING: -[NSImage compositeToPoint:operation:] is deprecated in MacOSX 10.8 and later. Please use -[NSImage drawAtPoint:fromRect:operation:fraction:] instead.
2/26/13 3:14:01.321 PM PrinterProxy[596]: *** WARNING: -[NSImage compositeToPoint:fromRect:operation:] is deprecated in MacOSX 10.8 and later. Please use -[NSImage drawAtPoint:fromRect:operation:fraction:] instead.
2/26/13 3:14:03.703 PM NetAuthSysAgent[588]: Property list invalid for format: 200 (property lists cannot contain objects of type 'SecCertificate')
So, I guess problem is with NetAuthSysAgent or NetAuthAgent. But I spent already 10 hours trying to get a bit more information with no luck
-
Jul 4, 2013 11:00 PMby ryden74,My situation is pretty standard: a Mac user in a Windows-based network. The solution uses CUPS.
I originally set my Mac up in Snow Leopard in 2012, and got it working with the windows network printer. But then it stopped working after a few weeks, continually getting the "On hold (authentication required)" message.Despite authenticating and re-authenticating, and deleting the network passwords many times, I couldn't get it to work.
This message is INCREDIBLY frustrating, since I could see that my computer was communicating successfully with the printer; getting the levels of toner in the printer, for example.
The original thing that I had done was to set up the printer with the following connection string, using Mac OSX's Settings application:
smb:\\<printer's IP address>\<printer's Windows network name>
(I had tripped up for a long time here on the fact that the Windows printer network name had spaces in it. Scotched that one by replacing the "space" character with the "%20".)
However, as mentioned already, this only worked for a while. Then there ensued much head-bashing against-wall (given that the network IT people are soooo anti-Mac that it is simply a waste of time talking to them, which, again, I think is pretty common in the world.... all those "IT professionals" are in the job-protection scheme, and don't want people to move to Mac).
The solution was to use OSX's CUPS printing management, via http://localhost:631 on the Mac. This brings up the "Common Unified Printing Solution", which is OSX's printer management. Then I added the printer from the "admin" part of the CUPS web-based interface, using the connection string
socket:\\<printer's IP address>
(discovered from http://localhost:631/help/network.html)
and told CUPS the printer's name (going with the %20 thing for all spaces in the name again) and my network username and password, and then told it the printer type... and it proceeded to print.
YAY!
So I can yet again keep working in an anti-Mac environment, without anyone forcing a crappy Windows 7 or 8 PC onto me.
-
Oct 3, 2013 10:39 AMby bumpwhite,Tried your approach and deleted related keychain access items. Did not resolve issue. Old user id still shows up. This has always been the biggest piece of crap mac has. It really ****** me off Apple has no interest in fixing the problem. These arrogent ******** need to understand MS will be around for the forseeable future.
