ImageCLASS MF455DW - Scan to Shared UNC Path Folder

[ewade]

I am working on setting up an ImageCLASS MF455DW for a small business.

They host their files on a network shared server (we'll call it "Server01"). Runs Windows Server 2022.

I'm going in to set up destinations in the Address Book via the Remote UI. But I cannot get it to scan to the shared folder. Before we get in the weeds:

1. The folder is Shared and accessible, and the Username used below has "Modify" access
2. The printer is on the same LAN Network
3. Shared Folder is NOT on the C:\ Drive (we'll call it the "D:\" Drive)

• Protocol: Windows (SMB)
• I put the server name in the "Host Name" ("Server01")
• Added a Username and Password. (domain\user format)
• for the Folder Path I have tried multiple methods
  • UNC Path (\\Server01\folder\scan)
  • Drive Path (D:\folder\scan)

however, I continually get error 804 - Folder cannot be found or I don't have rights to the folder.

I can't for the life of me figure out why this isn't working. I have set up multiple other multifunction brands in a similar manner (typically with a login credential saved and the UNC Path), even to the folder I am trying to set up with this printer.

Any help would be appreciated.

[ewade · Accepted solution]

Face-palm Moment.

all I had to do was remove the Drive/UNC from the Path and use (folder\scan) as the Folder Path and it worked fine.

Leaving this open for the next sorry soul who tried to over-define their Folder Path.

Cheers,

[Stephen]

Hello!

I'm not a tech, just a bit of a nerd. Instead of the UNC path, maybe try with Server01's IP address. The online manual indicates that is the proper way to do it. Check it out HERE.

[ewade]

Thanks - I was able to find my own solution. 😥

I was over-definiting the Folder Path (out of habit) and was either specifying the UNC Path or the Path with a Drive Letter.

However, when I removed these (using "folder\scan" instead of "D:\folder\scan" for example), it worked fine.

Which, is exactly what the documentation says to do, which I feel a bit foolish on. I guess I'm too used to having to overdefine a file location in other aspects of my job, else it goes to some other weird location.

Thanks again for the reply! Very fast.