MP C2003 Can scan to WIN 10 Home but not WIN 10 Pro

[luca72]

Re: MP C2003 Can scan to WIN 10 Home but not WIN 10 Pro

Would this be resolved by a firmware upgrade? Got 2 PCs scanning to Home with no problem but getting an authentication error for 3 Pros.

1) check the firmware version (!!!)

2) check in the system registry in WIM, under "configuration" the exact error encountered by the controller during the comunication, in the registry you will find the solution for sure

p.s. do you have enabled SMB client, in windows andvanced features?

[keithxxiii]

Re: MP C2003 Can scan to WIN 10 Home but not WIN 10 Pro

Hello? Anybody out there?

Yep!

I would suggest keeping this points whenever doing scan to a folder.

If DNS is present - and does successful connection test - configure using hostname of the PC/Server with domain user to authenticate
If no DNS - configure using IP address with local user to authenticate

[dalewb74]

Re: MP C2003 Can scan to WIN 10 Home but not WIN 10 Pro

Yes update the firmware if you're still having issues as there was a security release for this model enabling SMB 2/3 support.

i agree as the firmware update gives you a checkbox that enables smb 2/3. make sure you get the correct one for the model. have used it in the past and it usually fixes scanning issue.

[patterson70]

Re: MP C2003 Can scan to WIN 10 Home but not WIN 10 Pro

i agree as the firmware update gives you a checkbox that enables smb 2/3. make sure you get the correct one for the model. have used it in the past and it usually fixes scanning issue.

I greatly appreciate all the information. I had or have tried all of these suggestions. It was always an authentication issue and what I found is that you can scan to Windows Home with a PIN but not PRO. I have seen this at two different accounts.
So I set up a new local user with a password (as someone had suggested - thank you as well), created a scans folder, shared it out, and success!

By the way, I could not change from a pin back to the Microsoft password the user originally created because he lost it and it was a major to-do to reset the password with Windows and get rid if the PIN. He also had forgotten his back-up email address.

[kplow1986]

Re: MP C2003 Can scan to WIN 10 Home but not WIN 10 Pro

This is very bad advice: there are multiple security issues with SMB1 and if you turn it on and a customer gets hit with an vulnerability related to it that falls on you.

This model supports SMB3 with firmware updates as has been noted already.

Most of the issues with scanning on non-domain Windows machines come down to the person being signed in with a Microsoft account as opposed to a local account. It's often best to create a local account for scanning, even if it's not the one the user logs into the computer with, as long as it has access to the share folder and the same credentials are used on the MFP it will work.

You are right ! there is a risk if windows turn on smb v1.But some old models would not support smbv2/3. This is another ways to scan if user insist to do do

[BillyCarpenter]

Re: MP C2003 Can scan to WIN 10 Home but not WIN 10 Pro

You are right ! there is a risk if windows turn on smb v1.But some old models would not support smbv2/3. This is another ways to scan if user insist to do do

SMB is Dead, Long Live SMB!




Hello again, James Kehr here with another guest post. Titles are hard to do. They must convey the topic to the reader while being both interesting and informative, all at the same time. Doing this with a technical article makes life even harder. Now imagine my dilemma when starting an article about SMB1 behaviors in modern Windows. Think about that for a minute. Go ahead. The article will still be here.

Today I'll explain why you still see a little SMB1 on your network even after you uninstalled SMB1 from Windows, and why it's a good thing.

SMB1 is Dead!

The end of SMB version 1 (SMB1) topic has been discussed in great detail by Ned Pyle, who runs the SMB show here at Microsoft. Go read this article if you have not.

• The only versions of Windows that require SMB1 are end-of-support (EOS). By years! These are Windows Server 2003 (EOS July 2015), Windows 2000 Server (EOS July 2010), their client editions, and older.

• EOS Windows versus Apple:
  • Windows 2000 was released 7 years before the first iPhone.
  • Windows 2003/XP was released 4 years before the first iPhone.
  • Apple computers were still running IBM PowerPC processors.

• • Kernel 2.2.14 was released the same year as Windows 2000.
  • Version 2.4 was the newest kernel when Windows Server 2003 launched.
  • Support for the last version of the version 2 kernel, 2.6.32, ended in 2016.

dominant and the world was still learning how high-speed Internet would impact computer security.



The real question here is: Why are you still running an OS or device that is so old it requires SMB1?

The SMB1 Problem

The biggest problem with SMB1 is that it was developed for the pre-Internet era. The first dialect came out in 1983 from IBM. Security and performance were designed for closed token ring networks and old fashion spinny disks. As EternalBlue and WannaCry would later prove, it is not a protocol that has aged well and it is no longer safe to use.

Unlike most other deprecated protocols, however, SMB1 controls the keys to the kingdom: data, services, file systems, accounts, and more. This makes SMB1 exploits critically harmful.

When Microsoft decided to retire SMB1 for real, and stop asking nicely, we tore off that band-aid by removing it completely from Windows 10 Spring 2017 Update (Win10 1703), when Windows detected that SMB1 was not in use. No SMB1 dialect was sent during negotiation, no SMB1 was allowed at all. And that broke things.



We ended up making changes to mitigate this without actually enabling SMB1.

• Windows 10 1709 (2017 Fall Update) and newer will send SMB1 dialects as part of the SMB negotiate. We do this to help interoperability with legacy devices. I.E. prevent Windows Explorer from pausing/hanging.
• We will not actually allow an SMB1 connection when SMB1 is disabled. We only pretend to. The connection will end up getting closed when the server or client tries to use an SMB1 dialect.

In addition to preventing uncomfortably long waits for Windows users, it lets us bubble up messages about SMB1 only devices on your network. System admins can look in the Event Viewer > Applications and Services Logs > Microsoft > Windows > SMBServer-Operational log for event ID 1001, which is created when SMB1 is used.

[CopyBats]

Re: MP C2003 Can scan to WIN 10 Home but not WIN 10 Pro

Try using Ricoh scan to folder setup tool next time

First time in my life as a tech Ricoh put something out there that is actually useful

[sandmanmac]

Re: MP C2003 Can scan to WIN 10 Home but not WIN 10 Pro

Try using Ricoh scan to folder setup tool next time

First time in my life as a tech Ricoh put something out there that is actually useful

That's actually pretty cool.
Just downloaded it.
First I'd heard of it myself.
Thanks for the tip!

[tsbservice]

Re: MP C2003 Can scan to WIN 10 Home but not WIN 10 Pro

Interesting. Was going to ask someone to share this but found it here:
Scan to Folder Configuration Tool Downloads | Ricoh Global
Now I have a couple of questions before I can play with it.
-Is this the right tool?
-Will it works with other brands?
Some good soul care to enlighten me

[BillyCarpenter]

Re: MP C2003 Can scan to WIN 10 Home but not WIN 10 Pro

Interesting. Was going to ask someone to share this but found it here:
Scan to Folder Configuration Tool Downloads | Ricoh Global
Now I have a couple of questions before I can play with it.
-Is this the right tool?
-Will it works with other brands?
Some good soul care to enlighten me

Kyocera has a scan tool. I used to use it all the time but I've found I can do it just as fast the old fashioned way. The reason Kyocera develped the scan tool is that the customers found it too difficult to set up scan to folder.

[CopyBats]

Re: MP C2003 Can scan to WIN 10 Home but not WIN 10 Pro

Kyocera has a scan tool. I used to use it all the time but I've found I can do it just as fast the old fashioned way. The reason Kyocera develped the scan tool is that the customers found it too difficult to set up scan to folder.

This one takes care of the windows sharing settings issues. So far I've found it to make it much simpler.

Ricoh address book isn't the best and this takes care of it all.

[CopyBats]

Re: MP C2003 Can scan to WIN 10 Home but not WIN 10 Pro

Interesting. Was going to ask someone to share this but found it here:
Scan to Folder Configuration Tool Downloads | Ricoh Global
Now I have a couple of questions before I can play with it.
-Is this the right tool?
-Will it works with other brands?
Some good soul care to enlighten me

Yes it's the right tool. Don't know if it'll work for other brands but it can get the folder ready for sharing

[BillyCarpenter]

Re: MP C2003 Can scan to WIN 10 Home but not WIN 10 Pro

This one takes care of the windows sharing settings issues. So far I've found it to make it much simpler.

Ricoh address book isn't the best and this takes care of it all.

Understood. When I first learned how to set up a shared folder I used the scan tool all the time. After setting up a scan folder for about the 1000th time, I just prefer to set it up manually. It probably does save a little time using the scan tool, though.

[tsbservice]

Re: MP C2003 Can scan to WIN 10 Home but not WIN 10 Pro

Yes it's the right tool. Don't know if it'll work for other brands but it can get the folder ready for sharing

Thanks CopyBats. I have script doing this plus creating user for MFP to write in shared folder but it's always better to have plan B.

[sandmanmac]

Re: MP C2003 Can scan to WIN 10 Home but not WIN 10 Pro

This one takes care of the windows sharing settings issues. So far I've found it to make it much simpler.

Ricoh address book isn't the best and this takes care of it all.

Agreed.
In my first couple test runs, it does it all. No need to even open the WIM.
Not that I've not had many issues doing it the 'old fashioned way', but I'd say this is even faster than doing it that way, and something I can offer some clients to do themselves, when they want to make changes/ additions.

Whatever the case, it's a good additional tool for the toolbox