This post is more than 5 years old
4 Posts
1
53197
July 21st, 2015 14:00
Compellent FS8600 fails to receive Scan from MFP using SMB ( konica minolta, xerox, and Canon)
Hello world,
I'm a system admin at a higher education organization and we are having issues when trying to scan to folder in our new storage Compellent FS8600. We are using an MFP ( Konica minolta, Xerox, and Canon) to scan to folder. We have moved from the Windows file share system to this Storage. We have no issues when adding permissions to the account we use to scan to folders. We have verified that the account we use to scan has all the access needed to the share file on the compellent FS8600. So far we have discovered that, although we can map to the path need on a windows machine with the account information, we are not able to scan to the file share using SMB on neother of the MFP. We have contact all three machines support team and also the DELL support team. We have recently received information that this CAN't BE DONE. Is this true?
Is there no way to scan to a file share on Compellent FS8600 using SMB?
We are in desperate need of help at this point because this use has stop our plan for implementation around the whole organization. We have migrated departments from their old File Share system on Windows servers to this File Sahre system on the Dell Compellent FS8600 and now all these users are experiencing issues when trying to scan to their departmental folders.
Can anybody help out?
Thank you
DELL-Daniel Ca
243 Posts
0
July 22nd, 2015 16:00
Hello, Dacuna1.
It is absolutely possible to scan and write files directly to FluidFS shares, and really to write files from any device, so long as current SMB (or NFS) protocol RFCs are followed. The most common problem we see with printer/scanner solutions and writing to a FluidFS share tends to be regarding use of old portions of the SMB protocol that Microsoft documents as being “deprecated”.
In some instances, this is related to the use of aged MFPs with old/out-of-date firmware, but the common root cause in every instance we’ve seen is the use of old portions of the SMB protocol.
So, the Engineering team for our FluidFS product line has advised that we have dropped support for deprecated SMB commands as of FluidFS version 3.0. (this has been the case since late 2013)
Did the Dell Support team verify that this is the error you're getting with a packet capture?
Anonymous User
1 Message
0
July 22nd, 2015 00:00
I`m in the same trouble but I can't find a solution
dacuna1
4 Posts
0
July 22nd, 2015 10:00
I just don't get it how this can't be done. Somebody from their team should be able to breakdown the communication from a Device. I would like to help as much as i can if anybody is willing to help out.
What machine do you have issues with inbrok?
dacuna1
4 Posts
0
July 27th, 2015 09:00
The Dell support does not really know what the issue is. At this point, we, the customers, are trying to figure something out that should be taking care by Dell. We have purchased the support and device thinking ( what the vendors told us) , that this will work in our environment. I just don't understand how SCAN-TO-FOLDER worked fine when using Windows servers 2008R2, and 2012 R2, but the minute we changed it to the Compellent Device, everything breaks.
How do other organizations SCAN-TO-FOLDER? do they use specific printers? is there any documentation about other companies with this issue?
I just can't believe is just us.
Also, I don't get how this issue is being tackle by US , the customers, instead of being Dell's job to satisfy their customers.
We are hoping this get taking care of.
DELL-Daniel Ca
243 Posts
1
July 27th, 2015 14:00
I asked if Dell support has been able to do a packet capture, and verify that this is even the error that you're getting. If so, I can email you, and you can email the case #, and we can assure that it's getting the attention that it needs.
However, warnings about the deprecation of SMB1 protocol commands have been out for some time now.
see articles:
blogs.technet.com/.../the-deprecation-of-smb1-you-should-be-planning-to-get-rid-of-this-old-smb-dialect.aspx
www.eweek.com/.../microsoft-start-preparing-for-smb1s-demise.html
For a list of the commands that are deprecated:
msdn.microsoft.com/.../ee441616.aspx
msdn.microsoft.com/.../ee442088.aspx
There is no resolution as long as you are using printers/scanners that use SMB1. Unfortunately I don't have better news than that.
Again, I'd like to be sure that this is even the issue in this case.
dacuna1
4 Posts
0
July 28th, 2015 10:00
I'm working with one of the MFPs ( Canon imagerunner C5051) and we are trying to update firmware. Now, they mention that we can use NTLM v2, as this is the same as SMB. I personally don't believe this but , is NTLM v2 a way to access the Dell Compellent also? if so, what settings do we need to do this? I'll be doing some testing today as soon as the Canon is updated to the new firmware. Thank you for working with us in this issue.
DELL-Daniel Ca
243 Posts
0
July 30th, 2015 10:00
Hey Dacuna1.
Sorry for the delay, was verifying some of my information.
So, here's where it may get a little tricky. After some research, I've found that if the printer only supports NTLM (no Kerberos) AND you have these updates ( support.microsoft.com/.../3002657 or support.microsoft.com/.../3068457 ) installed on your AD server(s), then you won't be able to connect UNLESS the "NTLM-Settings" CLI option is set to "ClusterName" (which requires FW v4.0.200700)
But, a key note to point out is that NTLM is only an authentication service, much like Kerberos. It only deals with verifying identity. Beyond that, SMB handles the actual file access to the NAS.
So, you'll need to determine whether you have these two updates, and if you do then it would be best to update to v4.0.200700.
THEN when updated, the way to make the changes to point the CLI option to "ClusterName" is as follows:
View Current NTLM authentication settings:
CLI> system internal protocols-settings SMB-settings NTLM-settings view
Allow NTLM authentication in MS15-027-patched environment:
CLI> system internal protocols-settings SMB-settings NTLM-settings edit -NTLMContextComputerName ClusterName
Allow NTLM authentication in non-patched environment (default setting):
CLI> system internal protocols-settings SMB-settings NTLM-settings edit -NTLMContextComputerName ControllerName
I hope that makes sense, and helps you out. Let me know if you need anything.
Have a great rest of the week!