Attached is the firmware history for the MP C3002/MP C3502. See items corrected by Network Support Firmware v 11.96. This is an example of when Ricoh USA updated firmware in order to scan to Windows 8/Server 2012(SMB v3).MP CXX03 SMB v3.Attachment 36627
If the pc or server has a static IP then try this and see if it works, I was told this only works when scanning via IP.
If the computer(or server) has an ip of 192.168.1.10 and the path is public\scans then put the path as follows:
\\192.168.1.10:445\public\scans
Also make sure that the pc/server is on a Private/work network in the Network and Sharing center.
And Star Trek was just a tv show...yeah right!
I am able to toggle off SMB1 on the server while I've been testing.
https://support.microsoft.com/en-us/...ws-server-2012
I have experimented with the various telnet SMB settings on the Ricoh machine
I had the Ricoh C6004 working with
client auth 3 (NTLMv2 Only)
client port 445
But as soon as I turn off SMB1 on the server itself, scanning fails again.
SMB v1 Windows Server 2000 / 2003
SMB v2 Windows Vista / Server 2008
SMB v2.1 Windows 7 / Server 2008 R2
SMB v3 Windows 8 / Server 2012
SMB v3.0.2 Windows 8.1 / Server 2012 R2
SMB v3.1.1 Windows 10 / Server 2016
Up to SMB v2.1 Windows would automatically negotiate which version of SMB to use for communication. (hence it would drop down to SMB v1 as required).
Then from SMB v3 they included the option to add backwards compatibility via add and remove Windows features (SMB 1.0 / CIFS File Sharing Support).
But your findings are the same as my findings.
Turn off SMB 1.0 / CIF and it will stop working.
So that makes Ricoh correct, they do just use the SMB v1 protocol.
The real question is does SMB v1 actually need to be turned off now?
If the customer has applied the latest Windows updates then the vulnerability has already been plugged.
Any help??? RD062011m.pdf
Bookmarks