I have a CQ 8900 with firmware non conect key 071.160.202.26500 and the tecnical update to 072.161.216.30801, after this upgrade the smf workflow don´t work anymore.
I have 2 machines with the same configuration and that have the 071.160......work fine the new frimware don't work.
Can I do a downgrade, and how or somebody already have that problem and have a solution.
Both firmwares are Connectkey, 071 is Connectkey 1.0 and 072 means Connectkey 1.5
we can't troubleshoot "don't work anymore".
Yes it can be downgraded, but only by an ALTBoot, meaning you need a tech to do it and it will wipe the device entirely, you cannot use a clone to restore it.
You would be vastly better off troubleshooting the issue, which is likely in the scan settings themselves, or the time on the device is wrong, but "don't work" is far from enough to work on, you need to provide at the very least:
1. OS of scan location
2. Failure at the device (Login or connection failure at least)
3. One touch, Workflow scan template, or Scan to is used
4. Domain or local credentials used to access server
5. LAN details about bridges, wired,wireless, corporate or residential
The 071.160.202.26500 is non-conectkey
I already did a instalation by altboot with the the forceupgrade e disablebackup and don´t work.
About the solution to work with the new firmware, this is what i want.
The configuration is the same, i have two 8900, one work ( 071.160.202.26500 ) and the other (072.....), don´t.
Same configuration, same os, same template, same place in disk, same login e pwd. but, did append a update no more works
Do a wireshark and find the error.
The only scan setting that would have changed is you would originally not been able to support SMB2-3 and been using port 139.
The newer firmware does support SMB2-3 and uses 445, it does not in any way contain Windows Networking (NETbios/TCP/IP) so scans on port 139 fail. In turn, this would then add that time needs to be within 3 minutes and Windows 8 and up would need a different username format than the older firmware. Which is easily found server/PC side (you need the name as it appears in the brackets exactly)
But the Wireshark will be enough to show you that. The protocols will apear different between the devices on different firmwares.