-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
- HP Community
- Printers
- LaserJet Printing
- P3015dn driver not connecting to the printer

Create an account on the HP Community to personalize your profile and ask a question
05-10-2016 03:23 AM - edited 05-10-2016 06:25 AM
Hi. We provide IT supports for a number of hotels and since about a month, we have had issues with a number of P3015 printers at different properties not being able to print. These are network printers shared through Windows 2008 R2 servers. The issue persists when the drivers are installed directly on the user computer (Windows 7 Pro).
The printer is connected and can be accessed through a web browser. When a test page is sent, no data seems to go to the printer. There is no error in the printer event log. After a while, an error appears for the printer in the 'Devices and Printers'. There is no specific error given.
The driver installed is universal PCL6 as there is no specific driver for this printer.
I would like to know if this is a common error that has surfaced recently. At the moment we have this issue in 4 seperate hotels. Most P3015s are few years old but one is recent and still under warranty.
Update: Installing the PS drivers does not resolve this either.
Solved! Go to Solution.
Accepted Solutions
05-10-2016 09:38 AM
A colleague of mine managed to resolve the issue, out of sheer desperation. Seems the printer services for the port has been disabled on the printers. 4 printers in 4 different sites. No wonder how it could have happened but this is all you need to do...
ENABLE 9100 IN MAMT.PROTOCOLS
05-10-2016 09:38 AM
A colleague of mine managed to resolve the issue, out of sheer desperation. Seems the printer services for the port has been disabled on the printers. 4 printers in 4 different sites. No wonder how it could have happened but this is all you need to do...
ENABLE 9100 IN MAMT.PROTOCOLS