eltroca Posted May 5 Report Share Posted May 5 Hi, I have moved to a new place and know my Frontier 340 is not connecting to the DI controller. Is this a LAN issue? Any ideas on how to solve this? Thanks! Quote Link to comment Share on other sites More sharing options...
Minilab service Posted May 5 Report Share Posted May 5 If before everything worked well and only in new place stopped to work then can be only LAN cable, or wrong network settings. Look network settings on both computers ( IP and mask ) . Check cable and cable type. If scanner computer connected directly to server then should be crossover cable. If they connected through switch, or hub then can be straight through cable. Try ping from one computer to other. Should see response time and shouldn't be connection errors. Quote Link to comment Share on other sites More sharing options...
eltroca Posted May 5 Author Report Share Posted May 5 Thanks MS for you answer. I have checked everything and even ping works, but when I run connection to "image controller" it says first "connecting to image controller", then it says "reading services from image controller" and then it fails. What else should I check? Best regards Quote Link to comment Share on other sites More sharing options...
Minilab service Posted May 5 Report Share Posted May 5 Seems network works. To be sure you can try access shared folder on other computer. Check working group names on both computers. Both computers should be on the same group. If nertwork settings are then someting happened with server. Which software there - C4/C5, S2, or MS01? Quote Link to comment Share on other sites More sharing options...
eltroca Posted May 5 Author Report Share Posted May 5 Is C4/C5. Both are on the same group. What do you meen with "someting happened with server"? The server is one of the computers? or the router or switch of my network? Thanks for your help. Quote Link to comment Share on other sites More sharing options...
Minilab service Posted May 5 Report Share Posted May 5 Server is only on external computer. Try on server from CD to run software upgrade. Might it it will help to restore connection. Quote Link to comment Share on other sites More sharing options...
eltroca Posted May 5 Author Report Share Posted May 5 Thanks. I will try to restore the image controller from a disk image. Quote Link to comment Share on other sites More sharing options...
eltroca Posted May 5 Author Report Share Posted May 5 One more question @Minilab service what should be the name of the computers and the workgroup? Also am sending pictures of the 3 messages I get: connecting, reading services and fail Quote Link to comment Share on other sites More sharing options...
TECNOR Posted May 5 Report Share Posted May 5 Exist differents reason for bad comunications between pc minilab and pc server. Quote Link to comment Share on other sites More sharing options...
Minilab service Posted May 6 Report Share Posted May 6 Working group name can be any, but the same group name sould be on both computers. Default Fuji working group name was MICSGROUP. Now Fuji use standard name - WORKGROUP. Minilab internal computer name - EZPC00 . Server computer default name - FRONTEND . Server name will be the same, what is server computer name on Windows. During C4/C5 instillation also need enter server name. It should match server computer name. Server name can be different, but it should match name entered on minilab computer during C4/C5 instillation. These errors see, when no communication between minilab internal computer and server computer. If you have disk image then try restore it. Usually it is enough on server to run C4/C5 upgrade and after that communication is restored. Quote Link to comment Share on other sites More sharing options...
eltroca Posted May 6 Author Report Share Posted May 6 10 hours ago, TECNOR said: Exist differents reason for bad comunications between pc minilab and pc server. Hello @TECNOR could you list them so I can check if one of them works for me? Quote Link to comment Share on other sites More sharing options...
Minilab service Posted May 7 Report Share Posted May 7 Can be bad network ( cable, IP, mask, working group names ) , mismatch server name entered on minilab computer with real server name, or bad server software. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.