Delete a printer that does not exist?

[TechSupp]

Had someone (not going in to details, and it was not me!) delete one of our shared system printers. I've managed to reinstall the printer and share it as before but now I seem to get two printers set up when the client XP PC's logon, the printer is shared and its name on the server is Xerox Phaser 6180DN-9DB7F8 PS.

 

The one which works appears in printers and Faxes as:

'Xerox Phaser 6180DN-9DB7F8 PS on hpserver' Ready on the client

The non connected one as

'Phaser 6180DN-9DB7F8 PS on hpserver' Printer not found on Server, unable to connect

 

(Tried to rename the printer on the server and just ended up with the opposite situation, one connected and working one not wanted and not connected!)

 

How do I get rid of the non wanted printer (the non connected one), tried to delete it, it seems to get rid of the one I want top keep then I try again it just says it can't because it does not exist!

 

Help Please!!!!!!!

[mac_shinobi]

how are you pushing the printers out from the print server ? vbscript, R2 using pushprinterconnections.exe or what exactly ?

[6Foot2]

I had something similar a while ago [except that the printer which would not go away was a real (present in the physical sense)] It was in one of our network rooms.

 

It eventually transpired that it had become incorporated into the profile while I was making some modifications to the network.

 

Could this be happening to you?

Edited April 28, 2010 by 6Foot2
Add brackets to (hopefully) clarify how the post reads.

[TechSupp]

Think I have made a problem of my own making in the end. Thought about this on the way home (as you do!). Anyway, As I did not want to change the share name I found details on the net how to remove an existing share name (as it would not let me reassign the existing share name to the reinstalled printer) but don't think I did it entirely correctly as I now think what has happened is that it it now is mapping via the logon script two refferences to the original share name as I must not have removed all refferences. So when they log on it maps two printers (the original and the new) to the same share and they both get loaded. Hence why deleting one deletes the other. No for the fix...it will either be just change the share to a brand new share name and let the script just map out the new printer ( and just deal with any manually mapped printers on laptops which in the first instance I was trying to avoid but there are only a few anyway) or delve into it a bit deeper and find the rouge refs to the old printer and keep the original share name.

Think it might be the first option first thing in the morning.

This is what happens when you try and sort a problem out before going home knowing that I have a billion and one other jobs to fit in tommorrow! Tech support is so much harder now as the LA has taken over web filtering and most of the technical discussion sites are now blocked which proves really frustrating when a situation like this arises!