nothing, Isilon stopped supporting depricated SMB commands. I had same issues with Konica Minolta and some Lanier printers, Konica were resolved with firmware upgrade but older Lanier printers were out of luck.

The Xerox printers have problems with authentication (they don't send the domain of the user) and are often using NETBIOS.

Try to turn on NETBIOS Support on your Isilon

Try to enable "assume default domain"

commands:

isi smb settings global modify --support-netbios yes

isi auth ads modify --assume-default-domain yes

Hello NathanBradshaw,

Thank you for your question! Both sluetze and dynamox are correct here. There are some legacy/deprecated SMB commands that are no longer supported in the OneFS architecture so there is not much for tuning on the cluster that can be done; however, it would be worth checking in to some of the changes mentioned above to continue to support the Xerox printers.

If you would like more details on the calls the Xerox printers are making and to double check on potential workarounds, I would create a service request for our Windows Protocols team to investigate with you. To create a service request, you have a couple options:

1. Log in to your online account on support.emc.com and go to this page: https://support.emc.com/servicecenter/createSR

2. Call in to EMC Isilon Support at 1-800-782-4362 (For a complete local country dial list, please see this document: http://www.emc.com/collateral/contact-us/h4165-csc-phonelist-ho.pdf)

Please let me know if there is anything else I can help you with!

Katie,

after, well lets say a quite interesting week of analyzing pcaps from Xerox Scans to Isilon SMB I would like to know if Xerox and EMC Isilon do in any way work together and test their products. We often have unwanted side-effects either deploying OneFS Code or Xerox Firmware. Also inter-company support is another problem. Xerox tells us it's the isilon, and EMC tells us it's the Xerox - this just doesn't help and i would like to know if there is any option to get EMC supporters (engineers please!) and Xerox supports work together - searching a solution and not a reason why the other company made mistakes.

If this is not the right place, I also take any other

Regards

-- sluetze

2 years ago i got Isilon to work with Konica Minolta. Isilon actually gave Konica the virtual appliance so they could test and fix their outdated firmware. It took a while because of some legal issues but in the end Konica updated their SMB stack.

sluetze

The issue you've described smells of as dynamox put it "outdated firmware" on the scanners themselves.  We've seen a number of old scanners that actually run Windows NT 4.0 under the covers, or some other similarly old embedded operating system.  The problem with that is the very early versions of the SMB1 (as used by NT 4, HPUX & AIX (built-in SMB clients, not SAMBA)) dialect permitted using ASCII including plaintext passwords for session setup and teardown.  We do support SMB1, however only in binary for setup/teardown messages.  So in general on scanners, there are a few options.

1. If you are a big enough customer of the scanner company, get them to fix their "outdated firmware" as dynamox did with Konica Minolta.

2. Try using a different protocol.  Isilon is of course at its heart a multiprotocol filesystem, and just about every commercial or enterprise scanner I've seen in the last 10 years also supports at least FTP.   Assuming the device is just dumping data into a given directory, make that the home directory of the service account performing the writes.

Maybe this isn't your issue, but usually it is;

Hope this helps,

~Chris Klosterman

Advisory Solution Architect

EMC Isilon Offer & Enablement Team

Hi Chris,

thanks for your response. We are a customer big enough to request / update firmware. The problem is, with every new firmware they provide, we find new bugs, which they don't find while testing against Windows Servers. Also we are (currently) speaking of connectkey machines which were introduced in 2013 (afaik).

also (too bad) a different protocol is no option, since we ftp is insecure and nfs is Linux (we are Windows only Environment)

Regards

--sluetze

I'm having the same issue with our Konicas after storage was updated to Isilon. I've contacted our Konica reps about this but they're saying they don't have a fix at this time.

Do you know what model/firmware version you used that worked?

This is what we had to upgrade to