• TwitterFacebookGoogle PlusLinkedInRSS FeedEmail

Fiery Remote Scan 6

6/14/2018 

Hi all, I just recently updated to the latest Command Workstation Software (Thank you EFI). After doing so, i can no longer remotely log in to retrieve scanned files either as GUEST or as ADMIN through the Fiery Remote Scan version 6.1.0.09c. The setup is like this: Fiery EX700 Server connected to a 700DCP, client workstations are macintoshes on OSX 10.8.4 with latest updates. The Fiery Remote Scan installed on the EX Server is version 5.5.1.30, the original version would also not log in as well. There has been no changes made on the 700DCP itself prior to these issues and after.

Fiery Remote Scan 6

Download Fiery Remote Scan 6 Windows 10 - best software for Windows. Fiery Remote Scan: Fiery Scan incorporates the Fiery controller as a key element of network and. Free download fiery remote scan 6 win7 64 bit Files at Software Informer. Fiery Scan incorporates the Fiery controller as a key element of network and distribution. Download Fiery Remote Scan 6 Win7 64 Bit - best software for Windows. Fiery Remote Scan: Fiery Scan incorporates the Fiery controller as a key element of network and.

Xerox Tech personnel seems clueless. There is also a similar error from a fellow member YARNIK on another thread but there seems to be no direct solution to the same issue too. Here's the thread: Here's the screenshot of Fiery Remote Scan on my end. Lastly, thanks to the moderators for letting me be a member. It is appreciated.

Last edited by marlomoya; at 11:01 PM. From the info you posted, it sounds like it used to work, but now both Fiery Remote Scan 5 and 6 can't log in. Just to be double sure, could you try connecting to that Fiery with Command Workstation, and logging in as guest? Keygen Zeta Producer 11 Alive.

I want to be sure the account is still functioning. If that works OK, then we'll need to take a look at your server setup, and your patches. Could you post a server configuration sheet? You can black out or delete confidential stuff like IP address, domains, email addresses, etc before you post it.

THANK YOU Mod Greta C! Your reply is sincerely appreciated, my apologies for a somewhat late, a friday holiday was declared and a super storm is currently on top of us right now, but my weather worries have lessened somewhat when i learned of your reply. I tried connecting on the Fiery Server from a workstation via CWS 5.5.0.16i as guest and it connected. I also tried to connect as guest from the Server itself and it connected as well. I tried to connect again on Fiery Scan as guest and admin and still - it wont go through on both stations. I am attaching a 3-page server config pdf for your evaluation.

I also tried to update the CWS software on the server end (after all these scan log issues), unfortunately, it wouldn't accept the Fiery Software Manager since it says it will only do so if it has System 9 (or higher) on it, the server is currently System 8 only and is possibly not upgradeable. I somehow think this might not be an issue at all, but if this information is pertinent, its already there. I am awaiting eagerly any response from you. Dso-5200a Usb Driver. Thanks heaps.

Hi, I just tried using Fiery Remote Scan 6 from Windows 7 and from Mac OS 10.8 and 10.7, both without issue. See my PC screenshot below. Mac is identical. I would suggest restoring from a Clone image, or if one is not available, reinstalling your Fiery. Thanks, Craig Yes, i think that is what the Xerox Tech people might do by next week.

It is an unfortunate way to process an issue, and a long one at that, somehow, i thought it best to consult EFI forum for a creative solution that doesn't need a day or two to complete, but yes, looks like i'll end up with that. I can't clone it myself though or reinstall as this surely will void warranty. Thing is, Xerox is somewhat busy serving a roadshow instead of a client. Marlomoya, Your config sheet shows no configuration issues, and I also can't replicate the problem on a fully patched EX700 like yours. Somehow your system must have been corrupted.

Craig is correct in suggesting you clone it back to a good state or reload. Sorry for the inconvenience! Vmware Converter 4.0.1 on this page. Thank you Mod.