Link to home
Start Free TrialLog in
Avatar of alonig1
alonig1

asked on

HP printer doesn't install

On the network trying to install the printer and get the following error:User generated image
ping reply to the printer
and I can browse to the printer.

All firewall and AV settings are the same as other computer, although I did try to disable it.

on other computers it did work.
Avatar of mbkitmgr
mbkitmgr
Flag of Australia image

The first thing I'd suggest is checkng your can browse to the Web interface of the printer you are working with.

Can't browse to it - check your TCP/IP setting to make sure they are correct
Can browse to it - try just creating a TCP/IP printer port, using the printers IP and just the basic HP driver
Remove the printer, delete the driver (Printer server management), make sure you have the most recent HP Driver for the operating system you have, restart the computer.

Now try installing again.

This works for most HP Printers that we install
Avatar of alonig1
alonig1

ASKER

mbkitmgr I specify wrote I can browse to the printer.

John , how can I remove a printer if it doesn't let me install it.
Avatar of hypercube
I use this fairly well tried and true method:
It assumes a network printer with a fixed IP address.
Best-Way-to-set-up-a-Windows-Network.pdf
Avatar of alonig1

ASKER

Please read my question before replying.

Fred Marshall: other computer have no problem installing the printer with the wizard.

The wizard detects the IP printer. that is not the issue.
I see an HP wizard.  That is NOT what I suggested......  Please read my response more carefully.
Install the printer as a local printer. When asked for the port, create a new Standard TCP/IP port with the printer's IP address. When asked for the model, either select it from the list or browse to the location of the driver files (the .inf file)
Avatar of alonig1

ASKER

I don't want to install it manually cause it's a scanner also , and that's the only way the scanning program will be installed.

there's an issue I want to resolve it , not do a workaround.
I understand your issue better now.  Thanks.

What I usually do with HP printers certainly is to select the full package (usually by download) and install it.
However, I still use the procedure I outlined to, shall we say?, CONNECT them.

Prior to installing, I remove all remnants of the printer.

Delete files from the spooler directory:
Open services.msc
Stop the spooler service.
Navigate to %SystemRoot%\System32\spool\PRINTERS, usually C:\Windows\System32\spool\PRINTERS.
Delete all flies in this directory.
Restart the spooler service.
Close Services

Open Devices and Printers
Remove all devices of the type you're working on.
Select any other printer (i.e. highlight it)
A menu bar will appear near the top of the window:
Select Print server properties
Select the Drivers tab
Remove the printer type you're working on.
Close out and reboot.

Install the full software package for the printer.
When it comes to connecting, do these things:
Select "the printer I want isn't listed" (even if it is listed)
Next
Add a printer using a TCP/IP connection
Next
Under Device type, change the pulldown from Autodetect to TCP/IP device!!
Enter the IP address
Next
etc.
Then complete the installation according to what may be needed for scanning, etc.
Avatar of alonig1

ASKER

That printer wizard doesn't let you continue unless it connects to the printer.

Now, other computer at the environment had no problem. only that computer .

I'm trying to understand why it isn't connecting to the printer the default way.
I don't know enough about the wizard.  There are so many of them.  However, with a lot of HP installs done, my recollection is that the wizard will eventually need to know how to connect.  And you've confirmed that.  And, that, I should think would follow the same steps that I've given to a great degree.  I'm sure that's what I've been doing.

Reasons why a *computer* will act differently:
- The print queue hasn't been flushed.
- The print server / driver remains behind.
Thus, the instructions to clear those things out may well still be useful.  
That said, it doesn't answer the question "why?" which may never be known exactly.

Also, I remain leery of WSD connections which have their own "personality".  I'm a lot more comfortable with TCP/IP because we rather *know* what that brings.  That's another way a *computer* could somehow be "different".
This question needs an answer!
Become an EE member today
7 DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.