What hath Apple wrought? Dealing with the client-error-not-authorized error
August 5th, 2009 by adminMy wife managed to wean herself from Microsoft a couple years ago. Not quite ready to jump to Linux, she decided on a Mac, and has generally been pretty happy with Mac OS X. I’ve been pretty happy with it since even though it’s not Linux, it’s BSD under the hood, and I can fix many of the problems she has.
But then she “upgraded” to Leopard. Man, was that a mistake. The first thing that has happened is that her MacBook can’t maintain wireless connection. She can get on our local home network, but AirPort drops signal every few minutes, has to rescan, and after a few minutes will pick up again. This makes web browsing almost impossible. I’ve tried all the tricks I could find on the net, but it just can’t keep stable. Apple really screwed up Airport with Leopard, at least in terms of compatibility. I hope the new Snow Leopard fixes this, because I haven’t figured out how to do it myself.
There’s another problem, though — her machine can no longer recognize the wireless HP PhotoSmart C8180 printer — which worked fine before the upgrade. The *original* way I added the printer was by going to System Preferences -> Print&Fax -> + to add a printer, choose “JP Jetdirect” as protocol, add the ip address, choose the driver from the list, and there you go. Unfortunately, this time, the printer is not found, and the driver defaults to “Generic Postscript.” When I try to add the printer manually, I get an no connect error with the error message “client-error-not-authorized error.”
I’ve tried every permutation on the books. Finally I decided to bypass the OS as much as possible and use CUPS (the underlying printer setup system) directly. To access that, go to http://127.0.0.1:631. That brings up the CUPS administration page for the local box. Choose “Add printer” and follow the directions. The only trick is that for the URL, you need to actually specify the socket, i.e. instead of “http://whatever” you type “socket://xxx.xxx.xxx.xxx:9100″ where xxx.xxx.xxx.xxx is the ip address of the printer. This added the printer fine, and it showed up in the list when I went back to system prefs. Go figure.
Good luck, and I hope Snow Leopard fixes this.
UPDATE: A friend of mine told me that there was a more simple solution. Apparently if you **log in** as the administrator and add the printer (as opposed to just putting in the admin name and passwd when the requestor comes up when you try while logged in as a regular user) it will work. I tried it on my wife’s mac. I can add the printer, but it doesn’t find it automatically, so I still have to enter everything by hand. Go figure. But it might be easier to try this before going directly to CUPS.
Posted in Computer stuff | 6 Comments »
August 7th, 2009 at 10:39 am
That’s funny. My kids Ubuntu box would not see my new network printer through the traditional Add Printer mechanisms. Didn’t even see it on the network. Did the CUPS thingie and it found it and all is well. Makes you wonder why CUPS is not “under the hood” of ADD PRINTER functionality.
August 7th, 2009 at 6:29 pm
Actually, it is. CUPS is what the “Add Printer” software talks to. The problem is that the folk who write the GUI overlays to try to automate everything end up screwing up the communcation and functionality of the CUPS system.
It’s that way with all the “make life easier” guis. Mandriva’s automatic wireless tools are a godsend half the time and a pain in the ass the other half.
October 9th, 2009 at 6:51 pm
Thank you for this! Rather annoying that the OS X gui does not allow providing credentials for admin stuff when logged on as a regular user. This post saved my weekend.
Cheers,
Chuck
October 21st, 2009 at 5:17 pm
I am very frustrated with the same problem. I have accessed the web site referred above. Is this site for the general public? It asks for a login and password.
October 21st, 2009 at 6:47 pm
If you are talking about the site “http://127.0.0.1:631″, then that is simply your own box. The ip address 127.0.0.1 is the local host. The “:631″ part is the port you are accessing on your own machine.
It doesn’t ask for a login and password on my box, but if it does for you, then I suspect it would work best if you use the root login and password.
August 11th, 2010 at 2:06 pm
Been working on trying to get this Toshiba to connect for over a year. Your post (CUPS) solved the problem in less than an hour. THANK YOU! I Can now print to the Shitiba.