Confirmed with our copier vendor. The 3635 does not scan to virtual storage. Xerox is supposed to work on this. It's extremely annoying.
Another problem is with using XSA (Xerox Secure Access). It's not supported by the 3635's and the 53xx and 71xx series copiers also ask for a user account password. Again another problem Xerox is supposed to be working on.... Sigh...
well, i newer firmwares (spar) firmwares , not listed on the xerox site, they have included the ability to have a service account for scanning
so you can add your domain also, that should work then
I have also had this issue. Xerox support was that anything other than the standard' setup is not supported. I have ensured the shard path for the scan is opened up to the everyone active directory group and tried scanning using both the local xerox admin login details and a network account created solely for this purpose.
I have setup scanning to xerox 52xx, & 7232 series devices but this same configuration does not work on 7235/45 or 4595 series which are in use in my organisation.
I have checked with the infrastruscture team to see if they were aware of any such issues with connecting to netapps boxes but they are not aware of any.
Currently my line management is escallating this with our Xerox client manager.
what firmware is installed on your machine?
startinf from version : 061.132.221.29100, the fix below was implemented
you can call xerox to obtain that firmware, maybe that helps
also try with DOMAIN\username or DOMAIN.LOCAL\username
that sometimes also helps
I have Scan to Home configured on a Xeorx 5745. When my home path is set to a Windows-based server, the Scan to Home works fine. When I point my home path to a Net App virtual storage box. The result is Login Failure. I am able to logon to the copier using my domain credentials. The copier uses a service account with Domain Admin rights, with LDAP.
On a Xerox 5350, I am able to use Scan to Home with our virtual storage solution.
On a Xerox 3635 using Network Scan folders the error I get back is: Invalid FIlename. And again it works fine if I point the shares to a Windows-based server.
Was hoping someone with virtual storage expertise could help me figure out why this is breaking in different scenarios. I believe it relates to the copier software on certain models.
Permissions just for testing on the virtual server are set to Local:Everyone, Share:Everyone