Unable to Scan from windows with imageCLASS MF462dw II

[fed-up-user]

Unfortunately I bought an imageCLASS MF462dw II a few months back when my previous Cannon Laser finally died after years of faithful use.  First unit, DOA.  Second unit works to print, or scan from face plate, but I have yet to get the software to work from computer (Windows 10).  I installed, rebooted, updated firmware, reinstalled, installed master package, rebooted, reinstalled, tried to find worthless help online.  If I weren't past the return period, I would return it for a refund and try to find a printer with working software.

Bottom line, I now find I **NEED** to scan multiple double sided pages to a PDF, and it appears I can't do that until I get this software to work.  So I guess after spending far too much on a printer to do such things that doesn't, I'll be driving down and PAYING someone to scan to pdf.  Thanks Cannon, it's been fun.

And yes, I've installed the MS Scan Utility.  Some installs literally did nothing after starting from the provided shortcut.  The latest, downloaded from your support page for the imageCLASS MF462dw II, is currently claiming there is no supported software driver installed.  I've never seen a bigger mess of a product...

[fed-up-user]

Thanks for the help, but I don't want to waste more of your time (or mine).  I seriously may just trash this thing and buy something, anything, NOT Canon.

Another Edit: I just realized I didn't answer about the VPN.  Not to try further on my problem, but to provide you another point of reference for whatever it may be worth, but I'm not running a VPN (nor have I ever) on the system in question.

I'm VERY reluctant to install anything on my phone.  Every freaking everywhere you go someone is pushing "Apps" on you like it's going to change your world.  And everyone I know who does has endless problems (much like this!!!) with their phones.  I don't install any apps but those **I** want for *my* purposes and convenience.  I refuse to install any others for any reason.

That said, I had a similar idea earlier and was planning to try it when I got a chance.  Crazy day (12 billable hours), but I finally got a chance to try it.  I fired up a VM that never had Canon anywhere near it.  Same problem, almost.  On this one, it didn't find the scanner with it's scan, so I tried entering the IP address.  But now it won't let me enter values at all.  Gives the "invalid input" ding.  Canceled and re-clicked the button to redisplay multiple times, same result.  Tried numbers at top of keyboard, and num pad, same problem.

Edit: I restarted the whole ScanGear installer, and this time after failing it's scan, it DID let me enter numbers this time, but still "no device found".  100% no doubt, that's buggy software period, and likely the root problem you've been helping me with.  I'm glad you have had good service with Canon, but I'm at 50% with 1 being perfect and 1 starting DOA and it's replacement being only partially functional.  And of course you can't reach anyone with Canon for help.  Canon won't see any more of my money... period.

With your help, I'm 99% certain it's not my network, and you helped sort out "what do I need" software issues that shouldn't exist (Canon at fault 100%).  Firewalls are off.  I'm convinced that after the first DOA I have a defective replacement unit too, or their software is just that much garbage.  Could go either way after not being able to enter numbers in the IP entry UI.  

Either way, this makes 3 significant efforts to resolve this so far.  This is the most detailed with your help, so thank you again.  But I think I'm 100% done with Canon at this point.  I've burned enough time to have bought an HP, which is likely where I'm going in the next few days.  It's gotta be something like 6 hours total now, and still I had to go somewhere else to do what I bought this to di.  I have enough to do with my business and life without having to debug busted Canon crap.  That VM test with the SAME problem AND the IP entry busted is the final straw.

[shadowsports]

Greetings, 

I absolutely understand how you feel.  Long ago my parents taught me the importance of placing value on one's time.

Once you exceed the reasonable and or customary threshold it's costing you money.  As I said I'm really sorry that you're not having any luck with both printers.  Shoot me a PM and let me know how things work out for you.  

[DerrickL]

Have you considered using a USB/printer cable and bypassing the wireless altogether? A cable makes a great troubleshooting tool. I owned a computer networking/telephone company for 25 years. We told all our customers to avoid wireless printing (the printer wireless, it was always wired,  not laptops or tablets) like it was the plague. 

[fed-up-user]

Thank trying to help on my behalf.  But after trying a second system untouched by Canon (I was leaning into some conflict with that device that won't uninstall) with the same result, I've given up.  I think it's possible that the replacement unit is also defective, just not as bad as the first.  And being out of return window, and getting nowhere with contacting Canon for tech/customer support (THERE IS NONE), the most likely path is an "Office Space" event and a replacement that is absolutely NOT Canon in the near future.

I have considered it, but sought out and bought wireless networked for a reason.  I limited my options AND paid extra for this very feature. From my desk to where the printer sets is very visible and in the open, there would be no option except exposed wires on the floor or dangling in the air.  To do otherwise would require a very long (beyond spec) USB cable, and I don't feel like trying to deal with that too.  I could reasonably patch the ethernet to my router, but there no indication that the problem is networking (especially with all of Rick's help in testing it), particularly since printing and scan from face plate TO computer work.  I'm pretty sure we are either looking at a bug in that Scan software (100% buggy given the input error "dings"), or something broken in the Canon MF that is not answering the connection handshake.  And neither appear to have solutions.