Customer Reviews

HP LaserJet 4250N Monochrome Network Printer

5 star:		(4)
4 star:		(0)
3 star:		(1)
2 star:		(0)
1 star:		(0)

 

 

I am used to faster network printers in the 30ppm range (which makes home printers seem slow). Then, this thing spits out at 45ppm. It seems like ours does 60ppm because it prints a page per second (maybe because they are not full pages of text). Wow. Of course, the expected HP quality and reliability.

I've installed a dozen of these printers on our office network beginning about 3 years ago. All are still up and running. Low maintenance workhorses, all I've had to do is purchase more toner cartridges as needed. Compared to our old Xerox printers, these are a dream come true. No fusers, transfer kits, main charge grids, or imaging units to replace. Easy to follow configuration and help screens makes it simple to set up as stand-alones or on a network. I've tried a couple of "lighter-duty" HP laser printers and found the 4250n to be a better machine and well worth the extra money in the long run.

I bought this printer new in 2005. 6 yrs later, in 2011, this printer hasn't given me a single problem. Not. One. Problem. It's still as fast as it was the day I bought it. It can spit out thousand page jobs without a single hiccup.

If everything worked as well as this printer, cars would get 200 mpg and never need to be replaced!

I also like the HP web interface for checking and administering the printer on my local ethernet network. Installing network printer drivers on multiple networked computers is as easy as could be.

As perfect a printer as I've ever used. I expect this printer will keep going for another 7 years at least.

Decent by today's means, but the older HP's are made with metal parts that really withstand the test of time.

However, these newer models will spit out a page fairly quickly and the web interface to modify the settings is a nice touch.

These play well in a small business networked environment.

I still prefer my older 4000's instead.

Nice product and fast but did stop working and needed to be re-configured with a "cold" reboot and it started to work again after much trouble-shooting.