Sharp copier hell

[HCHTech]

I am trying to get an older Sharp MX2620N copier (=SMB1 only) to scan to a network folder without success. It's a small workgroup consisting of 5 Win10 Pro laptops and a single Win11Pro computer (a Lenovo Tiny resident on their network shelf) to hold the very small amount of local data and a shared folder for their scanning. Everything is new (including computers, wiring, patch panel & switch) except this busted-a$$ copier. All computers can access the shared folder on the Win11 box just fine, but no dice for the stupid copier. It is being replaced, but the new unit doesn't arrive for 3 weeks and I'm trying to make this one work in the interim. I've enabled SMB1 on the Win11 box. I've created a special user for the copier on the shared computer, I've checked permissions over an over. I've tried using an administrator user for the credentials. I can access the folder with a laptop plugged into the same patch cable as the copier, so I know it's not wiring. It's old hardware vs. new, and I'm about to give up. The copier worked just fine at the old location with 30 year old wiring and an old 2012 server (now gone in favor of Sharepoint), and it's at the latest available firmware.

I punted the ball into the court of the folks servicing the copier, but they are saying "it's your network". The fact that a laptop connected to that same wire works fine makes me disagree with that sentiment. The error messages and logs on the copier are not verbose enough to give any particular clue as to the problem. I don't think there is any hope of getting this thing connected to Office365, although I did spend a little time trying that - unsuccessfully. So, how was your day?

I've got them scanning to a flash drive for now. They don't love it, but it works.

Does anyone know any secret Sharp incantations I can chant?

 

[NviGate Systems]

The only thing I can think of is to repurpose an old PC to run as a intermediary. Something that runs a version of Windows that can connect to the copier. Then simply share that folder. Newer machines will use new protocal, Copier will use SMB1. Not pretty but it works as I assume they have no intention of replacing the copier.

If Raspberry Pi weren't so expensive or out of stock, a Pi Zero with a HAT could do this easily.

 

[timeshifter]

Might be able to scan to FTP or SFTP. Think I worked around a similar problem that way once. I feel your pain though. Just about every site that has a unit like this is always a challenge.

Maybe scan to email, but that's a can of worms you may not want to open up. Consider yourself lucky that they want to scan to a folder. A few of mine insist on scanning everything to their own email address and managing it with their email program - yuck.

Like the dedicated PC idea too.

 

[Markverhyden]

Might be able to scan to FTP or SFTP. Think I worked around a similar problem that way once. I feel your pain though. Just about every site that has a unit like this is always a challenge.

Maybe scan to email, but that's a can of worms you may not want to open up. Consider yourself lucky that they want to scan to a folder. A few of mine insist on scanning everything to their own email address and managing it with their email program - yuck.

Like the dedicated PC idea too.

Yep. FTP should work fine. I've used that even on new machines where the OEM was less than enthusiastic about getting a scan to network share to work properly. Like so many other things it's not their problem, it a problem with the network, end point, etc. I use Filezilla server for that.

 

[YeOldeStonecat]

I'd "scan to email". Or if they're on 365 and using Teams/Sharepoint for file storage, just create a channel for scans...setup the power automate to save the attachments to the document library in that channel.

Workgroup where the scanner is trying to hit a workstation...you have that going to an IP instead of host name? Could be name resolution issues.

 

[mikeroq]

Yea I've done the scan to FTP a few times. One of note was a customer with a Xerox copier. It had frequent issues with SMB and they went through multiple copiers due to other issues (sometimes different model, couple times same model). So at the time I just setup a filezilla FTP server. Then each copier replacement or repair (they had the "mainboard" replaced a couple times) I would just put in the FTP settings and off they went. When I replaced their "server" with a real one I switched to setting up the FTP server in IIS.

Here at work we have Sharp copiers. They should be new enough for SMB2 at least. Everyone just scans to email pretty much. I do have the copier closest to me setup to scan to the server.

 

[Blues]

Yeah best solutions are FTP or an old PC with more compatible OS.

 

[YeOldeStonecat]

Problem with SMB1 is....now your LAN is frighteningly susceptible to exploits that self spread across outdated/unpatched LANs.

Sometimes a firmware update can be applied to the old MFP to add SMB2 or even 3 support.

 

[nlinecomputers]

I would go with FTP. As stated SMB1 is a security risk even behind a firewall. And setting up a "new" pc just for a few weeks seems to be a waste of time and money. Filezilla server is free and easy to set up and can live on that Win11 box.

 

[thatdude]

Yeah, old Copiers and even some of the newer ones can take forever to set up for network scanning. Some things you may have already tried but I’ll still mention below:

• The “account” you are entering into the Copier. Don’t just enter the name “Copier” or whatever you created enter in COMPUTERNAME\accountname. I know you’re not on a Windows domain but I’d try that.
• Completely disable the Windows Firewall on the Win 11 computer you’re scanning to. This may not be permanent, but it removes the possibility of a something in the Windows Firewall blocking the connection from the copier. If it works after disabling the Firewall you need to find out what ports or apps to open up so it can get through. It could be enabling SMB 1.0 within Win 11 needs some other firewall exception. I know that wasn't the case in Win 10 but maybe that's it.

Keep in mind, as others have mentioned there is an ancient Sharp at one office we manage. There are no SMB options just FTP and that’s how we had to set it up.

As far as @YeOldeStonecat comments with “scan to email” I wouldn’t waste your time with that. If the copier is as old as you say it is that’s gonna be way tougher than just setting up an FTP Server on the Windows 11 box. Like Windows M365 doesn't play well with old hardware.

One last question, are you lucky enough within the Sharp GUI to have a “Test connection” button so you can test the connection instead of physically scanning something. Meaning, can you do all this remotely?

 

[Markverhyden]

One last question, are you lucky enough within the Sharp GUI to have a “Test connection” button so you can test the connection instead of physically scanning something. Meaning, can you do all this remotely?

A lot of old systems like that have very limited GUI's. Add to that you may not have all the control panel functions available via the GUI. I'm lucky one customer just got a replacement Ricoh IM C2500 which has an option to drive it from the touch screen control panel. So between the two I can do everything.

 

[mikeroq]

One last question, are you lucky enough within the Sharp GUI to have a “Test connection” button so you can test the connection instead of physically scanning something. Meaning, can you do all this remotely?

One simple feature every WEB UI needs for scan to SMB/FTP/Email/etc. I've seen it only a few times.

 

[timeshifter]

One simple feature every WEB UI needs for scan to SMB/FTP/Email/etc. I've seen it only a few times.

Same here. But when they have it it is awesome.