Ricoh Copier Scan to folder SMB issue

Ricoh have issues with Vista, windows 7,8 and 10 when it comes to sending scans to a folder. You can either send to Email or fix the issue with SMB.

Microsoft decided a few years ago to turn off SMB1.0 for security reasons and moved everyone to SMB2. This means if your MFC hasn't had a firmware update for a while, the liklihood is that you now can't send a scanned file to a networked pc.


Luckily you have 2 options.

Option1: Enable SMB1.0


Go to Control Panel | Programmes and Features | Turn Windows features on or off | Tick SMB 1.0/CIFS Client and SMB 1.0/CIFS ServerOption2: Stick with SMB2 and update your MFC



Update Ricoh or Copier Firmware (usually through copier service company)



Download, install and open Putty
Choose TELNET and insert the Ricohs IP address and connect
username: Admin
Password: usually blank



msh> smb client auth
(This Displays the current SMB setting)
0 value = SMB1.0 client uses NTLM/LM authentication
1 value = SMB2.0 client uses NTLMv2/NTLM/LM authentication.



msh> smb client auth 1
(This Enables NTLMv2 /smb2)



msh> logout
(Saves data)




Changing the Port in-case firewall is blocking



msh> smb client port



-Displays the current port



msh> smb client port #



Change port number by replacing hash with number



139 (default)



445 SMB client uses port

msh> logout
-Saves data


Check and enable SMB Version on Windows 8.1, Windows 10, Windows 2012 R2, and Windows Server 2016

Detect:

Get-WindowsFeature FS-SMB1

Disable:

Disable-WindowsOptionalFeature -Online -FeatureName smb1protocol

Enable:

Enable-WindowsOptionalFeature -Online -FeatureName smb1protocol

SMB v2/v3

Detect:

Get-SmbServerConfiguration | Select EnableSMB2Protocol

Disable:

Set-SmbServerConfiguration -EnableSMB2Protocol $false

Enable:

Set-SmbServerConfiguration -EnableSMB2Protocol $true



Also useful is check SMB Configuration is correct



We had a client with EnableAuthenticateUserSharing set to true, this means the copier will need to provide a user and password to access the share, which it can't handle.



msh>Get-SmbServerConfiguration



AnnounceServer : False
AsynchronousCredits : 64
AutoShareServer : True
AutoShareWorkstation : True
CachedOpenLimit : 5
AnnounceComment :
EnableDownlevelTimewarp : False
EnableLeasing : True
EnableMultiChannel : True
EnableStrictNameChecking : True
AutoDisconnectTimeout : 0
DurableHandleV2TimeoutInSeconds : 30
EnableAuthenticateUserSharing : False
EnableForcedLogoff : True
EnableOplocks : True
EnableSecuritySignature : False
ServerHidden : True
IrpStackSize : 15
KeepAliveTime : 2
MaxChannelPerSession : 32
MaxMpxCount : 50
MaxSessionPerConnection : 16384
MaxThreadsPerQueue : 20
MaxWorkItems : 1
NullSessionPipes :
NullSessionShares :
OplockBreakWait : 35
PendingClientTimeoutInSeconds : 120
RequireSecuritySignature : False
EnableSMB1Protocol : True
EnableSMB2Protocol : True
Smb2CreditsMax : 2048
Smb2CreditsMin : 128
SmbServerNameHardeningLevel : 0
TreatHostAsStableStorage : False
ValidateAliasNotCircular : True
ValidateShareScope : True
ValidateShareScopeNotAliased : True
ValidateTargetName : True
EncryptData : False
RejectUnencryptedAccess : True



Here is an example of how to turn off a feature:

Set-SmbServerConfiguration -EnableAuthenticateUserSharing 0
We love ESET Internet Security
CCleaner Registry Cleaner multiple errors in Sage ...