Wrong Kyocera Model Scan

[MatzeK]

Hello together,

unfortunately, the model display for Kyocera printers is wrong, only F-Series appears for all of them. See Appendix.

Can the problem be solved?

Kind regards, MatzeK

[Obi_1_Cinobi · Accepted solution]

Hello there!

For your case, after analyzing your logs, it seems that this issue is caused by the following built-in OID mapping, which you can find under Configuration/Asset Mapping in the Device SNMP OID Lookup section.

As a workaround, you should be able to delete this entry by pressing the red delete icon behind the entry and then successfully rescanning your printers with the correct model. We will, of course, escalate this to our developers to ensure this entry is no longer added automatically.

F-Series

[Obi_1_Cinobi · Accepted solution]

Hello there!

It seems that this issue is caused by the following built-in OID mapping, which you can find under Configuration/Asset Mapping in the Device SNMP OID Lookup section.

As a workaround, you should be able to delete this entry by pressing the red delete icon behind the entry and then successfully rescanning your printers with the correct model. We will, of course, escalate this to our developers to ensure this entry is no longer added automatically.

F-Series

[rader]

Add another user to this list. I have 3 Kyocera's that are showing as F-Series as well. All have the OID of (1.3.6.1.4.1.1347.41) while I have one Kyocera/Copystar that is reporting the model correctly with an OID of (1.3.6.1.4.1.1347.41).

Doing a MIB library search under Scanning shows the Kyocera's listed under an OID of (1.3.6.1.4.1.1347.43).

Could the missing OID .41 be the issue?

[Obi_1_Cinobi]

Hello there!

We are still gathering information for our developers to look into this. Would you mind reaching out to our support team at support@lansweeper.com ?

We would love to receive the following information:

• Program Files (x86)\Lansweeper\Service\Errorlog.txt, as present on your Lansweeper scan server.
• Screenshots of one problem machine's Lansweeper webpage. Show us the following tabs:
  • Summary
  • Scan Issues (if it exists)
• Screenshot of a connection test performed to the same problem machine with devicetester.exe, which can be found in Program Files (x86)\Lansweeper\Actions on your Lansweeper server. Perform the test from your Lansweeper server to the problem machine, submit any relevant scanning credentials and show us the entire test window.

We recommend compressing these files into an archive (zip/rar/7z) prior to sending them to drastically reduce their size.

[rader]

Done.

[Obi_1_Cinobi · Accepted solution]

Hello there!

For your case, after analyzing your logs, it seems that this issue is caused by the following built-in OID mapping, which you can find under Configuration/Asset Mapping in the Device SNMP OID Lookup section.

As a workaround, you should be able to delete this entry by pressing the red delete icon behind the entry and then successfully rescanning your printers with the correct model. We will, of course, escalate this to our developers to ensure this entry is no longer added automatically.

F-Series

[MatzeK]

Thank you very much, it works perfectly.

[rader]

Worked perfectly. Also learned something new today.

Thank you.

[Obi_1_Cinobi]

Hello there!

Would you mind reaching out to our support team at support@lansweeper.com ?

We indeed see other users reporting similar issues. We would love to receive the following information to get started:

• Program Files (x86)\Lansweeper\Service\Errorlog.txt, as present on your Lansweeper scan server.
• Screenshots of one problem machine's Lansweeper webpage. Show us the following tabs:
  • Summary
  • Scan Issues (if it exists)
• Screenshot of a connection test performed to the same problem machine with devicetester.exe, which can be found in Program Files (x86)\Lansweeper\Actions on your Lansweeper server. Perform the test from your Lansweeper server to the problem machine, submit any relevant scanning credentials and show us the entire test window.

We recommend compressing these files into an archive (zip/rar/7z) prior to sending them to drastically reduce their size.