


I may be missing something but I disabled the firewall completely to check if that was the issue but it unfortunately didn't change anything. The Ricoh was set up previously, what killed the connectivity was our new computers. Wasn’t about to question it or poke the beast. I left it at that and counted it as a win. SMB 1 was already enabled in windows features. On the host system, somehow port 139 was blocked even though everything else on the system checked out as it does everywhere else I’ve been. I’ve only had one scenario where this worked on a machine that only supported SMB 1. One last thing I can suggest….try switching the port on the mfp to use 445. Also verify that the same scan account is listed under security with the right permissions.


I’ll usually take it a step further and re-share the folder using advanced sharing and add the scan account there too. Folder is shared, explicit read/write permissions for scan account. Other than that I can’t say I’ve run into many issues outside of compatibility of firmware. I’ve had some third party security still interfere even with these rules and it only worked when disabled. You have to create rules to allow the correct tcp port inbound in order for it to work. I’ve had 3rd party and built in windows firewall occasionally cause issues. Is the network the machine is connected to flagged as a private or domain network? If it’s flagged as a public network that will cause issues. Does anyone have any experience with windows 11 and Ricoh machines? To confirm my own suspicions I used the scan to folder program on an older windows 10 machine we had in the back, and it worked first try with no issues. I've made sure it's not a firewall issue. I've made sure I shared the scan folder properly. I've made sure printer and file sharing is enabled. I've made sure background sharing processes are running. I've double and triple checked to make sure I'm entering the credentials correctly but it's still not able to send files to my computer. The program tells me it's possibly an authentication error and asks me to confirm the user password. I've gone through the exact same manual steps I always do to set up scan to folder on our previous machines and even found a program from Ricoh I've never seen before that automated the process but nothing's worked. To start, I know my computer and the printer can see each other since I'm able to access the web interface and I'm able to ping my computer's ip from the printer successfully. At this point I'm figuring it's an OS incompatibility but I thought I'd ask around here before giving up. So the other day my small office got new windows 11 computers to replace our aging hardware and I'm having quite the time trying to set up scan to folder like our previous hardware had. I apologize if this is the wrong sub but it seems like it fits here.
