Windows server 2022 & mpc2051 - smb v2 dont work, and smb v1 instead work

[luca72]

Hi, we have this problem on a new windows 2022 server with scan to folder
the mpc 2051 (fw updated) doesn't work using smb v2 but we had to activate smb v1, I'll start by saying that I don't follow the server part, but only the machine, the mpc2051 has active smb v2 and port 445, in the wim system registry, the machine with smb v2 says "unable to connect"

do you have a ideas?

[BillyCarpenter]

Re: Windows server 2022 & mpc2051 - smb v2 dont work, and smb v1 instead work

I don't know anything about the copier but can tell you that Server 2022 supports SMB1, 2, and 3. The copier will negotiate with the server staring with the higest version and work its way down. This may help.



https://Deion's first postgame press...down? Stop it.

[luca72]

Re: Windows server 2022 & mpc2051 - smb v2 dont work, and smb v1 instead work

Anyone have a flash of genious?..lol

[rthonpm]

Re: Windows server 2022 & mpc2051 - smb v2 dont work, and smb v1 instead work

Is NetBIOS over TCP enabled on the NIC for the server? Permissions correct? SMB encryption enabled on the server or any shares?

Any additional firmware updates for the machine?

Remove the SMB 1 feature from the server and forget it ever allowed you to install it. If you need to resort to that then tell the client too bad: no scan to folder.

Sent from my Pixel 6 Pro using Tapatalk

[slimslob]

Re: Windows server 2022 & mpc2051 - smb v2 dont work, and smb v1 instead work

According to the following thread v2 is available for the C2051 using the firmware update tool. Automatic Rico Printer Firmware Update (Tested on Rico MP C2051)

[copier tech]

Re: Windows server 2022 & mpc2051 - smb v2 dont work, and smb v1 instead work

Hi, we have this problem on a new windows 2022 server with scan to folder
the mpc 2051 (fw updated) doesn't work using smb v2 but we had to activate smb v1, I'll start by saying that I don't follow the server part, but only the machine, the mpc2051 has active smb v2 and port 445, in the wim system registry, the machine with smb v2 says "unable to connect"

do you have a ideas?

Have you tried scanning to another Windows PC or your own laptop to prove the Ricoh is not the issue ?

Did you update ALL the firmware files ?

I would tell the client the MP C2051 has long since discontinued & sell them un upgrade.

[luca72]

Re: Windows server 2022 & mpc2051 - smb v2 dont work, and smb v1 instead work

Is NetBIOS over TCP enabled on the NIC for the server? Permissions correct? SMB encryption enabled on the server or any shares?

Any additional firmware updates for the machine?

Remove the SMB 1 feature from the server and forget it ever allowed you to install it. If you need to resort to that then tell the client too bad: no scan to folder.

Sent from my Pixel 6 Pro using Tapatalk

hi, the problem occurred precisely when installing this new Windows 2022 server, before it worked with the old one (my super Microsoft certified colleague takes care of it), he actually had to enable smb v1 precisely because smb 2 didn't work, but the machine It's very up to date, I checked the FW versions

[luca72]

Re: Windows server 2022 & mpc2051 - smb v2 dont work, and smb v1 instead work

According to the following thread v2 is available for the C2051 using the firmware update tool. Automatic Rico Printer Firmware Update (Tested on Rico MP C2051)

hi, I had that one used to update the machine, I wasn't at the customer's, my colleague called me because the scans weren't working, and I had him download and run RFUT, but nothing, he had to temporarily enable smb v1... however I connected remotely, and I saw that the FW versions are the latest.

[luca72]

Re: Windows server 2022 & mpc2051 - smb v2 dont work, and smb v1 instead work

Have you tried scanning to another Windows PC or your own laptop to prove the Ricoh is not the issue ?

Did you update ALL the firmware files ?

I would tell the client the MP C2051 has long since discontinued & sell them un upgrade.

hi, the 2051 half an hour before, with the old server it worked, it's after the installation of the new server with 2022 that it doesn't work, the firmware is the latest, in particular "network support 10.64", smb v2 is present, and enabled , but the colleague had to enable smb v1 because V2 doesn't work.
the car is rented, the longer you keep it, the more we earn

[emiliorsg]

Re: Windows server 2022 & mpc2051 - smb v2 dont work, and smb v1 instead work

You have an old copier for such a modern Windows. Any other protocol that Windows uses, 2051 does not have it.

[General Copiers]

Re: Windows server 2022 & mpc2051 - smb v2 dont work, and smb v1 instead work

Hi, we have this problem on a new windows 2022 server with scan to folder
the mpc 2051 (fw updated) doesn't work using smb v2 but we had to activate smb v1, I'll start by saying that I don't follow the server part, but only the machine, the mpc2051 has active smb v2 and port 445, in the wim system registry, the machine with smb v2 says "unable to connect"

do you have a ideas?

From where are you updating the firmware?
Since some months I have been updating all the machines using the Firmware Update Tool.
Some firmware downloaded from the Ricoh portal (I think we use the same one) are not really up to date.
In this way I was able to use scan to folder from MPC2051 to some Windows 10 and Windows 11 pc (I haven't had to do this on Server 2022 yet but I think it's the same...).

[rthonpm]

Re: Windows server 2022 & mpc2051 - smb v2 dont work, and smb v1 instead work

(I haven't had to do this on Server 2022 yet but I think it's the same...).

Server 2022 is the server equivalent of Windows 10 21H2.

Sent from my Pixel 6 Pro using Tapatalk

[luca72]

Re: Windows server 2022 & mpc2051 - smb v2 dont work, and smb v1 instead work

From where are you updating the firmware?
Since some months I have been updating all the machines using the Firmware Update Tool.
Some firmware downloaded from the Ricoh portal (I think we use the same one) are not really up to date.
In this way I was able to use scan to folder from MPC2051 to some Windows 10 and Windows 11 pc (I haven't had to do this on Server 2022 yet but I think it's the same...).

hi, I also noticed this thing you say, however the latest firmware available for mpc2051 are from 2018, and I remember having updated them I think max a year ago with an SD card, however as they were not present at the time of installation of the server, I had my colleague download RFUT on the phone and run it.
network support is 10.64

[UNICORNico]

Re: Windows server 2022 & mpc2051 - smb v2 dont work, and smb v1 instead work

Hi, we have this problem on a new windows 2022 server with scan to folder
the mpc 2051 (fw updated) doesn't work using smb v2 but we had to activate smb v1, I'll start by saying that I don't follow the server part, but only the machine, the mpc2051 has active smb v2 and port 445, in the wim system registry, the machine with smb v2 says "unable to connect"

do you have a ideas?

I think SMB 1.0 on a Server is not the right decision. On a private/office computer that does not contain sensitive data, it is not a bad option at all. But on a Server (I tremble just imagining it) I prefer to ask the opinion of the company's IT technician, and manage with him, access via an FTP link protected by the Firewall, with a local user account with a very secure password.


Alternatively, they can use direct scanning to the HDD and access through the device's WEB, or add an email account and scan the users' emails.

[luca72]

Re: Windows server 2022 & mpc2051 - smb v2 dont work, and smb v1 instead work

I think SMB 1.0 on a Server is not the right decision. On a private/office computer that does not contain sensitive data, it is not a bad option at all. But on a Server (I tremble just imagining it) I prefer to ask the opinion of the company's IT technician, and manage with him, access via an FTP link protected by the Firewall, with a local user account with a very secure password.


Alternatively, they can use direct scanning to the HDD and access through the device's WEB, or add an email account and scan the users' emails.

smb 1, it's right for the moment, next week we're going to uninstall the old server, and I'll try to fix the problem, I'm creating a mental "work-flow", on what actions to take to make this blessed smb 2 work