Create an account on the HP Community to personalize your profile and ask a question
02-25-2012 01:03 PM
I have an HP Laserjet 2015d in WIN7 (32 bit) with USB connection. I keep getting unwanted pages printing with:
"GET /DEVMgmt/Discoverytree.xml HTTP/1.1
I found similar posts for other HP Laserjets but their repair method didn't work for me as I don't have a "Printer Status Notication" option as noted below.
(repair method quoted from another post for the 2055dn printer)
- Goto Printer and select HP 2055dn (currently using "PCL6" driver)
- Right click and select "Printer properties"
- Goto "Device Settings" tab
- Goto "Installable Options" settings
- Duplex Unit: Installed
- Printer status notification: DISABLED
Press "OK" to accept!
Since I don't have the Printer Status Notication under "Device Settings" how do I fix this problem with my P2015d? I am also using the PCL6 driver. Ideas?
Solved! Go to Solution.
03-28-2012 06:33 AM
The P2015 is a commercial printer. For the best chance at finding a solution I would suggest posting in the forum for HP Business Support!
You may find the Commercial Laserjet board here.
The actual article related to this product can be fonud here:
Hope this helps! :smileyembarrassed:
If my post helped you in any way, please click the blue KUDOS star under my name! It would mean a great deal. 🙂
05-02-2012 01:33 PM
I have an M2727, just back from repairs, doing the same thing. Never happened when I was using XP, but now using Win 7 Home Premium 64-bit and problem has surfaced. Installed drivers for HP Universal Printer PS UPD. I'm also so far unable to print via our network; only able to print by plugging in USB to my laptop. Any solutions would be most appreciated!
12-19-2012 12:58 PM
I really wish people would stop suggesting the disable Notification method because it has literally NEVER worked for me and I work for a company where all we do is work on HP printers. This issue plagues NUMEROUS printers. I usually see it with either P2015s or Color 2605s. I'm just wondering why so many people can read the original post and suggest the very thing that the poster said DIDN'T work for them.
I'm still looking for a "fix" for this clearly HP problem. Out of the hundreds of printers that I deal with in a short period of time, this issue always bugs me to no end.