Ricoh Mp 5055 Driver Windows 7

[Paz Warsager]

Keepin mind those drivers are a couple weeks short of five years old as of this writing, and printing has changed over that time. The install is failing by design, specifically because a line in the install check script stops it if macOS version 11 is detected. You could hack the installer to defeat that script, but I still have my doubts about them working. I would recommend finding a different driver or replacing the printer.

You didn't mention what Ricoh device you're using, but If memory serves, Ricoh copier/printers had PostScript as an optional feature, but the macOS drivers required it. That could be what you're running into with the Ricoh supplied PPD.

Ricoh(5055's & C6004's) and Papercut here. No driver issues in Catalina. We use the postscript drivers on Ricoh's website.

Can't comment on Big Sur as I've blocked it until Sophos gets the lead outta their tookus and releases their BS compatible update.

Same issue here and my google-fu isn't finding any answers. My hunch is that it is that the installer isn't properly notarized which is why it won't fly with Big Sur. I might try notarizing it myself for internal use, but I think I tried that back in the summer.

As a matter of fact, actually any Mac driver for the printer model would do I guess.

It would be great help, since its not there in the Apple Ricoh Driver 3.0 pack you posted above, I already checked.

Many thanks in advance!

Looking on Ricoh's site they only have W7 and Windows Server 2008R2 as their only drivers for this particular model. That tells me the model is quite old and non-supported so Mac drivers from Ricoh or Apple most likely won't happen. I'd stick with the generic PPD or find something a little newer to kill trees with if that's a possibility.

Thank you all for the response.

@joshuasee , we are using Ricoh IM C4500 / 6000 MFP. Apparently the drivers in Ricoh website stated it is PPD file but when I dig into /Library/Printers/PPDs/Contents/Resources/ it is not in a format I can upload to the policy.

@mainelysteve Yes, on Catalina no issues and works like a fly. How did you extract and upload the PPD file as the postscript drivers in Ricoh webpage does not contain the*.gz file? Did you map the printer from Jamf Pro? Care to share how you add the printer in Jamf Pro?

In our environment, we are using Papercut as well and also using virtual printer.

@sebastianl No extracting here. I use the provided pkg with no modifications. The printers I need to map are done through our Munki/Managed Software Center infrastructure. A user picks a printer, clicks install and in the back end it runs a script that uses lpadmin to actually map the printer on the client. It's semi old school as it relies on the driver(the .gz) being installed which as most of us have read are on borrowed time. I don't mess with the printer policies in Jamf Pro as I'd rather a bone headed slip-up or management hiccup not mess with my queues.

Once I upgrade my PaperCut app server I'm going to trial the print deployment tool they have or tempt fate and start using AirPrint. Either way it's best to start prepping for the current and future cups changes to macOS.

@mainelysteve We actually have the AirPrint working in Papercut on our environment. It works great but AirPrint does not have some printing features (like set dpi) compared to mapping printers. We have yet to try Print Deploy yet and curious as well on how it works. Do post some updates if you get it to work.

I waded into it not long after that post, but the pool was too cold so I got out very quickly. Print Deploy uses Zones based on IP addressing which wouldn't work for me since IP addressing sometimes spans to other buildings on our campus so it was pointless for me to continue down that rabbit hole.

We are using Mobility Print in Papercut for quite some time now. It has limited printing options but get the job done. Easy to set up and works really well. I hope you have a good transition to Mobility Print.

Jamf's purpose is to simplify work by helping organizations manage and secure an Apple experience that end users love and organizations trust. Jamf is the only company in the world that provides a complete management and security solution for an Apple-first environment that is enterprise secure, consumer simple and protects personal privacy. Learn about Jamf.

This site contains User Content submitted by Jamf Nation community members. Jamf does not review User Content submitted by members or other third parties before it is posted. All content on Jamf Nation is for informational purposes only. Information and posts may be out of date when you view them. Jamf is not responsible for, nor assumes any liability for any User Content or other third-party content appearing on Jamf Nation.

We have a site that has several printers on it. One of these was an HP Laserjet M400. The printer started doing this thing where it would boot up, then crash with a 79 Service Error when plugged into the network. We tried all of the usual nonsense. We unplugged the printer from the network and did a factory reset, printer came up just fine - second we plugged it into the network it crashed with the 79 error. We tried hard coding the IP at the printer console, no go. Setting it to either a reservation or auto assignment at the DHCP server, also no go. Finally, we took the printer off the network, and a tech took it home, plugged it into his lan, did a firmware update on it to the latest firmware. It was fine on his home network. Took it back, plugged it into the site network -79 error. Finally in desperation we tried a HP Model M402dne printer - and it also crashed with a service 79 error the moment it was plugged into the network. We even moved the printer to other ports on the switch - same problem.

What we finally did to "fix" it was we went into the printer services config and turned OFF IPv4. Then the printer did not crash when plugged into the network and it setup an IPv6 link local address. Then we downloaded and ran the latest HP printer driver installer on the 2 PC's that needed to print to this printer, and had the driver do a Search on the network whereupon it found the printer, configured a WDS port as IPv6 only, and setup the driver. The printer then printed fine.

There are 3 other printers on the network. One is an HP Laserjet Pro M404dn, another is a Ricoh MP 5055 and the last is an HP Laserjet Pro 4001dn. All 3 of those work fine. It is clear that this is a networking bug buried in HP's IP stack since it affects multiple printers. And in reading the history on this forum it's also clear many people have been bitten by this bug and firmware updates have done nothing at all for many of them.

3a8082e126