Scan to to folder/scan to email (mp 6001)

[sharpmind]

After upgrading from Windows Server 2008 to Windows Server 2016, the scan to folder suddenly not working. There is no new firmware update available in my-ricoh.com. Have you faced this kind of problem and how did you resolve it?

FTP scanning using filezilla server is unacceptable to IT administrator due to network security issue.

I tried to configure scan to email using smtp.gmail.com as SMTP server, port 465, DNS (8.8.8.8/8.8.4.4, but it fails.

Have you any idea on how can I configure scan to email using free mail server?

Please help.

[guitar9199]

For scan to email using Gmail, try using port 587 instead.

if you have access to the TSRC, there is a bundled firmware update for SMB v2/v3 available. I didn't see any update for SSL/TLS encryption so your Gmail scan MIGHT be dead in the water.

http://rfg-esource.ricoh-usa.com/ora.../rfg079199.zip

[slimslob]

You can always update the customer to a new multi function that supports SMB v2/v3 for scan to folder and TLS for email.

[sandmanmac]

After upgrading from Windows Server 2008 to Windows Server 2016, the scan to folder suddenly not working. There is no new firmware update available in my-ricoh.com. Have you faced this kind of problem and how did you resolve it?

As stated, while there is in fact F/W available to resolve the issue for scanning to folder (I don't think you'll have the same luck scanning via Gmail)
Having said that, It grinds my gears when companies decide to make the investment to update their systems, and when their 10 year old machines don't work the same afterwards- because the 'new system' uses a protocol that DIDN'T EVEN EXIST when their copier was manufactured, yet somehow it's still our fault!
(end of short rant )

[copier tech]

As stated, while there is in fact F/W available to resolve the issue for scanning to folder (I don't think you'll have the same luck scanning via Gmail)
Having said that, It grinds my gears when companies decide to make the investment to update their systems, and when their 10 year old machines don't work the same afterwards- because the 'new system' uses a protocol that DIDN'T EVEN EXIST when their copier was manufactured, yet somehow it's still our fault!
(end of short rant )

Worse still they book a call for not scanning but "forget" to mention they've upgraded their server simply telling you 'it just stopped working one day'

[KenB]

All of which should be billable time.

Yeah...right.

[mincopier]

This has worked in the past for some machines. Be sure to have the firmware updated. This is all done in a Telnet session.

msh> smb client auth
-Displays the current setting
msh> smb client auth 1
-Enables NTLMv2
msh> logout
-Saves data

Setting value	Result
0 (default)	SMB client uses NTLM/LM authentication.
1	SMB client uses NTLMv2/NTLM/LM authentication.

Authentication level setting: The device will use only one protocol with the priority that is the highest among the available protocols. The priorities are listed in the table below. The device cannot switch between them automatically.

Priority	Authentication
Level 0 (default)	Level 1
High | Low	NTLMv1	NTLMv2
LAN Manager	NTLMv1
Plain Text	LAN Manager
N/A	Plain Text

The SMB port can be changed via Telnet:
msh> smb client port
-Displays the current setting
msh> smb client port #
-Change port number

Setting value	Result
139 (default)	SMB client uses port 139 port
445	SMB client uses port 445 port