RMGBEU
asked on
Terminal Server 2003 suddenly using fallback driver for all printers
Last week we started noticing that remote users were all getting the fallback printer driver. Same users have been fine for months but now no matter what we do the fallback printer driver always takes over. Drivers are still showing installed, printers are still being created. Works ok for some users but most have issues with print being cutoff. Using the HP 550c as the fallback driver.
So we are getting the typical error in the system log saying the printer driver is not found. Some of the logins generate a strange DCOM error :1009: DCOM was unable to communicate with the computer xxxxx using any of the configured protocols.
I've searched this error but nothing matches with our environment. I've had 3 of the users reinstall printer drivers at home and we have tried reinstalling drivers on the terminal server. Clients are XP/Vista Windows 7 so that doesn't seem to matter. Any other ideas?
So we are getting the typical error in the system log saying the printer driver is not found. Some of the logins generate a strange DCOM error :1009: DCOM was unable to communicate with the computer xxxxx using any of the configured protocols.
I've searched this error but nothing matches with our environment. I've had 3 of the users reinstall printer drivers at home and we have tried reinstalling drivers on the terminal server. Clients are XP/Vista Windows 7 so that doesn't seem to matter. Any other ideas?
digitap
I don't understand what you mean by fallback printer. Are printers other than a HP 550C getting this driver...is that what you mean by fallback printer?
ASKER
I meant the fallback printer driver. We have set the fallback printer driver to the HP550C as this is supposed to be a fairly generic HP driver.
For example a user connects from home with a hp laserjet 1200 connected to their home computer. Even though the HP laserjet 1200 driver is installed on our terminal server, the session ignores it and uses the fallback printer driver (HP550C). This started last week for all of our users.
For example a user connects from home with a hp laserjet 1200 connected to their home computer. Even though the HP laserjet 1200 driver is installed on our terminal server, the session ignores it and uses the fallback printer driver (HP550C). This started last week for all of our users.
OK...I understand what you mean by fallback. The error you indicate in the question, do you see that when they login?
ASKER
Yes. However the error doesn't appear every time. A user just logged in: DCOM error first in evnt log, then the typical printer driver not found 1501 warnings.
when a user logs on and does NOT get the error, can they print?
ASKER
Printers are mapped regardless of the DCOM error--so the error doesn't seem to affect the connection of printers.
I'm noticing now that it also doesn't seem to affect the driver issue either. The users that don't get the DCOM error also have the fallback printer driver and not their installed driver. So now every user is connected and using the fallback printer driver. And yes they have printers that have drivers installed on the server as this worked just last week and has for for over a year.
So now i'm not sure where to look...
I'm noticing now that it also doesn't seem to affect the driver issue either. The users that don't get the DCOM error also have the fallback printer driver and not their installed driver. So now every user is connected and using the fallback printer driver. And yes they have printers that have drivers installed on the server as this worked just last week and has for for over a year.
So now i'm not sure where to look...
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Will try the tool this week and report. It is odd that it worked for 18 months and now fails.
i understand...i face that constantly with MS products.
ASKER
Well was going to do some testing today and happened to glance at the printers on the server. There are four printers that took the correct driver from the server (instead of the fallback printer). I'm still going to run the tool but this looks like it is working now.
The fallback printer works great in the situations where people have the OfficeJet printers at home. You cannot find a driver for these things without installing the annoying HP software. That's why I deal with it.
The fallback printer works great in the situations where people have the OfficeJet printers at home. You cannot find a driver for these things without installing the annoying HP software. That's why I deal with it.
yes...i hate the hp software they want you to install...they should make a special server aware client so you don't have to install all the other crap. it's like microsoft and IE. i've installed IE on a server...figure it out. instead, though, when i launch IE, it wants me to run the stupid IE wizard, THEN it defaults to the flash bloated MSN website...all this through TS session!!!! Sigh...
ASKER
I think your option to use the wizard would work. However, I have about 200 printers that are mapped daily so honestly I don't have the time to load drivers for each user from their home printer.
In the end, I had the two problem users download the same driver i had on the server and then it started working. One of the users had HP Laserjet P1006 PCL while the server had the driver as HP Laserjet P1006 PCL 5e. Once the driver names were the same it loaded the right driver on user login to the term server. Fun
In the end, I had the two problem users download the same driver i had on the server and then it started working. One of the users had HP Laserjet P1006 PCL while the server had the driver as HP Laserjet P1006 PCL 5e. Once the driver names were the same it loaded the right driver on user login to the term server. Fun
yes, i don't know why printing has to be such a pain...HP has started making universal drivers for their printers but they don't work woth spit. i don't think they'll ever figure it out...thanks for the points.