Ricoh MP C4000 - Scan to Folder issue

[esabet]

Hi;

I working on a Ricoh MP C 4000 machine in an office with three Windows 10 PCs on the network and trying to utilize the Scan to Folder option. I have been successful with two of the PCs on but I am having no luck with the third one.

When I attempt to connect to that one PC I get the error "Cannot find the specified path. Please check the settings."!!! I have tried both through programming the address book and doing manual entry and the same error.

BTW, I have used the Ping command through the network Interface Setting of the unit and I get success.

Anyone knows what may be the issue?

[eccelobo]

Hi;

I working on a Ricoh MP C 4000 machine in an office with three Windows 10 PCs on the network and trying to utilize the Scan to Folder option. I have been successful with two of the PCs on but I am having no luck with the third one.

When I attempt to connect to that one PC I get the error "Cannot find the specified path. Please check the settings."!!! I have tried both through programming the address book and doing manual entry and the same error.

BTW, I have used the Ping command through the network Interface Setting of the unit and I get success.

Anyone knows what may be the issue?

I know what you mean, I've fought a lot with scan to folder in W10, and at last I've choose the less traumatic way via FTP with Filezilla Sever. I recommend you do the same.

Enviado desde mi SM-G920V mediante Tapatalk

[esabet]

I know what you mean, I've fought a lot with scan to folder in W10, and at last I've choose the less traumatic way via FTP with Filezilla Sever. I recommend you do the same.

Enviado desde mi SM-G920V mediante Tapatalk

But how is it possible that I have success with two of the PCs on the network, BOTH running Windows 10 as well? That is just too strange???

[guitar9199]

It's likely the 2 you were successful on have Network Discovery and File and Printer Sharing enabled....while the other doesn't. Check their network connection type...if the bad one is set to "Public" for the network, that'll block discovery.

You may also need to make sure the IPv4 protocol on the computer is set for "NetBIOS over TCP/IP" instead of "NetBIOS over DHCP". That'll mess up SMB scans as well.

Good luck.

[slimslob]

1. Primary DNS is not correct.
2. Domain name or work group name is not correct.
3. Name and password being used does not have permission.

Might be minor spelling errors. 2 & 3 are case dependent

[mincopier]

The non-working PC may also have SMB V1 disabled. If so you may need to either enable it or got the FTP option. To check goto Control Panel, Programs and Features, Turn windows features on and off, scroll until you see SMB V1. Put a check the box and reboot. Keep in mind that by enabling SMB V1 you may expose the computer to unwanted Malware. SMB V1 is being phased out in favor of SMB V2/V3.

[esabet]

It's likely the 2 you were successful on have Network Discovery and File and Printer Sharing enabled....while the other doesn't. Check their network connection type...if the bad one is set to "Public" for the network, that'll block discovery.

You may also need to make sure the IPv4 protocol on the computer is set for "NetBIOS over TCP/IP" instead of "NetBIOS over DHCP". That'll mess up SMB scans as well.

Good luck.

The non-working PC may also have SMB V1 disabled. If so you may need to either enable it or got the FTP option. To check goto Control Panel, Programs and Features, Turn windows features on and off, scroll until you see SMB V1. Put a check the box and reboot. Keep in mind that by enabling SMB V1 you may expose the computer to unwanted Malware. SMB V1 is being phased out in favor of SMB V2/V3.

RESOLVED...... Thank you both. The solution was as follows:

1- Enable "NetBIOS over TCP/IP" AND
2- Enable SMB V1

Both were required, one without the other wouldn't work.

BTW, The Public setting was not the issue. The other two PCs were also set to Public. Although it was set to Public, Network Discovery and File and Print Sharing were both enabled for all machines.

Once again, THANK YOU!!!

[copier tech]

Interesting as i've never had to change this setting from default on multiple Win 10 installations.

My laptop is set as following & scans via SMB fine.


net.JPG

[bsm2]

Turning SMB V1 back on you may expose the computer to unwanted Malware. Turning this on ANY customers PC opens you and your company for legal problems down the road. As this was a MS security update NOT Recommended

Used filezilla server or scan to email or update firmware on machine to support smb 2 or 3


Windows 10 tip: Stop using the horribly insecure SMBv1 protocol | ZDNet

Most likely after a future MS 10 update that feature as well as smb1 will be removed and permanently disable

[esabet]

Interesting as i've never had to change this setting from default on multiple Win 10 installations.

My laptop is set as following & scans via SMB fine.


net.JPG

I will check the other two PCs on the network and most likely you are 100% correct. I never touched the default settings on the other two PCs and they are both running Windows 10 as well. Taking this one step further I don't even think SMB V1 was ever enabled on those PCs either and they are working flawlessly.
I will revisit and post an uodate as to my findings.

Sent from my SM-G955U using Tapatalk