If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

KM-5050 SMTP set up error

hi,

I need to set up SMTP from a KM5050. I have made all the correct settings and have allowed the IP and username to relay on Exchange server (2003).
However, when I click TEST on the http KM5050 Command Centre, it gives:

All of the send error codes are described in the Basic Operation Guide under Troubleshooting.

2101, 2102, 2103, 2201, 2202, 2203, 3101:
The network cable is disconnected or the hub that it is connected to is not operating properly. Check the cable and the hub. Otherwise, the server name or the host name of the SMTP server is not set correctly. Use COMMAND CENTER and register the SMTP server name and the host name correctly.

If you can print to the 5050, you know the network connection to the machine is fine.

I'd try using the IP address of the exchange server first. If this fixes it, check the DNS settings in the copier.
If that doesn't work, try running 'telnet exchangeserverName 25' from a command prompt on a nearby computer. You should see something like '220 exchangeserverDNSname ESMTP' as a response if it connects. If this works, I'd start with checking the gateway settings on the copier.

You might be on to something with the username. The previous Kyocera machine that ran linux (KM-1820) listed send error 3101 as smtp authentication or other weird smtp problem. I have no idea if they changed the error on the 5050 or just lumped it into the wrong box in the manual.

It sounds like you might've tested the server with a plain client like Eudora or Thunderbird, but that would be my next step. Since I never get to configure the services, I use Thunderbird to test settings like the format of the username.

Beyond that, I've used wireshark to track down some odd email problems on older Kyocera copiers, but I haven't seen the linux-based machines mess up email.

As I recall, the domain name needs to be entered in upper case if you didn't already. Also, I believe [but not positive about this] the login username of the exchange server may need to have admin rights. It's usually the only way I can get it to work.

I had this same issue worked on it for hours and what got it to work as simple as it might sound was to turn on DHCP and let the machine grab the information itself then input the static IP and the other few missing info. It worked when I thaught I would never get it