KM 3060 Scan Error 2101

Hi
I have found a list of error codes at the link below and your code is described as;
Drum EEPROM error Reading from or writing to EEPROM cannot be performed. Poor contact in the connector terminals. Defective drum unit. Error Codes Kyocera Mita KM3060
It looks therefore like a drum unit problem which probably requires a replacement drum unless you can check and improve the contacts in the connector terminals.
Hope this is helpful, if so would you please register that with Fixya
Cheers

The following errors are simalir;

2101, 2102, 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.

The link below takes you to Kyocera's Scan to SMB setup guide on GFBM's website (they are a Kyocera dealer). The guide setup guide is good and gives pictures and examples.

http://gfbm.net/Documents/self_help/SCAN%20TO%20SMB%20PC%20setup%20R3.pdf

I hope this is helpful,
Shawn

Software trouble error code
720f Error: Unknown error

Causes:
Unable to determine the
cause.

Check procedures/corrective measures:
Turn the main power switch off and on.

Click this LINKfor the Scan to SMB setup guide which will walk you through the settings. If it had been working then stopped most likely just one setting has changed; the two things I would look at first is the password for the folder you are scanning to and and IP/Host Name of the computer you are scanning to.

Does your Domain require you to change your password on a regular bases? If so then the password set in the copier to access the folder on the computer may have changed and the new password needs to be set in the copier.

Also the person that setup the scanning originally may have set it to scan to the IP address of the computer you are scanning to but if the computer is setup for a dynamic IP address the IP will change from time to time and then the copier will not be able to find the computer you are scanning to. Change the IP that the copier is set to scan to, to the Host Name of the computer you are scanning to and that will no longer be an issue.

The Scan to SMB setup guide goes over these settings.

You can also call Kyocera's free help desk Monday - Friday 9 am - 6 pm EST at: 1-800-255-6482.

you have to have a user name and password set up on the computer you are scanning to then you set that up in the address you set up on the copier.

maybe your account reach the limits

The KM-1820 to scan to PC is using SMB, FTP or e-mail.

for SMB:
I am assuming you have the KM-1820 connected within the network and a static IP address for it.
open any Internet browser and go to KM-1820's IP address.
You should see the Command Centre web page.
Go to Basic page and add/register a contact within the Address Book.
Give a name and at the SMB section field, fill up with your computer hostname or the ip address of your computer where you want to scan. Fill up the user name with the local user name - the one what you are using to get into your computer - or create a new LOCAL user for your PC lets say "kyocera". So for SMB will be your computer and username: kyocera. (You will need a password for that computer user (kyocera) ). Then create a folder "scan" where you want ot receive the scanned files and add "scan" at the path field (SMB section of that webpage - command center).
Now share the folder "scan" as "scan".

if you want you can always use the scan to e-mail !! but you need a smtp server. All the settings can be done using that command center webpage.

you have to have a user name and password set up on the computer you are scanning to then you set theat up in the address you set up on the copier.

I don't know if SMB for a Mac is supported on Bizhubs. I know it works with Microsoft workgroups. The only other way to get around it is to scan to e-mail. Then retrieve the e-mail from a Mac.

I had the same issue and fixed it by adding the group "Everyone" to the shared folder permissions (where I was sending my scans) and assigning the "Everyone" group rights to "change" and "read".