Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Windows Network Printing Connection Timeouts - Lion Specific

Hi Guys,


In a school environment here and starting to update some of the machines to Lion to test compatibility with the systems we utilize.

I have got two machines that have done an update from Snow Leopard to Lion and two that I did a fresh install with using the widely used boot disc method.


Everything was going fine, all the SMB shares were mounting as they should, proxy auth was working and 802.1X auth was fine.


But SMB/Windows printing is screwed. Lion can see and connect through SMB to the Printer Server and access the SMB file shares on that server. When I first tried to print to the Windows hosted printers Lion claimed it could not connect to the server. No problem I thought, something was bound to happen at some point, so I removed and added the printers again manually. Now, while it does let me try to lodge print jobs on those printers it sits there, displays a progress bar and states that it is "Connecting". After roughly 30 seconds, the "Connecting" window disappears and nothing changes at all. The Mac OS X Print API pane is still there with no changes what so ever.


I am assuming that for some reason it is impossible for Lion to communicate with SMB printers now and that the connection is timing out.

This behaviour is exhibited on both the upgraded and clean install machines.

This behaviour is not exhibited on the Snow Leopard (or even the couple of Leopard machines we have lying around) or Windows.


Any ideas?

All help would be greatly appreciated.


Thanks,


Paul

Posted on Jul 21, 2011 2:44 AM

Reply
41 replies

Jul 21, 2011 1:57 PM in response to PaulDab

I don't know about that, if the print server didn't like the credentials it should just request fresh ones. No matter how Lion packages it all up, if it requests new ones Lion should still respond to that. Or at least somewhere along the way Mac OS X should have seen an error in communicating with the print server, not just timing out and reporting nothing.


I suppose this is because Apple has dropped Samba in Lion. (http://www.appleinsider.com/articles/11/03/23/inside_mac_os_x_10_7_lion_server_a pple_replaces_samba_for_windows_networking_services.html)

Obviously they haven't worked out all the kinks yet, but it doesn't really make sense because it can connect fine to SMB file serves.

Jul 21, 2011 5:24 PM in response to PaulDab

Nope, the Windows print server is set up with just simple authentication (NTLM). The Windows server is running 2008 R2. Yes I have tried clearing out the Keychain. I don't think that authentication is the problem here. CUPS shows an error in the SMB backend. Lion has changed how it talks to SMB servers. I think this could be contributing. Have attached the log with the relevant parts below. Permissions aren't the problem. I tried chmod'ing smb to 777 with no change.


D [22/Jul/2011:10:10:04 +1000] [Job 3] Backend returned status 1 (failed)

D [22/Jul/2011:10:10:04 +1000] [Job 3] Printer stopped due to backend errors; please consult the error_log file for details.

D [22/Jul/2011:10:10:04 +1000] [Job 3] End of messages

D [22/Jul/2011:10:10:04 +1000] [Job 3] printer-state=5(stopped)

D [22/Jul/2011:10:10:04 +1000] [Job 3] printer-state-message="/usr/libexec/cups/backend/smb failed"

D [22/Jul/2011:10:10:04 +1000] [Job 3] printer-state-reasons=paused

Jul 23, 2011 11:56 PM in response to PaulDab

I haven't had a look at Lion yet with regards to SMB printing. But as we use UniFlow, Mac printing via SMB is of no use to us as every print job shows 'Remote Level Download' rather than the job name. This is turn makes it difficult to track job usage and billing. So we have always had LPD print services enabled on the Windows server and then print via the shared queue using LPD on the Mac (lpd://server_name/printer_share_name). This method ensures the user name and job information is present in the SPL/SHD files being sent from the Mac.


Another thing I have found over the years with SMB printing is that the vendor drivers are not always compatible with this methiod. For Postscript devices it is best to use a PPD rather than the vendors 'full' driver. And if the printer is not Postscript, well then it becomes a bit of a nightmare.


I have to check a couple things tomorrow regarding SMB and LPD printing via Server 2008 R2. I will let you know what I find Monday evening.

Jul 24, 2011 3:14 AM in response to PaulDab

I have a SBS2008 server with some Mac clients. Everything works, except for smb printing. I have a Canon Pixma ip4000 USB connected tot the SBS box and shared with the sbs wizard.


It used to work with 10.6 perfectly but since I updated to lion printing was impossible.

After a couple of days i figured it out:

When printing, I get an EventID of 4625, password or User unknown with

Accountname: domain/user

Accountname: domain

which format is not correct.


In the printer status view (with Printername on top) It says: Authentication required (Sme time when ID 4625 on the SBS box)

Printing stuck, but when I 'resume' the printing, I get the Authentication Screen (radio button Registered User isselected) which says:

User: ' domainname/user' is fillled in


But at that moment, when I change that to 'user' only and resume printing works, but one time only!


When i select to store it in the keychain, next time I get the same procedure to handle.


So good so far.. If anyone knows how to handle this, I would like to hear it.


('domain' and 'user') are actually the domain an username of the SBS enviironment.

Jul 24, 2011 4:26 PM in response to A333

Good to know, but I'm pretty much convinced that there is something wrong with the SMB printer backend in CUPS in Lion as the logs state over and over again that: "/usr/libexec/cups/backend/smb failed"

Starting to think that this is a bug in the CUPS build included with Lion. Lion states that CUPS 1.5.0 is the active build (I can't find out if it is b1, b2 or rc1). For comparison, to my knowledge 10.6.8 included CUPS 1.4.6.


A bug report has been submitted to CUPS about this issue. There is one other line that intrigues me: "auth-info-required is set to negotiate, but AUTH_UID is not in env" Anyone with CUPS background know what I can set in cups.conf or printers.conf to try and fix this?

Jul 25, 2011 11:12 AM in response to PaulDab

Printing with Lion seems to be aproblem for me as well. My network printers are no loner visible and restting CUPS didn't help with that. I can see the server that hosts the print queues but not the queues themselves. Also, not all of my network systems appear. I can, however, mount shares from the same host.

Jul 25, 2011 4:18 PM in response to PaulDab

Well I cannot fault SMB printing from Lion. The only thing I did notice is that for a workgroup configuration of Lion, when adding the printer and selecting the 2008 server share, you have the ability to select Guest. Then when you actually print, the window that appears with Lion is not the same as SL where you have the Guest radio button and the other account section. Lion only shows a window prompting for user info. I typed guest and it let the document print.


For my test, the printer is a Canon imageRUNNER ADVANCE C5051. The Server 2008 R2 is a standalone server. The driver installed is the Canon Postscript v20.55. On Lion, I used the Canon PPD for the iR ADV C5051.

Jul 27, 2011 11:55 AM in response to PaulDab

I'm having the exact same problem -- configuration that worked on an AD network (HP Printer using generic postscript driver, using windows auth) no longer works after having upgraded to Lion.


Errors from cups/error_log:



D [27/Jul/2011:14:39:06 -0400] [Job 6] Started smb backend (PID 585) D [27/Jul/2011:14:39:06 -0400] [Job 6] cgpdftops - using PPD file "/private/etc/cups/ppd/NYPS01_Online_B4.ppd"... D [27/Jul/2011:14:39:06 -0400] [Job 6] PS Matching Mode = AP_ApplicationColorMatching D [27/Jul/2011:14:39:06 -0400] [Job 6] cgpdftops - languageLevel = 2, mediaBox.size.width = 612, mediaBox.size.height = 792 D [27/Jul/2011:14:39:06 -0400] [Job 6] cgpdftops - documentMediaBox.size.width = 612, documentMediaBox.size.height = 792 D [27/Jul/2011:14:39:06 -0400] [Job 6] STATE: +connecting-to-device D [27/Jul/2011:14:39:06 -0400] [Job 6] Connecting to printer... D [27/Jul/2011:14:39:06 -0400] [Job 6] Set job-printer-state-message to "Connecting to printer...", current level=INFO D [27/Jul/2011:14:39:06 -0400] [Job 6] Looking up "NYPS01.NYDOMAIN.local"... D [27/Jul/2011:14:39:06 -0400] [Job 6] Failed to connect to "smb://:@NYPS01.NYDOMAIN.local/": STATUS_INVALID_PARAMETER D [27/Jul/2011:14:39:06 -0400] [Job 6] Set job-printer-state-message to "Unable to connect to server", current level=ERROR D [27/Jul/2011:14:39:06 -0400] [Job 6] smb backend (PID=585) stopped with status 256 D [27/Jul/2011:14:39:06 -0400] [Job 6] smb backend will exit with status 1 D [27/Jul/2011:14:39:06 -0400] [Job 6] Page = 612x792; 17,19 to 595,773 D [27/Jul/2011:14:39:06 -0400] [Job 6] slow_collate=0, slow_duplex=0, slow_order=0 D [27/Jul/2011:14:39:06 -0400] [Job 6] Before copy_comments - %!PS-Adobe-3.0 D [27/Jul/2011:14:39:06 -0400] [Job 6] %!PS-Adobe-3.0 D [27/Jul/2011:14:39:06 -0400] [Job 6] %APL_DSC_Encoding: UTF8 D [27/Jul/2011:14:39:06 -0400] [Job 6] %APLProducer: (Version 10.7 (Build 11A511) Quartz PS Context) D [27/Jul/2011:14:39:06 -0400] [Job 6] %%Title: (FedEx Ship Manager - Print Your Label\(s\)) D [27/Jul/2011:14:39:06 -0400] [Job 6] %%Creator: (Chrome: cgpdftops CUPS filter) D [27/Jul/2011:14:39:06 -0400] [Job 6] %%CreationDate: (Wednesday, July 27 2011 14:39:06 EDT) D [27/Jul/2011:14:39:06 -0400] [Job 6] %%For: (sasha e) D [27/Jul/2011:14:39:06 -0400] [Job 6] %%DocumentData: Clean7Bit D [27/Jul/2011:14:39:06 -0400] [Job 6] %%LanguageLevel: 2 D [27/Jul/2011:14:39:06 -0400] [Job 6] %%Pages: 1 D [27/Jul/2011:14:39:06 -0400] [Job 6] %%BoundingBox: (atend) D [27/Jul/2011:14:39:06 -0400] [Job 6] %%PageOrder: Ascend D [27/Jul/2011:14:39:06 -0400] [Job 6] %%EndComments D [27/Jul/2011:14:39:06 -0400] [Job 6] Before copy_prolog - userdict/dscInfo 5 dict dup begin D [27/Jul/2011:14:39:06 -0400] [Job 6] Before copy_setup - %%BeginSetup D [27/Jul/2011:14:39:06 -0400] [Job 6] Before page loop - %%Page: 1 1 D [27/Jul/2011:14:39:06 -0400] [Job 6] Copying page 1... D [27/Jul/2011:14:39:06 -0400] [Job 6] PAGE: 1 1 D [27/Jul/2011:14:39:06 -0400] [Job 6] pagew = 578.8, pagel = 754.8 D [27/Jul/2011:14:39:06 -0400] [Job 6] bboxx = 0, bboxy = 0, bboxw = 612, bboxl = 792 D [27/Jul/2011:14:39:06 -0400] [Job 6] PageLeft = 16.6, PageRight = 595.4 D [27/Jul/2011:14:39:06 -0400] [Job 6] PageTop = 773.4, PageBottom = 18.6 D [27/Jul/2011:14:39:06 -0400] [Job 6] PageWidth = 612.0, PageLength = 792.0 D [27/Jul/2011:14:39:06 -0400] [Job 6] Wrote 1 pages... D [27/Jul/2011:14:39:06 -0400] [Job 6] Backend returned status 1 (failed) D [27/Jul/2011:14:39:06 -0400] [Job 6] Printer stopped due to backend errors; please consult the error_log file for details. D [27/Jul/2011:14:39:06 -0400] [Job 6] End of messages D [27/Jul/2011:14:39:06 -0400] [Job 6] printer-state=5(stopped) D [27/Jul/2011:14:39:06 -0400] [Job 6] printer-state-message="Unable to connect to server" D [27/Jul/2011:14:39:06 -0400] [Job 6] printer-state-reasons=paused

Jul 27, 2011 12:27 PM in response to lfdjr

We're seeing a similar problem for early Lion adopters on our campus. Mac users who don't bind to our AD print to SMB shared printers on a central server. The setup procedure was such that adding a printer (as an 'smb://<server>/<queue> style resource) required no authentication but the first print job would ask for your AD username and password. Saving that in your keychain meant that printing always worked automatically after that.


Now, with Lion, adding the printer in the same way gives no errors and asks for no authentication but trying to send a print job to the queue silently fails.


Reading elsewhere on the support forums that smbutil seems to work properly where printing fails I decided to point that tool at the print server along the lines of 'smbutil view //domain;username:password@<server>' and was rewarded with a full list of all the print and file shares available on the server.


As an experiment I attempted to mounted a shared volume from that server. I was prompted for a username and password which I duly enterred (as it was not stored in my keychain) and the volume was successfully mounted. I then added the printer again (shared from the same server to which I was already authenticated for the shared volume). This was, as usual, successful but this time subsequently trying to print I was this time prompted for credentials. Enterring my AD credentials resulted in my print job being successfully submitted!


Next I unmounted the shared volume and tried to print again, this worked fine. I then deleted the printer, added it again and successfully submitted another print job.


Lastly I logged off and on again and tried to submit another print job, which this time silently failed. Back to the old behaviour. I'm guessing this was due to my Kerberos ticket being cleared by my logout.


I know this isn't a fix, but I think it's pointing towards the problem. I'm fairly sure this proves there's an authentication bug specifically in the interaction between SMB and CUPS.

Aug 3, 2011 1:30 PM in response to PaulDab

Similar issue here. After reading through the posts and trying different options, as in keychain, printer drivers and others. This is what worked for me; I found the printer via bonjour, selected it, the correct driver was installed and no authentication errors. As a postscript to this note, it seems strange that when there is an authentication error, you are not prompt for a password as happen in Snow Leopard.


thanks

Windows Network Printing Connection Timeouts - Lion Specific

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.