Re: Windows server 2022 & mpc2051 - smb v2 dont work, and smb v1 instead work
[SOLVED] Hi, the replacement of the management software from that customer was taking a long time, but today I went for the noisy fuser, and I took the opportunity to fix it, well...
I overwrote the firmware, and disabled and re-enabled smbV2/V3 flag from WIM, and now everything works.
I didn't quite understand what resolved the two, I think the second one...ciaooooo
Windows server 2022 & mpc2051 - smb v2 dont work, and smb v1 instead work
Collapse
X
-
Re: Windows server 2022 & mpc2051 - smb v2 dont work, and smb v1 instead work
If you can not get SMB2 to work scan to folder to work would they be interested in scan to memory device? The USB2.0/SD Slot Type G (D556) may not still be available but you don't really need it. Just make the SP settings shown in the service manual for it and put your thumb drive in the USB slot that the USB2.0/SD Slot Type G (D556) uses. To bring the connection to the front panel just use a USB extension cable. An adapter can be used for SD cards.
we have to make smbv2 work, no usb or anything else, rather we change the machineLeave a comment:
-
Re: Windows server 2022 & mpc2051 - smb v2 dont work, and smb v1 instead work
If you can not get SMB2 to work scan to folder to work would they be interested in scan to memory device? The USB2.0/SD Slot Type G (D556) may not still be available but you don't really need it. Just make the SP settings shown in the service manual for it and put your thumb drive in the USB slot that the USB2.0/SD Slot Type G (D556) uses. To bring the connection to the front panel just use a USB extension cable. An adapter can be used for SD cards.Leave a comment:
-
-
Re: Windows server 2022 & mpc2051 - smb v2 dont work, and smb v1 instead work
Some news for this issue ?Leave a comment:
-
Re: Windows server 2022 & mpc2051 - smb v2 dont work, and smb v1 instead work
we don't like using ftp, and probably neither does the customer, he's been using scan to folder for years, however we will solve the problem as soon as possible....the defeat is not contemplated..lolLeave a comment:
-
Re: Windows server 2022 & mpc2051 - smb v2 dont work, and smb v1 instead work
this problem is very interesting, but the main thing is allowing an old copier to speak SMB with a recent Windows Server.
Have you considered using a FTP server on the WS2022 ?
This would solve your problem with ease.Leave a comment:
-
Re: Windows server 2022 & mpc2051 - smb v2 dont work, and smb v1 instead work
thanks, i think that this sp its same thing of wim settings, but i check this anywayLeave a comment:
-
-
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.Leave a comment:
-
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.Attached FilesLeave a comment:
-
Re: Windows server 2022 & mpc2051 - smb v2 dont work, and smb v1 instead work
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 issueLeave a comment:
-
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 TapatalkLeave a comment:
-
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 TapatalkLeave a comment:
Leave a comment: