Ricoh MPC6003 SMB 2.0

[Kenny]

HI guys,

does anyone ricoh mpc6003 firmware to enable SMB 2.0 for the machine, got a customer trying to set up scans to folder on their server, tested the machine on a pc with SMB 1.0 and works.

and a guide on how to install this, hardly use these machines

[Kenny]

or can i just use this?

RICOH Firmware Update Tool Downloads | Ricoh Global

[emiliorsg]

It has been supporting smb v2 for several years now. Check that the firmware version is higher.
Newly added SMBv2/v3 support.
This firmware is dependent on the following firmware modules.
Please be sure to update all of them:

System/Copy v1.33 (D1495569J)
Network Support v12.74 (D1495567T)
Web Support v1.07 (D1495561R)
Scanner v01.13 (D1495560Q)
OpePanel
- Europe, China, and Taiwan model: v1.14 (D1491490Q)
- NorthAmerica, Asia and Koria model: v1.10 (D1501438J)

Please refer to the RTB(No.RGene095) for details.

[Kenny]

It has been supporting smb v2 for several years now. Check that the firmware version is higher.
Newly added SMBv2/v3 support.
This firmware is dependent on the following firmware modules.
Please be sure to update all of them:

System/Copy v1.33 (D1495569J)
Network Support v12.74 (D1495567T)
Web Support v1.07 (D1495561R)
Scanner v01.13 (D1495560Q)
OpePanel
- Europe, China, and Taiwan model: v1.14 (D1491490Q)
- NorthAmerica, Asia and Koria model: v1.10 (D1501438J)

Please refer to the RTB(No.RGene095) for details.

Ricoh Firmware Details.jpg

i have used the update tool and this is what i have got,

how to i enable the smb2?

[Kenny]

does anyone have the firmware i require for it, the update tool doesnt say it needs an update

[TonerMunkeh]

Can you print off and scan in a Diagnostic Page, SP5990-005.

[KenB]

does anyone have the firmware i require for it, the update tool doesnt say it needs an update

I know the RFUT does not work with the MP C4503, so it makes sense that it doesn't work with the 6503, either (same group).

That tool is junk, at least as far as I'm concerned.

[rthonpm]

I know the RFUT does not work with the MP C4503, so it makes sense that it doesn't work with the 6503, either (same group).

That tool is junk, at least as far as I'm concerned.

There have been updates to the tool and both of those models are now supported.

RICOH Firmware update tool : Model List | Global | Ricoh

The tool does require a few background services like FTP to be enabled to properly, which can be enabled from the web interface. This is not the scan to FTP function, but rather the ability to communicate to the device via FTP.



Sent from my Pixel 6 Pro using Tapatalk

[KenB]

There have been updates to the tool and both of those models are now supported.

RICOH Firmware update tool : Model List | Global | Ricoh

The tool does require a few background services like FTP to be enabled to properly, which can be enabled from the web interface. This is not the scan to FTP function, but rather the ability to communicate to the device via FTP.



Sent from my Pixel 6 Pro using Tapatalk

Are you sure it works with those models?

It has claimed to all along, but doesn't. I beleive it will update the Java, but not the rest of the machine.

I have been told that models which offer both the NOP and SOP panels (as these 2 models do) don't work because the tool can't tell the difference between them, and we all know what happens when the wrong version gets applied.

I have a herd of MP C4503s where I had to use the firmware packaging tool to build a package containing all the files (I think there were about 20) and then distributed it using SLNX.

[slimslob]

Are you sure it works with those models?

It has claimed to all along, but doesn't. I beleive it will update the Java, but not the rest of the machine.

I have been told that models which offer both the NOP and SOP panels (as these 2 models do) don't work because the tool can't tell the difference between them, and we all know what happens when the wrong version gets applied.

I have a herd of MP C4503s where I had to use the firmware packaging tool to build a package containing all the files (I think there were about 20) and then distributed it using SLNX.

It hasn't worked with a lot of model all along. It tended to crash and leave you with a dead machine if you didn't have a recovery SD.