Local Printers not recognized
in [Terminal Services]
|
From: Stefan Vermeulen on 15 Mar 2006 16:07 Printernames are CaSe SenSative, so yo umight need to map the client name to the servername: http://support.microsoft.com/default.aspx?scid=kb;en-us;239088 Stefan http://www.printingsupport.com "Chris" <Chris(a)discussions.microsoft.com> wrote in message news:1590F016-087D-44F1-A4BC-715C00D20A7E(a)microsoft.com... > > Jeff, > > I tried to install the HP895 printer drivers, but that did not help. As > for > the other printer driver errors in the event logs, would it help to just > remove them so that they are not trying to connect? If so, any ideas how > to > remove them? > > thx...Chris > > "Jeff Pitsch" wrote: > >> The HP895 may be a standard driver but even windows cd drivers are not >> installed automatically on OS installation. They must be added just like >> any other driver. >> >> As for the other drivers, I would recommend testing them thoroughly first >> to >> make sure they do not cause problems with the terminal server. Most >> problems in a TS environment are caused by bad 3rd party print drivers. >> My >> other recommendation would be to only install the drivers and not the >> extraneous software that comes with them. >> >> If you are on windows 2003 sp1 you could also try using the fallback >> drivers. >> >> Jeff Pitsch >> Microsoft MVP - Terminal Services >> http://www.sbcgatekeeper.com >> Your Terminal Services Security Website >> >> "Chris" <Chris(a)discussions.microsoft.com> wrote in message >> news:1BDDA612-4CB8-4904-B5F4-58AC4FE15C82(a)microsoft.com... >> > The errors in the event log are for three other printers... The printer >> > I >> > have attached is an HP895 deskjet printer, which is a standard printer >> > driver >> > that is already included in Windows I believe. >> > >> > If I download and install the these other printer drivers, do you think >> > that >> > would fix the problem of it not seeing the HP895? Also, is this the >> > recommended way of installing additional printer drivers on a terminal >> > server: >> > >> > Start - Printers and Faxes - Server Properties - Drivers - Add >> > >> > >> > "Jeff Pitsch" wrote: >> > >> >> The first log message seems to explain it. You do not have the >> >> correct >> >> driver installed on the terminal server. >> >> >> >> Jeff Pitsch >> >> Microsoft MVP - Terminal Services >> >> http://www.sbcgatekeeper.com >> >> Your Terminal Services Security Website >> >> >> >> "Chris" <Chris(a)discussions.microsoft.com> wrote in message >> >> news:911CB3BA-6A63-48C4-BF65-6707C0098448(a)microsoft.com... >> >> >I have Windows 2003 Terminal Services w/ SP1 and when I run an RDP >> >> >session >> >> > from a computer that has a locally attached printer (HP 895), it >> >> > does >> >> > not >> >> > show up under printers. I have the settings defined to redirect >> >> > local >> >> > printers. >> >> > >> >> > I do see in the even logs three errors for other printer types: >> >> > >> >> > Event Type: Error >> >> > Event Source: Print >> >> > Event Category: None >> >> > Event ID: 23 >> >> > Date: 3/9/2006 >> >> > Time: 10:37:39 AM >> >> > User: NT AUTHORITY\SYSTEM >> >> > Computer: SERVER1 >> >> > Description: >> >> > Printer Brother HL-2700CN series failed to initialize because a >> >> > suitable >> >> > Brother HL-2700CN series driver could not be found. >> >> > >> >> > I also see a DCOM error in the event viewer: >> >> > >> >> > Event Type: Error >> >> > Event Source: DCOM >> >> > Event Category: None >> >> > Event ID: 10010 >> >> > Date: 3/9/2006 >> >> > Time: 10:38:43 AM >> >> > User: N/A >> >> > Computer: SERVER1 >> >> > Description: >> >> > The server {323CE21C-A448-40AA-BA74-7FCF1E44106E} did not register >> >> > with >> >> > DCOM >> >> > within the required timeout. >> >> > >> >> > I am thinking of just reinstalling the whole server again, but if >> >> > anyone >> >> > has >> >> > any ideas to try and fix it, I would love to give it a try. >> >> > >> >> > thx... Chris >> >> >> >> >> >> >> >> >> |