SparkMonkeyHellion
Banned
- Messages
- 546
- Location
- Guantanomo Bay, Cuba
Okay, I would not post this up here except that the problem has escalated from "Annoyance" to "Unique"
The original error was "Printer cannot be removed. Access is denied" - which the solution was to delete the registry entries for the printer. Done. That seems to have cleared up the problems for everyone else who posted that problem on the internet.
The problem then evolved into "Printer cannot be removed. Either the printer name was typed incorrectly..."
I verified that the printer is working properly because I can go straight to it's IP and print, but that's not "best practices" I need to get the share working on the server again.
Another interesting thing is that there are still active sessions from a couple of machines which have been off the network for a while - a couple of months. I'm wondering if that has something to do with it...
It seems that the previous IT goons had their own ideas about "best practices" which has fudged up the printer for everyone else.
The original error was "Printer cannot be removed. Access is denied" - which the solution was to delete the registry entries for the printer. Done. That seems to have cleared up the problems for everyone else who posted that problem on the internet.
The problem then evolved into "Printer cannot be removed. Either the printer name was typed incorrectly..."
I verified that the printer is working properly because I can go straight to it's IP and print, but that's not "best practices" I need to get the share working on the server again.
Another interesting thing is that there are still active sessions from a couple of machines which have been off the network for a while - a couple of months. I'm wondering if that has something to do with it...
It seems that the previous IT goons had their own ideas about "best practices" which has fudged up the printer for everyone else.