SMB v1 (or any for that matter) is NOT in the list of features.

[computertechguy]

I need SMB for scan to folder on a minolta copier.

I tried this command in powershell to enable
Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters" SMB1 -Type DWORD -Value 1 –Force
But this does nothing, it applies with no fix.

Any ideas what I am missing?

 

[Diggs]

We're missing a few details (OS?) but SMB1 is disabled in Win10. You can turn it back on again though.

 

[YeOldeStonecat]

What OS? Either desktop or server I never do the registry edit.

Windows 10...it is in the WIndows Features as long as you have at least 1803 installed. If it's not..get it installed.


Ensure you check the Server box, not client.
You can confirm it's set by running this command in powershell
Get-SmbServerConfiguration | Select EnableSMB1Protocol

You can check 2/3 by replacing the "1" with a "2"
On Windows desktop a reboot is needed to kick in SMB1 after checking the feature.

On servers, you just enable/disable via powershell and no reboot is needed
Set-SmbServerConfiguration -EnableSMB1Protocol $true

You replace the "1" with a "2"...and if you want to disable, replace the "true" with a "false".

 

[computertechguy]

What OS? Either desktop or server I never do the registry edit.

Windows 10...it is in the WIndows Features as long as you have at least 1803 installed. If it's not..get it installed.
View attachment 10206

Ensure you check the Server box, not client.
You can confirm it's set by running this command in powershell
Get-SmbServerConfiguration | Select EnableSMB1Protocol

You can check 2/3 by replacing the "1" with a "2"
On Windows desktop a reboot is needed to kick in SMB1 after checking the feature.

On servers, you just enable/disable via powershell and no reboot is needed
Set-SmbServerConfiguration -EnableSMB1Protocol $true

You replace the "1" with a "2"...and if you want to disable, replace the "true" with a "false".

No it actually isn't in there, that's why I am confused, by the way Win 7 Pro.
hmm those powershell commands don't work (I am in elevated mode) powershell doesn't understand the "get" commands...

 

[YeOldeStonecat]

No it actually isn't in there, that's why I am confused, by the way Win 7 Pro.
hmm those powershell commands don't work (I am in elevated mode) powershell doesn't understand the "get" commands...

Oh..yeah, Windows 7. Some important info there we didn't have. I haven't done Windows 7 SMB1 in a long time...we don't deploy Win7 anymore, any SMB1 enablements in Win7 we did were years ago.

Those powershell commands I listed above only work from Win8.1 onward...as well as Windows Features having SMB1.

So...the way you're doing it is the way, referring to old links I have.
Your syntax appears correct...
https://www.tenforums.com/tutorials...b1-file-sharing-protocol-windows.html#option1

You're doing this via Elevated powershell, right? Not just straight up? But "run-as-admin" launch of PS?

 

[Your PCMD]

https://support.microsoft.com/en-gb...-disable-smbv1-smbv2-and-smbv3-in-windows-and

 

[nlinecomputers]

I need SMB for scan to folder on a minolta copier.

I tried this command in powershell to enable
Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters" SMB1 -Type DWORD -Value 1 –Force
But this does nothing, it applies with no fix.

Any ideas what I am missing?

What model of copier? Most have firmware upgrades to move them from SMB 1.0(which has security issues that can't be fixed) to at least 2.0.

 

[computertechguy]

What model of copier? Most have firmware upgrades to move them from SMB 1.0(which has security issues that can't be fixed) to at least 2.0.

Possibly but there aren't ANY SMB versions in the add remove features section.

 

[nlinecomputers]

You're not going to find it as it has been removed from Windows 7 as it not safe to use. Windows 7 only supports SMB 2. Hence my comment about upgrading the printer.

 

[computertechguy]

You're not going to find it as it has been removed from Windows 7 as it not safe to use. Windows 7 only supports SMB 2. Hence my comment about upgrading the printer.

Should I see SMBv2? Because I don't.

 

[nerd2u]

What type of copier is it? I have seen copiers specifically canons where settings like SMB are buried deep in the tech menus and you have to know how to get to them.

Possibly but there aren't ANY SMB versions in the add remove features section.

Sent from my SM-G870W using Tapatalk

 

[nlinecomputers]

Should I see SMBv2? Because I don't.

Nope because it is built in. You wouldn't have windows networking without it.

 

[YeOldeStonecat]

Possibly but there aren't ANY SMB versions in the add remove features section.

In Windows 7? I mentioned above....they only introduced enabling SMB1 for Windows desktop in the "Windows Features" section starting with Win8.1. Prior to that...you had to do the registry edit via CMD.
By default SMB1 is disabled (not removed) on Win7..the commands you had above will enable it.
Here is an article by Microsoft published (edited/updated) Sept 2018 on how to do it.
https://support.microsoft.com/en-us...-disable-smbv1-smbv2-and-smbv3-in-windows-and

As mentioned above..it is a security risk (malware can spread easier via SMB1)...and you lose cool new features of newer OS's in networking. So there are many arguments against it..and recommending "just get a new MFP that doesn't need old school networking!".

Sometimes there's a big increase in cost in trying to maintain old stuff!

 

[fencepost]

I need SMB for scan to folder on a minolta copier.

Will the copier support scanning to FTP instead, and is the destination just a single server? If so, just install Filezilla Server, create a user account with both username/password and the folder set to the scan destination, set permissions to allow FTP to create and append to files, and be done with it.

 

[Sky-Knight]

Will the copier support scanning to FTP instead, and is the destination just a single server? If so, just install Filezilla Server, create a user account with both username/password and the folder set to the scan destination, set permissions to allow FTP to create and append to files, and be done with it.

This 1000 times this...

Linux based devices will always have issues with SMB. For that reason I only support scan to FTP, and scan to SMTP, configure this way and it'll work forever... mess with SMB and you'll go old and gray before your time with random issues.

 

[fencepost]

One caveat, though the same applies to SMB: I would never put this anywhere exposed to the world. That's less likely with SMB simply because most properly-configured firewalls and routers should block it, but since FTP is an accepted "Internet" protocol it seemed worth mentioning.