08-02-2014 10:28 PM - edited 08-03-2014 04:37 PM
We recently bought a MF8580cdw and installed it wireless, very easy. Scanner works great. We are mostly Mac but I want to use my Chrome book to print. When I try to enable Google print in the remote UI and hit Register I get message "Failed to acquire information for registration". I see in the enable area Install CA Certificate. When I check CA certificates there appears to be 5 pre installed. I have checked the e-manual and don't find this error listed. Checked on line and didn't seem to get a good hit.
Update 24 hrs later. I Found that the SSL connection check box was not checked. After checking this the printer registered fine and it is now printing from my Chrome Book. I did not see any reference to make sure that SSL was enabled. sSmple fix but hard to find.
04-20-2015 05:36 PM - edited 04-20-2015 05:53 PM
This may or may not help some, but should help others...
08-04-2017 10:23 PM
I had this same error and on my MF212w I had to set the Date/Time.
After that I could register my printer on Google Cloud print.
This would normally be pushed to the printer via the router's NTP daemon.
04-22-2018 02:37 PM
Google Cloud Print suddenly stopped working on my MF733cdw. Here's what fixed it:
I didn't have to re-register Cloud Print or restart the printer.
05-05-2018 07:34 PM
I have a MF8280Cw and needed to Log into Remote UI (printer)
Cloud Print Settings
Uncheck Verify Server Certificate
Don't know how secure this is but I can't log into Remote Ui if I check SSL and when I check SSL certificate nothing is showing. At least I can print. Will think twice about printing anything sensitive.
05-21-2018 02:17 AM
Howdy y'all. Just won a Google Cloud Print grudge match with my MF8580Cdw. Thought I'd chime in here with some of the things that helped, and some that didn't.
My GCP on my 8580 just stopped working one day. No print for you. >:-(
It seems Google update the CA's on the CloudPrint servers, rendering some printers (mine) unable to login to register their availability to print. The required certificates were not installed. Word on the street is that the manufacturer has to update the firmware & include the newer certificates.
However, for me, the solution was to more simply install and register a new CA. I couldn't find a procedure to do exactly what I wanted, so I flailied in the dark until I stumbled upon a solution that worked for me. I hope it works for you too. It's amazing what flailing can do when you're a desperate father trying to get his daughter's Chromebook to print her 5th grade report on the state of Maryland that's due tomorrow.
- On my Mac OS machine:
- Go into Keychain Access (Utilities folder), and export all the entries for "GlobalSign" as .cer files.
- On the printer's web page:
- Go to "Settings/Registreation" -> "Security Settings" -> "CA Certificate Settings"
(Note the absence of GlobalSign in the default certificates)
- Click the button "Register CA Certificates".
- Specify one of the .cer files exported above
- Click Install, then Register
Note: You'll see the previous .cer file again. It's safe to click "Delete" & specify a new file.
This doesn't delete the registration, just the install file.
- Go to "Network Settings" -> "CloudPrint Settings" and try to register your printer.
Note, no power-cycling of the printer was needed in any of my above procedures.
Here were some of the things I tried that didn't work.
- SSL settings enabled/disabled, and all the hoops I jumped thru making my own certificates & keys on the printer, etc. None of that seemed to affect GCP's ability to see my printer.
- Registering the printer with GCP was possible by disabling "Verify Server Certificate", however every print job threw an "error" in the CloudPrint queue.
- A *lot* of restarts
- Initializing all settings (I admit this *may* have contributed to the solution, but even after taking this step, nothing worked until I installed the .cer files above)
I hope this helps someone. I'll put this on appropriate GCP discussions that reference the MF8500 series.
05-21-2018 09:48 AM - edited 05-21-2018 09:51 AM
I'm assuming you were generating an SSL cert from a self signed CA/ICA? Whenever a non-commercial CA/ICA is used, the self-signed CA should be concantenated within the SSL cert's file, with the SSL cert listed first in the file, and the CA listed second (if it's a self-signed CA & ICA, certificate would contain the SSL cert, ICA cert, then the CA cert).
All internet ready devices contain a master CA list, either as individual certs or as a master cert will all CA included within, so it's a bit odd that you would have to export a master list of CAs from an Apple product.
05-21-2018 10:00 AM