OSX Lion, Windows Network Printer

I'm afraid I don't have a solution to this, but am experiencing the exact same issue.

Similar issue. More specifics: one can add the windows printer as usual, but the "URL" that is available post-setup in Snow Leopard is no longer there. However, it appears that Lion connects to the printer, but fails to keep the connection.

I am having this same problem and have been searching for a fix for over a week.

We have Active Directory authenticated Windows print queues that our Mac users connect to using SMB. The problem is that when we connect in Lion, the printer comes up, but all print jobs immediately pause because the connection is refused by the server. Best I can tell, this is because the new SMBX protocol in Mac OS X Lion is not properly authenticating to the Windows print queues.

If anyone has any idea how to fix this without directly compiling and configuring SAMBA in Lion, please reply to this post and let us know - we will owe you bigtime!

For Windows printers that connect via SMB, but hang up indefinitely, first try to reinstall all of them in the Lion control panel. The procedure is what one would expect here, although the proper driver has to be selected for each printer. Windows printer choices carried over from Snow Leopard still seem to look for the now-ejected SAMBA, while new installations go to straight to SMBX invisibly. This all worked for me, but there still might be a problem in that my print job took minutes to terminate after all the actual printing was done.

Unfortunately, adding the printer through the GUI is not an option for us due to our fragmented network setup and the complixity of adding a printer using this method. We have 4000+ students who need to add the a Windows print queue to their computers in order to use the printing systems at Washington University in St. Louis. The Mac users add the queue by running a script that uses the Unix lpadmin command to add the printers via CUPS. Based on the info you just shared, I'm guessing that maybe Apple forgot to modify the built-in CUPS interface to use SMBX and that's why any Windows printers added using that method simply won't work.

Again, any other clues would be greatly appreciated!

After trying all sorts of suggestions for solving this, wasting hours and giving up, I just discovered a very simple solution indeed.

I have two printers connected to the same Windows server, and both of them paused whenever I tried to print to them, with a message saying Unable To Connect To Server. I tried deleting and re-installing the printers, but it made no difference. However, I did notice that I was never prompted for any login credentials, either when re-installing the printers or when printing to them.

I opened the Keychain Access utility, and searched for the name of the server to which the printers are connected. I found several different sets of credentials, some of which mentioned the printers. I deleted ALL of the credentials which mentioned the name of the server.

I then tried to print to one of the printers. I got prompted for login details, gave them and ticked the checkbox to remember them in my keychain.

Both printers now work, and Keychain Access only shows one set of credentials for the server, with no mention of the names of the printers.

I had the same issue and deleting the printer's Keychain entry did work for me.

Unfortunately, my issue runs deeper than an old keychain entry. Even with nice new fresh keychain entries, Lion still refuses to correctly authenticate using Active Directory Credentials. I am dealing with an extremely large enterprise-level Active Directory setup here, which I think is likely what is causing the issues.

I take it the error you get is still "Cannot connect to server"?

Are your printers connected to Windows computers, or are they network printers?

Do you get prompted for credentials when you try to print?

I have the same issue, and with me, it is not a keychains issue.

In the past, my Brother HL-2030 laser printer was connected to my DSL modem (a Telekom Austria Pirelli PRGAV4202N). After entering its IPP URL, that worked perfectly.

With Lion, this has stopped working, showing exactly the symptoms you described (printer goes to pause immediately).

Today, I have moved the printer from the Pirelli modem to my Iomega StorCenter ix2-200 NAS which supports USB printing, too.

With the NAS, printing does not work, either, but the symptoms slightly vary. In the beginning, there is a slight improvement: When I click the "+" icon for adding a printer, the printer shows up in the list! (This is new - with the Pirelli modem, I had to manually enter the IPP URL.)

But as soon as I try printing, the printer queue dialog (German MacOS) shows "Drucker suchen" ("searching for a printer") for a few seconds, and then the printer dialog shows the printer as paused ("Angehalten.") with the additional information "Drucker ist nicht angeschlossen" ("printer is not connected").

When selecting the blue "i" (print job info), the information "Auftragsnachricht: Der Drucker-URI ist falsch oder existiert nicht mehr." (literally: "print job message: The printer URI is wrong or does not exist any longer".)

This is really annoying, and I am desparately looking for a solution, too.

I've been periodically trying to get my recently updated Mac to print through our university network to our lab's printer. It took a bit of faffing about but so far the information here works to use the smb route:

https://discussions.apple.com/thread/3216160

It is really important to do everything - delete all keychain references, set everything up in CUPS, etc. It's like 'spitting and turning round three times with your eyes shut, etc'!

Hope this helps.

Thanks for recommending the other thread. I looked it over and it again seems to be a fix only for an instance where you are authenticating using credentials that are local to the Windows print server. In my case, the Windows print server is part of a large Active Directory forest. This forest is used to grant permissions to the print queues. We actually have a script that adds the printer using the underlying CUPS interface, but we NEED to be able to send a credential such as: "username@domain.university.edu" - we can't simply pass "username".

To give a little more info, when we setup a printer through CUPS (the same as in 10.6) the print queue is added and configured, but when you send a print job, you breifly see the error "connection refused" then the job goes into a "Paused" state, indicating that authentication is required. If you re-start the print job, you are prompted for credentials (which can be saved in the Keychain) but even if you supply the credentials again, the job still pauses with the samme "connection refused" error.

For some reason, 10.7 Lion cannot send a proper username (username@domain.university.edu) across to active directory and authenticate.

Conincidentally, this same problem seems to also be keeping us from joining our Lion computers to our Active directory system.

Same for me: I also had the immediate pausing problem and solved it by removing all the keychain entries of the corresponding server.

We have the same problem, as jwbailey mentioned, at our University. Our printer access is authenticated through an Active Directory and every user that has upgraded to Lion is presented with 'connection refused' errors.

Is there any known solution or work-around yet, or is this still in Apple's hands?

- dutchminator