refreshing our stable of Xerox's. These 2 models are BOTH failing workflow scanning with Login failure. Check user password/and or setups.Okay so 30 of our other Xerox printers (3500 and 5475) have no problem with workflow scanning. These 2 units have been setup to print to the same folder on same server with same account (which is working on older models).
Version of firmware is 073.060.075.34540- Level 2 could not offer a solution. Now everything we have tried so far on forum as well. I even tried disabling the Mcafee on the 3655,
So knowing that these machines have been set up identical to ones that are actually working fine, rules out account issues, permission issues,. Im pretty sure its buggy firmware that these came with although this version is the latest greatest, its not working. I am hoping there maybe a spar release that fixes this issue before we get the other 40 machines in here that dont perform workflow scanning properly Thanks in advance
Solved! Go to Solution.
Thank you for using the Support Forum. Have you contacted your local support centre to ask about the availability of a SPAR firmware?
Thank You for the reply. I was in contact with level 2 tech support- and they were using a 72 ver ironically same model and there scanning was fine. See here is the thing when the printers arrived (demos) a tech showed up and updated the firmware to 073.060.075.34540, on both models, so I really do not have an earlier version to test with. I wish he would not have updated to 73 version which just came out a month ago I see.Well level 2 did not want to back date the firmware, which I understand, but I am hoping there is a spar patch for this firmware, to address the smb issue.We don't even need the connect key won't be using it. But workflow is critical
First up, these 2 devices are in what is called the Connectkey family. Connectkey devices do not have Windows Networking built into them, and what that means for you is, unless they are on a Domain (and registered to it) you cannot scan via hostname. In short, if it isn't on a Domain using DHCP you have to scan via IP.
2nd, Chrome and Xerox do not play well together, and even Firefox is as of late joining in on that. And what this means to you is occasionally, any box you fill in that shows dots (password fields) and the occasional check box, don't actually set when you click apply.
In short, If all else fails, try using IE or Safari, and make sure you scan via IP and not hostname.
3rd, make sure the time is correct, if it is off by 3 or more minutes, and the CWIS page is https, scan will fail to Windows 7 and up, this didn't effect the older devices that did SMB scan via port 139 (SMBv1) but it does for the newer port 445 setup (SMBv2)
(CWIS > Properties > General Setup > Date and time
4th, also in line with some of the above, username formatting is different, it has to be put to the machine exactly as displayed in brackets here. (Again, different than the older SMBv1 ala NetBios over TCP/IP
The Share name has no forwarding or trailing slashes of any kind, literally identical to the shared folder. So if the shared folder on the PC is scAn then that is exactly what you put on the printer setup, not scan, not SCAN, you put scAn.
In short, even if all the settings are right, they can still be wrong. The older machines use very different methods to attain the same thing.
As for firmware, I would update both, but I really can't see the update resolving this issue, it's just an aside.
<If you called in to 2nd level, Canada or USA, please PM me the log number (Don't post it here), You have peaked my interest as while scanning has intricacies , it is 100% doable as long as you understand the changes between the old tech and the new. >
Thank You Joe !,
Much appreciated, I am currently downloading the firmware you kindly posted and will return with results!
The Connectlkey products all work right up to SMB3. I believe the 5030 does up to SMB2 (but I am not sure on SMB2.1).
Here is how the version break down to different Windows versions.
You can lower the version supported on the server side if needed.
But the biggest issue now by far across the board is username formatting, that is why I suggest taking it from the brackets in permissions, especially in the case of Windows 10 and Server 2012.
Check to everything you suggested. Updated the firmware same result. The strange thing is when I created a new scan directory on the server, it worked? But why will it not scan t0o the existing scan folder directory login that the other printers are going to? Hmm
No idea, I would assume that the specific user was not added to the specific folder , but since I already showed that had to be done in the screenshots above, it can't be that. At this point nothing but a Wireshark trace will say for sure, we just know it isn't the Xerox at this point.
Thank you for taking the time to offer assistance and insight. I truly appreciate that. I have created another scan directory and works fine.