SMB Network Scan

[tecchie]

[bsm2]

Re: SMB Network Scan

is domain name entered? try hard Ipaddress

[BillyCarpenter]

Re: SMB Network Scan

• KYOCERA devices that only support SMB version 1
• 
  
  TASKalfa 3050ci - TASKalfa 3550ci - TASKalfa 4550ci - TASKalfa 5550ci

• TASKalfa 1800 - TASKalfa 2200
• FS-1135 - FS-1220MFP - FS-1320MFP - FS-1325MFP - FS-6025MFP - FS-6030MFP - FS-6525MFP
• - FS-6530MFP - FS-C8020MFP - FS-C8025MFP - FS-C8520MFP - FS-C8525MFP

You're not going to be able to do SMB on this older model.

[tecchie]

Re: SMB Network Scan

Yes I used computer name for server and also tried ip address

sorry to hear about it not being smb v2 compatible. I was hoping with the new firmware it would be. Machines not that old and it will be tough to explain to customer that one of the reasons they bought the machine for is non functional because of a Microsoft change

can someone explain a simple way to setup ftp scan and is it as smooth as smb scan to folder or is it too involved. Never done it before.

any other alternatives besides scan to email

[BillyCarpenter]

Re: SMB Network Scan

Yes I used computer name for server and also tried ip address

sorry to hear about it not being smb v2 compatible. I was hoping with the new firmware it would be. Machines not that old and it will be tough to explain to customer that one of the reasons they bought the machine for is non functional because of a Microsoft change

can someone explain a simple way to setup ftp scan and is it as smooth as smb scan to folder or is it too involved. Never done it before.

any other alternatives besides scan to email

I've done it before. I ran into a couple of problems by my own doing. Give this thread a read:

https://www.copytechnet.com/forums/connectivity/152621-ftp-scanning-question-post1612777.html?152621=#post1612777

And, yes, FTP scanning works very smooth. The customer will never know a difference and it's gonna be you're only option. You can do it.



EDIT:



Kyocera ECOSYS FS-C8520MFP and FS-C8525MFP

Release date

October 2012

[bsm2]

Re: SMB Network Scan

You can scan via ftp filezilla server
or scan to email.
Or sell them a newer model copier.

[richs]

Re: SMB Network Scan

Kyocera has software to add smb 2 to this model.Its on their ftp site(hopefully its still up and running).

[copier tech]

Re: SMB Network Scan

Yes I used computer name for server and also tried ip address

sorry to hear about it not being smb v2 compatible. I was hoping with the new firmware it would be. Machines not that old and it will be tough to explain to customer that one of the reasons they bought the machine for is non functional because of a Microsoft change

can someone explain a simple way to setup ftp scan and is it as smooth as smb scan to folder or is it too involved. Never done it before.

any other alternatives besides scan to email

All you need to do is add an old PC on the network with say Win 7 OS, create shared folder(s) & let users scan to these.

[tecchie]

Re: SMB Network Scan

Just to close out this thread I did opt to ftp scan. A couple of bumps in the road but that was me making a couple mistakes. Thanks for the ftp links. Server program and setup went pretty smooth for a first timer. Thanks again.

[dalewb74]

Re: SMB Network Scan

what process are you using to setup smb scanning? i got a shock about a year ago. i was able to setup a kyocera km 2550 to scan via scan file utility. and it was sending the file to my PC running windows 10. i almost hit the floor when it worked. before hand i would have sworn the older copier wouldn't scan to win10. boy was i wrong. if you know the km2550 there is actually 2 network cards. one is used for printing and the other for scanning.
that being said i would really recommend a new copier.

[ChrisG]

Re: SMB Network Scan

You can also reenable Scan to SMB 1.0 on Windows 10 so long as any IT manager signs off on it if applicable. It's under Programs and Features (Control Panel) advanced Windows features. Check the box for SMB 1.0 and make sure all boxes inside are checked. You'll have to do a system restart to finish the installation of the Windows files.

Windows decided it was a "security risk" for the Wannacry virus back when. Much like most of their other security updates which only serve to create more headaches than help.

Chris
TJL Copy

[aosboise]

Re: SMB Network Scan

"Make sure SMB is checked in the windows features on\off, sometimes a windows update will shut off SMB"

[aosboise]

Re: SMB Network Scan

Make sure SMB is checked on in windows features, sometimes windows 10 will shut it off

[BillyCarpenter]

Re: SMB Network Scan

To the best of my knowledge, SMB 1 has been disabled. Checking the box does nothing to enable SMB 1.



SMB is Dead, Long Live SMB!
By
JamesKehr
JamesKehr
Published 02-26-2020 09:22 AM 19.3K Views
Skip to footer content
Hello again, James Kehr here with another guest post. Titles are hard to do. They must convey the topic to the reader while being both interesting and informative, all at the same time. Doing this with a technical article makes life even harder. Now imagine my dilemma when starting an article about SMB1 behaviors in modern Windows. Think about that for a minute. Go ahead. The article will still be here.





Today I'll explain why you still see a little SMB1 on your network even after you uninstalled SMB1 from Windows, and why it's a good thing.





SMB1 is Dead!


The end of SMB version 1 (SMB1) topic has been discussed in great detail by Ned Pyle, who runs the SMB show here at Microsoft. Go read this article if you have not.





At first glance this seems like I’m beating a dead horse. If that’s what you thought, you’d be right. Unfortunately, this figuratively dead horse needs to be beaten1 some more.





Please stop using SMB1. Please get rid of those ancient, legacy systems that only support SMB1. We constantly get cases from customers asking why modern Windows 10 doesn’t support SMB1 out-of-the-box so it will work with their old, insecure systems.





Let’s go over this one last time.





The only versions of Windows that require SMB1 are end-of-support (EOS). By years! These are Windows Server 2003 (EOS July 2015), Windows 2000 Server (EOS July 2010), their client editions, and older.
Samba and Linux distros like Ubuntu have retired SMB1 as well. If you have a Linux/Unix-like distro that only supports SMB1, it’s time to upgrade.
Not only does Microsoft not support these EOS operating systems (OS’s), we do not support interoperability with them. Meaning, if the latest version of Windows 10 does no work with an EOS version of Windows over SMB, Microsoft will not support you.



Why not? Let’s start by putting the age of Windows 2000 (W2000) and 2003 (W2003) into perspective.





EOS Windows versus Apple:
Windows 2000 was released 7 years before the first iPhone.
Windows 2003/XP was released 4 years before the first iPhone.
Apple computers were still running IBM PowerPC processors.
Asking for EOS Windows support is like asking Apple to support PowerPC Macs. I’m sure Apple support would get a good laugh out of the request, but I imagine that’s as far as the request would go.



… vs Android
Didn’t even exist.



… vs Linux
Kernel 2.2.14 was released the same year as Windows 2000.
Version 2.4 was the newest kernel when Windows Server 2003 launched.
Support for the last version of the version 2 kernel, 2.6.32, ended in 2016.
How fast do you think the “no” would come back from Linux distro support if you asked for support on kernel 2.2 or 2.4? Assuming your distro of choice even existed back then.
By asking Microsoft to support EOS Windows, people are effectively asking us to support an OS that is so old that the modern smartphone didn’t even exist yet. Not counting Pocket PC or Windows Mobile here. An era when dial-up internet was still dominant and the world was still learning how high-speed Internet would impact computer security.





Multi-core processors didn’t exist yet, outside of the mainframe space. Those didn’t come around until 2004 (AMD) and 2005 (Intel). X86 64-bit processors didn’t exist when W2000 was released and they were brand new for W2003. Running legacy OS’s is not just bad security, it’s scary security because you are running an OS built for a completely different era of computing.





The real question here is: Why are you still running an OS or device that is so old it requires SMB1?





The SMB1 Problem
The biggest problem with SMB1 is that it was developed for the pre-Internet era. The first dialect came out in 1983 from IBM. Security and performance were designed for closed token ring networks and old fashion spinny disks. As EternalBlue and WannaCry would later prove, it is not a protocol that has aged well and it is no longer safe to use.





Unlike most other deprecated protocols, however, SMB1 controls the keys to the kingdom: data, services, file systems, accounts, and more. This makes SMB1 exploits critically harmful.





When Microsoft decided to retire SMB1 for real, and stop asking nicely, we tore off that band-aid by removing it completely from Windows 10 Spring 2017 Update (Win10 1703), when Windows detected that SMB1 was not in use. No SMB1 dialect was sent during negotiation, no SMB1 was allowed at all. And that broke things.





It turned out that some devices which only know about SMB1 weren’t quite sure what to do when getting an SMB request with no SMB1 in it. This caused a lot of strange behavior on the Windows-side; namely, hanging or pausing until everything finally timed out. This manifested in Windows as an unresponsive Windows Explorer (the technical name for the yellow folder icon you click on to access your files). People don’t like that. I don’t like that.





We ended up making changes to mitigate this without actually enabling SMB1.


Windows 10 1709 (2017 Fall Update) and newer will send SMB1 dialects as part of the SMB negotiate. We do this to help interoperability with legacy devices. I.E. prevent Windows Explorer from pausing/hanging.
We will not actually allow an SMB1 connection when SMB1 is disabled. We only pretend to. The connection will end up getting closed when the server or client tries to use an SMB1 dialect.
In addition to preventing uncomfortably long waits for Windows users, it lets us bubble up messages about SMB1 only devices on your network. System admins can look in the Event Viewer > Applications and Services Logs > Microsoft > Windows > SMBServer-Operational log for event ID 1001, which is created when SMB1 is used.





Log Name: Microsoft-Windows-SMBServer/Operational


Source: Microsoft-Windows-SMBServer


Date: 9/17/2019 12:17:41 PM


Event ID: 1001


Task Category: (1001)


Level: Information


Keywords: (8)


User: N/A


Computer: DC01


Description:


A client attempted to access the server using SMB1 and was rejected because SMB1 file sharing support is disabled or has been uninstalled.





Guidance:


An administrator has disabled or uninstalled server support for SMB1. Clients running Windows XP / Windows Server 2003 R2 and earlier will not be able to access this server. Clients running Windows Vista / Windows Server 2008 and later no longer require SMB1. To determine which clients are attempting to access this server using SMB1, use the Windows PowerShell cmdlet Set-SmbServerConfiguration to enable SMB1 access auditing.





SMB1 auditing can be also be enabled to get more details about what is using SMB1 on your network.

[ChrisG]

Re: SMB Network Scan

Unfortunately in a lot of environments and smaller dealerships, you don't have the option to not support older equipment that's years past the discontinuance date. Windows 10 more often then not will turn off the advanced sharing settings through the security updates which is a lot more bothersome than SMB 1.0.

To the best of my knowledge, SMB 1 has been disabled. Checking the box does nothing to enable SMB 1.



SMB is Dead, Long Live SMB!
By
JamesKehr
JamesKehr
Published 02-26-2020 09:22 AM 19.3K Views
Skip to footer content
Hello again, James Kehr here with another guest post. Titles are hard to do. They must convey the topic to the reader while being both interesting and informative, all at the same time. Doing this with a technical article makes life even harder. Now imagine my dilemma when starting an article about SMB1 behaviors in modern Windows. Think about that for a minute. Go ahead. The article will still be here.





Today I'll explain why you still see a little SMB1 on your network even after you uninstalled SMB1 from Windows, and why it's a good thing.





SMB1 is Dead!


The end of SMB version 1 (SMB1) topic has been discussed in great detail by Ned Pyle, who runs the SMB show here at Microsoft. Go read this article if you have not.























The only versions of Windows that require SMB1 are end-of-support (EOS). By years! These are Windows Server 2003 (EOS July 2015), Windows 2000 Server (EOS July 2010), their client editions, and older.











EOS Windows versus Apple:
Windows 2000 was released 7 years before the first iPhone.
Windows 2003/XP was released 4 years before the first iPhone.
Apple computers were still running IBM PowerPC processors.










Kernel 2.2.14 was released the same year as Windows 2000.
Version 2.4 was the newest kernel when Windows Server 2003 launched.
Support for the last version of the version 2 kernel, 2.6.32, ended in 2016.













The real question here is: Why are you still running an OS or device that is so old it requires SMB1?





The SMB1 Problem
The biggest problem with SMB1 is that it was developed for the pre-Internet era. The first dialect came out in 1983 from IBM. Security and performance were designed for closed token ring networks and old fashion spinny disks. As EternalBlue and WannaCry would later prove, it is not a protocol that has aged well and it is no longer safe to use.





Unlike most other deprecated protocols, however, SMB1 controls the keys to the kingdom: data, services, file systems, accounts, and more. This makes SMB1 exploits critically harmful.





When Microsoft decided to retire SMB1 for real, and stop asking nicely, we tore off that band-aid by removing it completely from Windows 10 Spring 2017 Update (Win10 1703), when Windows detected that SMB1 was not in use. No SMB1 dialect was sent during negotiation, no SMB1 was allowed at all. And that broke things.











We ended up making changes to mitigate this without actually enabling SMB1.


Windows 10 1709 (2017 Fall Update) and newer will send SMB1 dialects as part of the SMB negotiate. We do this to help interoperability with legacy devices. I.E. prevent Windows Explorer from pausing/hanging.
We will not actually allow an SMB1 connection when SMB1 is disabled. We only pretend to. The connection will end up getting closed when the server or client tries to use an SMB1 dialect.
In addition to preventing uncomfortably long waits for Windows users, it lets us bubble up messages about SMB1 only devices on your network. System admins can look in the Event Viewer > Applications and Services Logs > Microsoft > Windows > SMBServer-Operational log for event ID 1001, which is created when SMB1 is used.





Log Name: Microsoft-Windows-SMBServer/Operational


Source: Microsoft-Windows-SMBServer


Date: 9/17/2019 12:17:41 PM


Event ID: 1001


Task Category: (1001)


Level: Information


Keywords: (8)


User: N/A


Computer: DC01


Description:


A client attempted to access the server using SMB1 and was rejected because SMB1 file sharing support is disabled or has been uninstalled.





Guidance:


An administrator has disabled or uninstalled server support for SMB1. Clients running Windows XP / Windows Server 2003 R2 and earlier will not be able to access this server. Clients running Windows Vista / Windows Server 2008 and later no longer require SMB1. To determine which clients are attempting to access this server using SMB1, use the Windows PowerShell cmdlet Set-SmbServerConfiguration to enable SMB1 access auditing.





SMB1 auditing can be also be enabled to get more details about what is using SMB1 on your network.