I get one of these whenever I send something to this list. But I get replies, so it seems to be delivering.
-Rick

-------- Original Message --------
Subject:        Delivery Status Notification
Date:   Fri, 9 Jan 2015 07:53:31 -0700
From:   <[email protected]>
To:     <[email protected]>



Your message was not delivered successfully.

  Subject:   Re: Printing to a Windows 2012 R2 print server with Version 4 
drivers
  Sent:      Fri, 09 Jan 2015 09:47:52 -0500

 The message could not be delivered to the following recipient:
 [email protected]



Final-Recipient: rfc822; [email protected]
Action: failed
Status: 5.0.0

--- Begin Message ---
Jake,

Thanks for confirming my analysis.  Misery loves company.

I am implementing a paralell system using SSL encrypted Basic Authentication via IPP to a Linux CUPS server. I think it will work well.

The big players seem to be trying to capture their customers permanently.

Yours,
-Rick

On 1/8/15, 8:19 PM, Rundall, Jacob D wrote:
Unfortunately all I can do is echo what you’re finding and experiencing.  I 
also have not been able to get Windows 2012 print server + Type 4 driver + Mac 
client printing to work.  When I was first running into that I searched the web 
as you’ve done and found a few articles that explained it wasn’t generally 
possible.  Here’s another article similar to the one you’ve found (with an 
answer by the same person, in fact):

https://social.technet.microsoft.com/Forums/en-US/7464779c-19b3-446e-8af3-4e38ea0b1066/os-x-printing-to-server-2012-and-type-4-drivers?forum=winserverprint

When I encountered this issue I tested with several models of printers and 
could get things working with Type 3 drivers but never Type 4.  It’s too bad MS 
seems to be cutting Mac clients out of the picture, because it was just 
starting to work fairly well.

Jake

On Jan 8, 2015, at 3:13 PM, Rick Cochran <[email protected]> wrote:

It pains me deeply to even be in a position to ask this question, but there I 
am.

I can create the CUPS queue on the OS X client.  When I print to the queue, it 
prompts me for ID and password.  The print job is sent to the Windows print 
server.  Then it disappears, but not without a trace. Which led me to this 
article:

https://social.technet.microsoft.com/Forums/windowsserver/en-US/0e72ba1d-8c80-4e76-88a7-8d48335f78d5/windows-server-2012-printing-error?forum=winserverprint

Apparently, the format of print jobs from OS X is incompatible with Microsoft's 
Version 4 print drivers.

My understanding is that Version 4 drivers address many of the problems 
associated with running a Windows print server.  I am not willing to revert to 
Version 3 drivers.  If necessary, I will implement a separate solution 
(probably IPPS via Linux CUPS) for OS X.  I suspect IPPS to Windows would 
result in the same Version 4 driver problem.

Any help would be appreciated.

Yours,
-Rick


_______________________________________________
Do not post admin requests to the list. They will be ignored.
Printing mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/printing/rundallmac%40gmail.com

This email sent to [email protected]


  _______________________________________________
Do not post admin requests to the list. They will be ignored.
Printing mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/printing/rcc2%40cornell.edu

This email sent to [email protected]

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Printing mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/printing/8427890616%40sms.mycricket.com

This email sent to [email protected]


--- End Message ---
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Printing mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/printing/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to