02-21-2017 12:14 PM
Due to the recent security vulnerability in SMBv1 on Windows systems, our central computing disabled SMBv1 on our file servers. Now our scan-to-network folder no longer works (gives login error). The firmware on the 7556 is 061.121.225.06100. Does anyone know if there is a newer firmware that might get us up and running again?
Scan-to-network also broke on our 7970 with firmware 072.200.024.14107, but I see there is a newer version 073.200.075.34540 on the Xerox support site that offers "Improved operability in MS environment (SMBv2/v3) and Support for Windows 8 and Server 2012". So I'm hoping that will solve the problem on the 7970.
02-21-2017 02:22 PM
7556 and it's 6 versions newer and should work, you will likely need to update existing ports from 139 to 445 to make it work.
7970, don't load the one on Xerox.com, run the one I linked.
The 7556 needs to be upgraded the old school method (USB or dumped onto it via CWIS)
7970 is updated via tool installer (run the file from a PC, needs JAVA)
3 weeks ago
Thanks Joe, was able to do the 7556 firmware upgrade to 061.121.227.03404 using Index > Manual Upgrade in the web interface, which was successful. Unfortunately it didn't fix our scan-to-network issue. We are already using port 445.
3 weeks ago
I tested a 7556 today with that version and it certainly works, have a tech altboot it and don't use a clone file to rebuild it.
There is an issue somewhere in your setup or the firmware is corrupt.
I am not allowed to disclose the altboot process here.
2 weeks ago
I'm in the same situation where the disabling of SMBv1 broke our scan to file feature on the 7556. The 7990 is currently working fine when we do scan to file through the address book. It looks like the 7556 doesn't have that same feature so I've setup the exact same options through workflow scanning and I'm still getting a login failure. This is on the 7556's newest firmware version.
2 weeks ago
Tested it again today on 061.121.227.03404 and it scans with no issue from the 7556 to Server 2003-2008R2-2012-Win10.
Wireshark traces show it using SMB2 to both Win 10 and Server 2012, didn't have time to trace the others.
Call Xerox, get 2nd level support, they will probably require an Altboot since I can't replicate your issue in their own test environment, they will need a config sheet, Server information and likely will want a Wireshark trace of the failure (They can help you do that if need be)