getting error 0x803C010B while runing printer troubleshooter

Anonymous
2014-11-22T06:26:10+00:00

Original Title: Can't Troubleshoot - get error 0x803C010B 

My printer suddenly stopped printing today and when I run the troubleshooter I get the above error 0x803C010B

I've tried everything - uninstall, re-install, update drivers, configure using TCP/IP - nothing works. The printer always shows offline since last windows update.

Windows for home | Previous Windows versions | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2014-12-11T13:43:14+00:00

Hi All,

Sorry for the delayed response.

For all of those who are using network printers, the reason for the issue to occur can be due to SNMP (Simple Network Management Protocol). SNMP manages devices on a network. Some Printers may not support this protocol, because this obtains the printer's status regardless of whether or not they support SNMP, although it only supplies simple status information for those devices.

I suggest you to disable the SNMP option from the printer properties. To do that please follow the steps below:

  1. Open Control Panel.
  2. Select Hardware and Printers option.
  3. Right click on the Network printer (your printer).
  4. Choose Properties.
  5. Go to the Ports tab and choose Configure.
  6. Uncheck SNMP Status Enable option.
  7. Restart the computer and check if the issue persists.

Please reply for any further help.

Was this answer helpful?

90+ people found this answer helpful.
0 comments No comments
Answer accepted by question author
Anonymous
2015-05-28T10:01:22+00:00

Hi Jerry,

If issue still persist you may try the steps provided in the tutorial provided below and see if it helps you to fix the issue.

**Fix printer problems**

Do keep us updated about the status of your issue. We will be happy to assist you.

Regards,

Was this answer helpful?

30+ people found this answer helpful.
0 comments No comments
Answer accepted by question author
Anonymous
2015-06-17T03:06:13+00:00

There was as recent update that allows the firewall to let Epson Print inside.  With the amount of attacks that Norton stops, I'm happy to have to figure this out safely and patiently.

Was this answer helpful?

3 people found this answer helpful.
0 comments No comments

119 additional answers

Sort by: Oldest
  1. Anonymous
    2014-12-07T17:48:57+00:00

    there is no help at all

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2014-12-29T14:59:16+00:00

    Thanks!  I will try this. However, in my case, turned out to be much deeper trouble: I am a CenturyLink DSL customer, and they supplied a Zyxel modem/router/wifi combination device. Seeking a stronger WiFi signal, I purchased a LinkSys  6300 WiFi router and for 10 months ran the ZyXel PK5001z with its WiFi turned off.  The Zyxel suddenly returned to its default state (everything on) and the two routers began fighting with each other for the same IP address. The computer's failure to communicate with the Brother printer's static IP address -- which never changed -- was a symptom of this conflict. When I  opened the Zyxel's configuration page and turned its WiFi off again, its modem refused to connect to the Internet. CenturyLink and LinkSys tech support refused to provide advanced configuration instructions to get  the the Zyxel and LinkSys devices to coexist and told me to hire an IP technician if I wanted to continue using them both. (Score one for Comcast!). I went back to using the Zyxel combo device and disconnected the LinkSys router. I then chose "remove printer" in Devices and Printers on all Windows 7 and 8 computers, and re-mapped to the Brother as a new printer, and all devices now recognize the Brother's IP address and print normally. Also did something similar on my Macs and again, was able to print.

    Was this answer helpful?

    0 comments No comments