"Printer Spooler failed to reopen error" - Server 2008 RW

I have a problem with a terminal server environment I have set up.  There are 3 locations to this set up.  I have a VPN set up at all locations, which is functioning properly.  The server has 2008 R2 64-bit installed, and is acting ONLY as a terimnal server, not a domain.  

The problem I am having is with printing.  I originally added the printers to each remote user by sharing the printer off the user's local machine, then pathing to it ("//computername/printer").  I have verified all the drivers are Server 2008R@ 64-bit compatible as well.  Whats happening the sites will randomly lose their printers.  When this happens I have to recreate the printers by pathing to the IP address instead of the name (//10.0.0.0/printer), which allows the printers to be installed.  Then at random times the IP address mapping will fail, and I have to map to the name again.  

I checked on the server event viewer and keep seeing error's that read :

"The print spooler failed to reopen an existing printer connection because it could not read the configuration information from the registry key S-1-5-21-4019898469-3110971113-3073775663-500\Printers\Connections\,,computername,HP Deskjet 6500 Series. This can occur if the key name or values are malformed or missing."

I am assuming this has something to do with the problem but I have not been successful at identifying what is causing the problem.
Consolidated_TelcomAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

digitapCommented:
I'm puzzled as to why the printers aren't mapped through the TS session.  If the driver isn't available, then you should get an Event log error indicating that a driver could not be found.  Otherwise, you shouldn't have to manually map the printers to the server from the user's workstations.  Did you manually install the drivers by going to Printers > Server Properties > Drivers?  Is the driver on the user's workstation PCL6, PCL5?  Whichever is on the user's workstation, it must match exactly to what's on the server.  If it's PCL6 on the workstation then it must be PCL6 on the server.

If not, then try this.


Go to HKEY_USERS\S-1-5-21-4019898469-3110971113-3073775663-500\Printers. Right click and create a new key named 'Connections'.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server OS

From novice to tech pro — start learning today.