Kyocera - Fleet Services

[kuby]

Re: Kyocera - Fleet Services

Got everything working on both ends. Can see all of the machines at both locations on our side.

Boss just ask me if we can load the gateway on a MAC at his church and see all the Kyocera's there. I told him that there was not a driver as far as I knew. I just saw a Windows 32bit and 64bit version. Is there a way to make it work on a MAC.

Thanks

[kuby]

Re: Kyocera - Fleet Services

OK we installed a Windows 64bit computer at my employers church now. Installed the Gateway and XML file. Sees everything but the Kyocera devices. (This is a MAC environment with no Domain Name, just Peer to Peer network). When I go into the Kyocera and try to setup the Remote services and click the Submit button it gives a error every time. Is there a way to make it work in a MAC environment using a Windows PC? Go everything working but this.


Thanks for all who helped..

[darry1322]

Re: Kyocera - Fleet Services

What device are you trying to connect (model and firmware level)?

[kuby]

Re: Kyocera - Fleet Services

TASKalfa 5551ci

Software Version
System :		2N4_2000.004.505
Engine :		2N4_1000.003.003
Panel :		2N4_7000.004.501
Scanner :		2N4_1200.003.001

[kuby]

Re: Kyocera - Fleet Services

Keep getting a

Cannot register to the server.
Remote services communication error.
200

error when trying to get it to connect for the Remote Services

[darry1322]

Re: Kyocera - Fleet Services

No need for the Gateway on that model unless you just want it. Update the firmware, make sure your copier is on the network with a good gateway address and good dns server addresses. Put in the correct URL and code for your KFS account and it should connect right up.

[kuby]

Re: Kyocera - Fleet Services

The problem is when I try and "Put in the correct URL and code for your KFS account and it should connect right up. " and press Submit I get the "Cannot register to the server.
Remote services communication error.
200"

error when trying to get it to connect for the Remote Services

[darry1322]

Re: Kyocera - Fleet Services

No need for the Gateway on that model unless you just want it. Update the firmware, make sure your copier is on the network with a good gateway address and good dns server addresses. Put in the correct URL and code for your KFS account and it should connect right up.

You haven't addressed whether these issues are complete.

[wragsdale]

Re: Kyocera - Fleet Services

I would suggest double checking your DNS settings as darry mentioned. If you cannot resolve a hostname, you cannot reach a URL. I've also seen malformed URLs. It should read exactly "https://rfs-us.kyocera.biz"

[kuby]

Re: Kyocera - Fleet Services

Thanks Guys. Will try that and let you know.

[tmaged]

Re: Kyocera - Fleet Services

You can't use the gateway to get to devices that can connect direct. The 5551ci will connect direct. I was getting that same error today on a 2551ci. I think it may have been server related as it was working until I updated firmware. Removed the settings through maint. mode & set it back up.
You also need to update the firmware on that one. You'll have tons of problems with them dropping offline unless you get firmware fixed.

[kuby]

Re: Kyocera - Fleet Services

Thanks, everything just started showing up.

[sparkycivic]

Re: Kyocera - Fleet Services

'Error 200' means KEEP TRYING.
Been seeing this error frustratingly frequently the last two weeks. it's definitely server related because if you change the access code, you get the access code error immediately.
usually takes less than 10 minutes of repeating until it actually completes.
KEEP TRYING

[kuby]

Re: Kyocera - Fleet Services

Everything working OK, but how do you keep the machines from going OFF LINE. Both Kyocera and the others show that they are reporting to be OFF LINE under KFS when I can print to them with not problem. . Is there a setting that will keep them ON LINE and not reporting that they are OFF LINE?
Thanks

[tmaged]

Re: Kyocera - Fleet Services

If they are machines that connect direct to KFS, you need to update the firmware. That was all addressed. If they are Gateway connected machines, make sure you're using the latest version of the gateway and the computer has to be on obviously.
The updated versions of the Gateway are working better, the direct connected machines shouldn't have any problems.