Ricoh Aficio MP161 will not scan to network drives

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • tek3
    • May 2025

    #1

    Ricoh Aficio MP161 will not scan to network drives

    Hello,

    I am having issues with a Ricoh Aficio MP 161 Printer when scanning to a network drive using smb. I was hoping maybe someone has experienced a similar issue and could provide some insight as Ricoh's support on par with the worst I have ever dealt with. Any help would be greatly appreciated.

    First off, I am pretty well experienced with this type of issue. I have tried everything I can think of. Feel free to get as technical as need be in any replies.

    The Issue:

    Ricoh Printer gives a connection error when trying to scan to a shared drive. Does not specify on the printer's screen or in the logs what the error is.

    The Set Up:

    Without making it more complicated than it needs to be. Printer has a static ip on the network - no conflicts. I am attempting to scan to a file server on the same local area network. It is a different subnet but connectivity is not an issue - at least for everything but this printer. I get a general connection error. However, I have another HP printer here which can scan to the drive with no issues - same settings and credentials.

    I also have 3 printers in another location, same internal network, that can scan to the same smb path/folder with the same credentials. So the problem is isolated to this one device. Scans can be sent via Email using this Ricoh printer but not to the network path. For testing purposes, I am using the network admin account - which has full access rights - to rule out any odd permission errors.

    I have tried using both \\ServerName\Share\ and \\IPAddress\Share\. No difference. I cannot find any new firmware on Ricoh's website for the Printer. I don't see why it should matter but the share path is not on the c:\ of the file server. The file server can ping the printer.

    If anyone has any insight or ideas they would be greatly appreciated.
  • KenB
    Geek Extraordinaire

    2,500+ Posts
    • Dec 2007
    • 3945

    #2
    Do you have the domain name entered in the MP161?

    I've seen this cause grief before, even if you use domainname\user in the login credentials.

    You also may want to consider testing with DHCP enabled on the machine.
    “I think you should treat good friends like a fine wine. That’s why I keep mine locked up in the basement.” - Tim Hawkins

    Comment

    • zed255
      How'd ya manage that?

      1,000+ Posts
      • Dec 2009
      • 1024

      #3
      I had an account that was using the administrator account credentials to try to scan to a share on server 2003 and the connection was refused. When switching to a regular user's credentials there was no issue. We created a specific user for the machine to use and gave explicit permisssion to the folder and all was well. Something to try perhaps?

      Comment

      • KenB
        Geek Extraordinaire

        2,500+ Posts
        • Dec 2007
        • 3945

        #4
        Thanks for mentioning that, Zed.

        I reminded me that I had the exact same thing happen on an MP171 about a year ago at a school.

        Once we stopped using the admin credentials, it scanned just fine.
        “I think you should treat good friends like a fine wine. That’s why I keep mine locked up in the basement.” - Tim Hawkins

        Comment

        • tek3

          #5
          Thank you guys for the recommendations! I ended up leaving the office so I can get some sleep but will try them first thing tomorrow morning.

          I did try using dhcp. Doesn't appear to make any difference.

          The MP161 doesn't seem to have a domain option under SMB or any network settings. I have tried the user name though as domain/administrator and just as administrator. Great recommendations though.

          Thanks for the tip on the administrator account. I hadn't thought of that. All of our HP Printers have worked fine with that account so this is good to know. I had tried it without credentials but looking back that was stupid, as the drive I'm attempting to scan to is open for all users, but you still must login as a domain user. I'll give that a try first, especially since that is how the final set up will be. I normally test everything using the least complicated set up (least restricted drive, highest permissions, etc.) to ensure its working before moving onto the final configuration, which often leaves more components/settings that could cause a problem. Perhaps in this case it caused me more problems

          Anyways, thanks again, I was not expecting any replies anywhere near as fast.

          Comment

          • PinevskiS
            Trusted Tech
            • Jul 2009
            • 284

            #6
            Pleace send you mail

            Comment

            • tek3

              #7
              zed was dead on. Worked using other credentials. Does not work when using the administrator account. Thanks again for the help guys!

              Comment

              Working...