Following wanacry we disabled SMBv1 via group policy on our network.
This stopped Command Workstation from working on our Fiery (FS100 Pro on windows 7 pro) - turns out SMBv2 was disabled in the windows registry on the Fiery itself - enabling that fixed the issue for Command Workstation on the Fiery itself - but not over the network - Command Workstation on other desktops can no longer connect to our Fiery over the network.
(This issue persisted over the update to Fiery Command WorkStation Package : 6.0.0.372
Fiery Command WorkStation: 6.0.0.46)
Does Command WorkStation depend on SMBv1 for communication? (even if you don't want/need Windows XP clients?)
Is this a known issue and is there anything I can do to make it work?