we have a WC 7845 and i am trying to get the remote control panel working. But after I fixed the java security problems and removed the efi fiery from the equation it is still not working. If i open the panel it is stuck in the "connecting to" => crash(Exception Connection reset) loop. Does anybody know why ?
And is there any way if it would work without the fiery to make it also work with a efi fiery in between ? Why does the java applet keep connecting to the internal Fiery-Printer Ip ?
Current Firmware: 072.040.104.14800
Used Browsers: Chrome, Firefox, IE
This would make my job a lot easier if i would not have to tell somebody to readout the Fault table to me or do some other stuff restricted to the control panel.
Thank you and best Regards
Solved! Go to Solution.
The remote control panel is a great feature, but it is a never ending battle to keep it running due to it relying on Java.
Every time Java updates again it pretty much breaks the Remote Control Panel, then Xerox needs to develop a new firmware to counter any changes made in Java, then it all begins again.
The last release of firmware ends in .14201 (As of today's date) and it supports Java 8 u25 with this caveat:
Java v8u25 no longer allows “Medium” level security. In many cases the Java Control Panel will need to have exceptions added for the remote UI to work properly even with this release installed.
1. In Control Panel on the PC choose Java.
2. Click on the Security tab.
3. Click the button for Edit Site List.
4. In the Exception Site List click the Add button.
5. Enter the address of the device, for example https://126.96.36.199 and press “Enter” to commit the entry to the table
6. When finished entering your exceptions click the “OK” button
7. Click “OK” to exit the Java Control Panel
The Fiery should make no difference in the setup
thanks for the quick reply. Sadly i cannot use the 14201 Firmware release atm because it breaks the Fiery (Booklet Printjobs are stuck in the print queue of the fiery endlessly altough they finish printing just fine). Xerox is currenly working on this issue . I would really like to try it out because it aparently fixes some other issues we are experiencing on our WC 7855 machines quite often. But for now this firmware release is off limits.
So i need to upgrade to the latest firmware or else i dont stand a change to get the remote control panel working ? (I added an java security exception allready)
Also it does make a difference with a fiery. The fiery has two network ports. One is connected to the WC 7845 and has an internal ip. Usually 100.100.100.101 for the WC 7845 and the Fiery has the ip 100.100.100.102. The second network port of the fiery is connected to the company network. The fiery is proxying all important traffic. Now if i try to access the remote control panel with a fiery in between, the remote panel client tries to connect to 100.100.100.101 which is not accessable from the company network (java throws a "timout" exception). If i try to access the remote control panel with just the WC 7845, it just connects to the printer assigned company network ip (java throws a "Connection reset" exception). So it cant work with the fiery at the moment because the remote panel client connects to the not accessable ip of the WC 7845 and not the fiery ip (also the fiery would need to proxy the vnc traffic through for it to work).
You should find what you're looking for in this page: Solutions for : Unable to Open the Remote Control Panel and an "Application Blocked by Security Sett....
You will find a instructions and a patch to install. I had to do just that a few days ago and it worked!
Note: If you want to connect directly to your machine webpage trough your Fiery, you can use your networked Fiery address with port 8080. Ex: 192.168.0.100:8080.
Hope you success!
thank you. The patch did work for the Workcentre without the Fiery attached.
Sadly it does not work with the Fiery attached. For the Control Panel to work I need Workcentre Webinterface HTTPS access. This is possible through port 8443 on the fiery ip. But if i try to connect to the remote control panel with the java client the java client tries to connect to 100.100.100.101 (The internal Workcentre ip adress which only the fiery server can access) and fails to do so.
Is this intended or a bug ? Is there a fix for this in the making ?
BTW: Whats speaks against opening the vnc interface to other vnc clients. Would make this a lot easier and secured with a password it would not even be a security issue. If somebody gets hold of the password for the webclient he/she can connect anyways.
This would make remote Administrating those Machines a lot easier.
Thanks again and best Regards,
I should have think of it earlier... Just use another network drop for the machine. One for the Fiery and one for the 7855. You could use a little network swtich between the Fiery, the 7855 and the network. You will need to change the IP address on the 7855 (DHCP will do). So, even if the 7855 is now on the network, the Fiery will be able to communicate with it as it will recognize the MAC address of the 7855.
So, Remote control will be accessible this way. And you will now be able to print both directly to the printer and trough the Fiery.
Should do it.
ah ok. I did not think they identify with the MAC address. Last question. Do you know if this works with multiple fierys/workcentres in the same network ? Is there maybe a way to assign a single Workcentre to a single Fiery or is this not possible ?
Not sure if I understand your question correctly.
A Fiery server is always dedicated to the machine it has been sold with. To get a Fiery to recognize a machine on a network, you need at initial setup to have the machine connected directly to the Fiery and establishe communication (ie Fiery icon on UI of the machine). Once that done you can disconnect the machine from the Fiery and give it it's own network drop. The Fiery should find the machine on the network and restore communication with it.
If you want to manage multiple Fiery, it will be with Fiery Command WorkStation.
Hope I've answered your question.
it could happen, that we have multiple Fiery/Workcentres in the same Network. If I connect all Fierys/Workcentres to the same Network i was not sure it would work. But if the Fiery and the Workstation are bound to another after the first intialization it should work fine.
Thanks again. I accepted your first response as the solution.