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

[slimslob]

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

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

What version was the old server?

Has your IT friend tried using wireshark or another utility to capture a session using SMBv2?

Has anyone checked the network log on the C2051 immediately after a failed scan attempt to see what was recorded as the SMB error?

[dalewb74]

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

you said fw has been updated. did you run the package all? if so, then you might look to see if there is one specific for scanning?

[BillyCarpenter]

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

What version was the old server?

Has your IT friend tried using wireshark or another utility to capture a session using SMBv2?

Has anyone checked the network log on the C2051 immediately after a failed scan attempt to see what was recorded as the SMB error?

I've done the wireshark capture before for SMB. It's very informative. It appears to be an SMB problem because it works with SMB1 enabled...which is a bad idea, IMO. If I had to bet, I'd say the copier isn't SMB2 capable...for whatever reason.

[Gift]

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

If it's not a firewall issue, perhaps M$ implemented some sort of SMB patch causing issues even if the device appeared to be SMBv2 ready.

I barely recall that with an older Ricoh I had to change some settings via telnet to get SMB up and running.
I think one setting was port related and the other was something with "auth" (entification).


.....found this:

smb client auth 1 - this sets ntlm auth level
smb client port 445 - this changes smb port to 445

[luca72]

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

What version was the old server?

Has your IT friend tried using wireshark or another utility to capture a session using SMBv2?

Has anyone checked the network log on the C2051 immediately after a failed scan attempt to see what was recorded as the SMB error?

the old server, which is still connected in parallel, until the management software is fixed on the new one is a windows server 2008, which I was told worked via smb v1.
the system registry, which is the first thing I checked on the phone (as I often suggest here on the forum) says "unable to connect" which seems like a connection problem, I remember that I didn't go in person, but only by phone to now, next week a colleague of mine and I should go to disconnect the old server, the colleague hasn't tried with wireshark.
yesterday we connected remotely, and using power shell with appropriate commands we verified that port 445 is open, and it is.
we heard from Ricoh, and he suggested that we check that "Auth" is present with a value of 2, if it isn't there, it can't work, at that point not having a 2051 mounted here, I tried to check on one mp171spf, and there is Auth 2, so if the 171 which is from 2007 has it, necessarily the mpc2051 which is from 2009 also has it, this is one of the things I have to try.

[luca72]

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

you said fw has been updated. did you run the package all? if so, then you might look to see if there is one specific for scanning?

the machine has all the latest firmware modules, in particular "network scanner 10.64" which is the very latest, we check this by remote

[luca72]

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

I've done the wireshark capture before for SMB. It's very informative. It appears to be an SMB problem because it works with SMB1 enabled...which is a bad idea, IMO. If I had to bet, I'd say the copier isn't SMB2 capable...for whatever reason.

unfortunately I don't know how to use wireshark, I tried some time ago, but it took a long time to understand how it works and interpret the outputs correctly

[luca72]

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

If it's not a firewall issue, perhaps M$ implemented some sort of SMB patch causing issues even if the device appeared to be SMBv2 ready.

I barely recall that with an older Ricoh I had to change some settings via telnet to get SMB up and running.
I think one setting was port related and the other was something with "auth" (entification).


.....found this:

smb client auth 1 - this sets ntlm auth level
smb client port 445 - this changes smb port to 445

I also had the same feeling, among other things for some time now, it is possible to change the Auth, even from wim, in the interface settings, in fact, yesterday we heard from Ricoh, and the technician told us "it could be that 2022 wants the auth at 2, try checking"
but you reminded me that my colleague on the phone when I told him to search on the 2051 for "smb port and version settings" in "interface settings" he didn't find it(?)...but do you know what it's like?.. If you don't see it in person, you will never be 100% sure.

[rthonpm]

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

In the Web interface, what's the SMB setting under Network > SMB > Advanced Settings? That will allow you to change the dialect that the device uses by enabling or disabling the newer SMB 2 and 3 stack. Just updating the firmware will not enable the feature.

Server 2008 is a poor reference point as SMB1 couldn't be disabled on its network stack at all, a feature that didn't arrive until Windows 8/Server 2012.


Sent from my Pixel 6 Pro using Tapatalk

[luca72]

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

In the Web interface, what's the SMB setting under Network > SMB > Advanced Settings? That will allow you to change the dialect that the device uses by enabling or disabling the newer SMB 2 and 3 stack. Just updating the firmware will not enable the feature.

Server 2008 is a poor reference point as SMB1 couldn't be disabled on its network stack at all, a feature that didn't arrive until Windows 8/Server 2012.


Sent from my Pixel 6 Pro using Tapatalk

the port is set to 445 and smb V2/V3 is active, is that what you mean?

[rthonpm]

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

the port is set to 445 and smb V2/V3 is active, is that what you mean?

That's it. So the machine is using SMB over DNS and the correct dialect. What does the system log show when trying to scan?

Sent from my Pixel 6 Pro using Tapatalk

[luca72]

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

That's it. So the machine is using SMB over DNS and the correct dialect. What does the system log show when trying to scan?

Sent from my Pixel 6 Pro using Tapatalk

the registry monitor log say "impossible to connect" like when its bad network parameter like wrong subnet mask or other bad ip class, but only with smb2, instead with smb1 the scanner work well....I'm starting to think it's really an "auth" selection profile issue

[emiliorsg]

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

Searching through the archive I found this bulletin It's in Spanish, I imagine you'll understand it. In case it helps you at all. I remember at the time, six years ago, I had that problem with an official organization and I seem to remember that the firmware could have solved it, but I'm not completely sure.

[emiliorsg]

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

In octopus the last firmware update is 7-2021.
c2051.jpg

[slimslob]

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

Searching through the archive I found this bulletin It's in Spanish, I imagine you'll understand it. In case it helps you at all. I remember at the time, six years ago, I had that problem with an official organization and I seem to remember that the firmware could have solved it, but I'm not completely sure.