Results 1 to 4 of 4

Thread: JDF enabled on Fiery's but DSF RPC says they are non-JDF

  1. #1
    Join Date
    Aug 2010

    Default JDF enabled on Fiery's but DSF RPC says they are non-JDF

    I've enabled JDF on an E-41, 2 x EB1357, and a Ricoh Pro C720 - I can see these using remote print center in Digital StoreFront but the RPC reports that these Fiery's are non-JDF. What am I missing? Do I need to install the old Fiery JDF Connector server on the same RPC host? If so where is the latest version because the links at go to the download centre but the Fiery JDF Connector isn't there.

  2. #2
    oxident is offline Fiery Forum Expert Contributor oxident is on a distinguished path
    Join Date
    Aug 2009


    I've seen this on an IC306. Did you try to manually add the Fiery using the JDF URL?

  3. #3
    Join Date
    Jul 2009
    Menlo Park, California

    Default Manually add Fiery to DSF if you encounter timeout issues

    You should be able to manually add those Fiery servers to DSF as long as JDF has been enabled in the Fiery server's Configure app. This is most likely being caused by a time-out issue, where DSF is not getting a response quickly enough from your Fiery servers. DSF 6.2 adds an option to extend the timeout for networks where this is an issue. The configuration is done in a text file on the DSF server itself.
    Mark Bui-Ford
    Fiery Sr. Program Manager

  4. #4
    Join Date
    Aug 2010

    Default Extend response time

    Thanks Mark,

    Can you please advise which file and how what variable(s) to change in order to extend the allowable timeout?

    - Regan.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts