A little fyi for those with scan to smb issues with smb1 disabled

[BHM]

Seems that a Windows update is disabling smb1 lately and we are getting hit with a lot of calls. We have been going around on our Konica boxes and installing the new f/w patches. Most work fine but we were getting a few random computers that were ok before but now can not be scanned to.


SMB2 does not support scanning without a user id and password in the scan address. Turning off password protected sharing and using the everyone account does not work! Yes it was bad practice but a lot of IT people around here still do it.

[Woxner]

Re: A little fyi for those with scan to smb issues with smb1 disabled

havent had too many issues with this. but i do carry the ftp utillity it always works.

[Hansoon]

Re: A little fyi for those with scan to smb issues with smb1 disabled

Since many years we are installing exclusively Scan-FTP but not SMB for exactly this reason. If the customer or his IT blokes think they need Scan-SMB, than its their problem.

We use Quick 'n Easy FTP Lite:

Quick 'n Easy FTP Server Lite

Download link at the bottom of the page.

Hans

[mntech]

Re: A little fyi for those with scan to smb issues with smb1 disabled

I usually push customers to use scan to email, unless they have a server with shared scan folders. I also need to use FTP on some older machines that don't have smb patches. I use fileZilla server.

Worst thing is when a customer wants 10+ PC's setup for scan to smb with no sever. I can usually convince them to use 1 PC as a file server.

[slimslob]

Re: A little fyi for those with scan to smb issues with smb1 disabled

SMB2 does not support scanning without a user id and password in the scan address. Turning off password protected sharing and using the everyone account does not work! Yes it was bad practice but a lot of IT people around here still do it.

To my knowledge, requirement of a user name and password was introduced with Windows Win 7 or possibly Windows XP. It was required at the network connection level, not SMB.

[allan]

Re: A little fyi for those with scan to smb issues with smb1 disabled

Really like Konica Minolta's new "userbox/samba" move. Shares the user boxes straight on the network. Only problem is the HDD filling up.

[slimslob]

Re: A little fyi for those with scan to smb issues with smb1 disabled

Really like Konica Minolta's new "userbox/samba" move. Shares the user boxes straight on the network. Only problem is the HDD filling up.

It won't fill up if the user after scanning a document the to a user box, the user then returns to his/her computer and moves the file(s) to a local drive. Proper user training solves many problems before they become problems.

[NeoMatrix]

Re: A little fyi for those with scan to smb issues with smb1 disabled

Really like Konica Minolta's new "userbox/samba" move. Shares the user boxes straight on the network. Only problem is the HDD filling up.

A 1-2 terrabyte NAS works great on home networks.

Set individual NAS directories with individual password protection and assign each directory a limited size/space. When the user runs out of HDD space they are forced to clean up their own directory. This allows others to continue to use the NAS without problems.

Requires FTP client which can be configured permanently in normal Windows Explorer.

[Santander]

Re: A little fyi for those with scan to smb issues with smb1 disabled

I usually push customers to use scan to email, unless they have a server with shared scan folders. I also need to use FTP on some older machines that don't have smb patches. I use fileZilla server.

Worst thing is when a customer wants 10+ PC's setup for scan to smb with no sever. I can usually convince them to use 1 PC as a file server.

Do you realize that US Federal regulations require that all business related emails be archived for seven years? This would include your scan to email setup! There are penalties for not archiving the scan to emails for the full seven years, which can amount to a very large usage of disk space. As you suggest, having one shared folder either on a server or a shared PC will circumvent the scanning to email setup and the archive requirements for emails. All of our state accounts and large customers prohibit scanning to email for this very reason as it creates a huge storage problem on their servers as the email and the attachment have to be archived for seven years. Simply creating a "temp scan folder" on the server or a shared PC and having the users pull the scanned documents into their own PC will circumvent the archive requirements. We have found that most IT people do not realize the archive requirements for a scan to email setup and when explained to them they do not want that setup implemented. Hope this helps a little.



S

[JR2ALTA]

Re: A little fyi for those with scan to smb issues with smb1 disabled

Since many years we are installing exclusively Scan-FTP but not SMB for exactly this reason. If the customer or his IT blokes think they need Scan-SMB, than its their problem.

We use Quick 'n Easy FTP Lite:

Quick 'n Easy FTP Server Lite

Download link at the bottom of the page.

Hans

Does it work with hostnames instead of IP address?

[slimslob]

Re: A little fyi for those with scan to smb issues with smb1 disabled

Do you realize that US Federal regulations require that all business related emails be archived for seven years? This would include your scan to email setup! There are penalties for not archiving the scan to emails for the full seven years, which can amount to a very large usage of disk space. As you suggest, having one shared folder either on a server or a shared PC will circumvent the scanning to email setup and the archive requirements for emails. All of our state accounts and large customers prohibit scanning to email for this very reason as it creates a huge storage problem on their servers as the email and the attachment have to be archived for seven years. Simply creating a "temp scan folder" on the server or a shared PC and having the users pull the scanned documents into their own PC will circumvent the archive requirements. We have found that most IT people do not realize the archive requirements for a scan to email setup and when explained to them they do not want that setup implemented. Hope this helps a little.



S

I believe that requirement actually applies to the SMTP that the email is sent through and the POP or IMAP sever the email I sent received from.

[tjvincent]

Re: A little fyi for those with scan to smb issues with smb1 disabled

Are there any directions on setting up the Quick and easy FTP server lite for a Ricoh machine ?

[copier tech]

Re: A little fyi for those with scan to smb issues with smb1 disabled

Are there any directions on setting up the Quick and easy FTP server lite for a Ricoh machine ?

I'd also be interested to know if there is a guide available.

[slimslob]

Re: A little fyi for those with scan to smb issues with smb1 disabled

I'd also be interested to know if there is a guide available.

Are there any directions on setting up the Quick and easy FTP server lite for a Ricoh machine ?

To my knowledge there is no Quick and easy FTP server lite software specifically for Ricoh. It is a third party software for the computer. You first need to decide on the specific software you wish to use. Hint, make sure that you select a server software and not a client software. If you choose FileZilla there are a number of member here that recommend it and threads that have directions on installation.

[NeoMatrix]

Re: A little fyi for those with scan to smb issues with smb1 disabled

Are there any directions on setting up the Quick and easy FTP server lite for a Ricoh machine ?

You don't require any additional FTP server software running on any PC or Server.

FTP Plug-n-Play for DIY home/small office Networks:

1. Plug 1GB - 2 Terrabyte USB/FLASH/HDD/SSD into any PC. Create individual customer scan folder/directories for all PC's on the network onto this USB stick or HDD. This will be come our NAS (Network Address/Adapter Share)
USB/HDD Create Folder example:
|_Bill
|_Fred
|_Mary
|_Jane

2. Plug in the above NAS into the local network "Modem/Router" or "Switch".

3. You will need to enter the NAS Router or switch configuration WIM (eg.http://10.1.1.254) and setup customized names,passwords and individual directories. These are the same directories you created in step 1. on the USB/HDD. Look for the "Set up Share" menu tab while inside the Router WIM.
Share setup Example:
User/Share name : Mary
Password : -accounts-123-
[x] Use directory :Mary
[x] read/write access

4.Configure all your customers MFD's or Scanners to "FTP Scan" to the same multiple customised NAS directories above.
Ricoh MFD address book setup :
FTP[x]
user :Mary
password :-accounts-123-
scan to folder:\\10.1.1.254\Mary\

5.On all PC's, run windows "File Explorer".
Right click on: Computer | Map Network Drive | enter \\NAS-IP<eg.10.1.1.254>\NAS-User-Id<eg Mary>\ | [Z] Drive | [x] Reconnect at logon| <enter>


DIY scan to FTP --as straight forward as it can be.

NB. FTP is not totally secure, but its a step up from SMBv1-2.

HTH