Savin 9025 Scan SMB to Server 2016?

[ChrisG]

Local customer updated their system to Server 2016. Their I.T. guys are asking if it's possible for the Savin 9025 to scan to the server via SMB without opening the SMB 1.0 ports? As we're no longer a Savin dealership, it's been hard to keep up on firmware updates.

Has there been any firmware patches released that might make scanning to Server 2016 possible. The last firmware update we had was when Windows 8 came out that was scanning related.

Thanks for the help
Chris
TJL Copy

[slimslob]

It has been almost 12 years since that model was first introduced. It might be too old to support SMB v2/3.

[FrohnB]

Quick answer No.

The past few months we have replaced over a dozen of these particular machines for similar issues. Plus they are getting to a point that Printing to them in certain environments is a pain.

[mincopier]

FTP would work in a pinch but as far as SMB they will need to upgrade.

[ChrisG]

Quick answer No.

The past few months we have replaced over a dozen of these particular machines for similar issues. Plus they are getting to a point that Printing to them in certain environments is a pain.

That was pretty much what I was going with. The product support guide only listed it as an option but no version so I'm not surprised by these responses. Thanks all

[Brianneoe]

Yes it is supported..

SMBv2v3
8/8/2018	D018-D020_SMBv2v3_SDcard

Keep in mind that if you do update the firmware you most likely will see a slow down on the machine when its printing and scanning at the same time. As per my answer on another post last week. This is only on older machines that did not support V2\3 from factory.

When Ricoh first came out with the new SMB V2\3 we noticed that the machines started to slow down when printing and scanning at the same time. It was explained to me that it was a limitation of the new firmware.
Writing only supports synchronous transfer, and even if set to asynchronous transfer, the device will still perform synchronous transfer.

Go figure..



2. Limitations
[COLOR=rgb(0.000000%, 0.000000%, 0.800000%)]The SMB version used for Windows authentication is SMBv1. Please use LDAP authentication instead asnecessary.[/COLOR]

• [COLOR=rgb(0.000000%, 0.000000%, 0.800000%)]- The SMB version used for SMB printing is SMBv1.[/COLOR]
• [COLOR=rgb(0.000000%, 0.000000%, 0.800000%)]- Plaintext authentication and LM authentication are not supported with SMBv2/v3.[/COLOR]
• [COLOR=rgb(0.000000%, 0.000000%, 0.800000%)]- In some environments SMBv3 encrypted communication using port 139/tcp is not supportedbecause Windows OS does not support it. The default port setting in the device has been changedto 445/tcp, so there should be no issue.[/COLOR]
• [COLOR=rgb(0.000000%, 0.000000%, 0.800000%)]- Addressing in CNAME using port 139/tcp is not supported. However, it is now supported by port445/tcp.[/COLOR]
• [COLOR=rgb(0.000000%, 0.000000%, 0.800000%)]- Writing only supports synchronous transfer, and even if set to asynchronous transfer, the device willstill perform synchronous transfer.[/COLOR]
• [COLOR=rgb(0.000000%, 0.000000%, 0.800000%)]- Regarding SMB Encryption, the device can communicate using encryption with individual sharefolders but not when encryption is enabled for the entire file server.[/COLOR]
  [COLOR=rgb(0.000000%, 0.000000%, 0.800000%)]The following PowerShell command to enable encryption for the entire server is not supported:[/COLOR]