2

One of my users' XP computer wouldn't start this morning - the problem turned out to be a corrupt registry, fixed with a chkdsk. Now everything is fine, except he's missing all his printers and can't add any. When I try to add a network printer (by drag and drop or going through the wizard), I get:

Windows cannot connect to the printer. Either the printer name was typed incorrectly, or the specified printer has lost its connection to the server.

Neither of those conditions is true, and the printers all work fine from any other workstation.

Also, if I try to add the printer that's physically connected to LPT1 on his computer, the New Hardware Wizard says:

There was a problem installing this hardware: Hewlett-Packard HP LaserJet 6P

It then gives me the option to install manually, where I get to chose the LPT port - only to find nothing listed in the selection box. The Device Manager shows a happy and healthy LPT1, so I have no idea why it's absent here.

Any ideas? I really don't feel like formatting and reinstalling everything.

4 Answers4

2

I would remove all printer drivers and then try again.

Here is the MS article on what to do:

http://support.microsoft.com/kb/135406/en-us

MathewC
  • 6,957
  • 9
  • 39
  • 53
0

OK, I know this sounds like a lame answer, but have you rebooted the PC? I've seen cases where Spool32 crashes, and displays a dialog box that it has to end. BAM! All the Printers disappear in Printers and Faxes, and the Add-a-Printer functions fail. Rebooting (maybe just restarting the Spooler) seems to fix it. Oh, and the users always deny having seen the dialog box that they clicked OK on.

BillN
  • 1,503
  • 1
  • 13
  • 31
0

I noticed that you skipped something very crucial. After the chkdsk works and you finally get in, I think a rollback is called for to get most everything in your settings back. I think this is quicker for getting the system back than trying to continue one a crippled system. Remember, "if you find yourself in a hole, stop diging"

jake
  • 194
  • 1
  • 4
  • 12
0

My solution was to reformat the computer.

For anyone else with this problem, I did have a similar incident on a different computer where the culprit was an out-of-date driver for an HP laserjet (which the user in this question did not have - go figure).