Guest HDI Posted September 3, 2008 Posted September 3, 2008 Hi, I've got a user who works at home with windows vista and he has a brother hl-5240. When he makes connection to our terminal server 2003 via RDP he can't see the printer and we reveive event id 1111 in our event log. There is a driver installed on our terminal server 2003 for windows 2000, xp and 2003. How can we solve this? Do I have to install the driver for windows vista on our terminal server 2003? Thx.
Guest Vera Noest [MVP] Posted September 3, 2008 Posted September 3, 2008 Re: Windows Vista client printing on terminal server 2003 This is probably a name mismatch problem. You can use the information from the EventID 1111 to map the vist driver name to the existing driver name on the server, using this article: 239088 - Windows 2000 or Windows Server 2003 Terminal Services server logs events 1111, 1105, and 1106 http://support.microsoft.com/?kbid=239088 _________________________________________________________ Vera Noest MCSE, CCEA, Microsoft MVP - Terminal Server TS troubleshooting: http://ts.veranoest.net ___ please respond in newsgroup, NOT by private email ___ HDI <hdinf@hotmail.com> wrote on 03 sep 2008 in microsoft.public.windows.terminal_services: > Hi, > > I've got a user who works at home with windows vista and he has > a brother hl-5240. > > When he makes connection to our terminal server 2003 via RDP he > can't see the printer and we reveive event id 1111 in our event > log. > > There is a driver installed on our terminal server 2003 for > windows 2000, xp and 2003. > > How can we solve this? > Do I have to install the driver for windows vista on our > terminal server 2003? > > Thx.
Guest HDI Posted September 4, 2008 Posted September 4, 2008 Re: Windows Vista client printing on terminal server 2003 On 3 sep, 15:13, "Vera Noest [MVP]" <vera.no...@remove- this.hem.utfors.se> wrote: > This is probably a name mismatch problem. You can use the > information from the EventID 1111 to map the vist driver name to > the existing driver name on the server, using this article: > > 239088 - Windows 2000 or Windows Server 2003 Terminal Services > server logs events 1111, 1105, and 1106http://support.microsoft.com/?kbid=239088 > > _________________________________________________________ > Vera Noest > MCSE, CCEA, Microsoft MVP - Terminal Server > TS troubleshooting: http://ts.veranoest.net > ___ please respond in newsgroup, NOT by private email ___ > > HDI <hd...@hotmail.com> wrote on 03 sep 2008 in > microsoft.public.windows.terminal_services: > > > > > Hi, > > > I've got a user who works at home with windows vista and he has > > a brother hl-5240. > > > When he makes connection to our terminal server 2003 via RDP he > > can't see the printer and we reveive event id 1111 in our event > > log. > > > There is a driver installed on our terminal server 2003 for > > windows 2000, xp and 2003. > > > How can we solve this? > > Do I have to install the driver for windows vista on our > > terminal server 2003? > > > Thx.- Tekst uit oorspronkelijk bericht niet weergeven - > > - Tekst uit oorspronkelijk bericht weergeven - When I was checking the drivers I noticed that for the brother hl-5240 there are two drivers: 'Brother HL-5240' and 'Brother HL-5240 series' The event log shows 'Brother HL-5240' and on the server 'Brother HL-5240 series' is installed. What is the difference? Can I install the 'Brother HL-5240' on the server?
Guest Vera Noest [MVP] Posted September 4, 2008 Posted September 4, 2008 Re: Windows Vista client printing on terminal server 2003 HDI <hdinf@hotmail.com> wrote on 04 sep 2008: > On 3 sep, 15:13, "Vera Noest [MVP]" <vera.no...@remove- > this.hem.utfors.se> wrote: >> This is probably a name mismatch problem. You can use the >> information from the EventID 1111 to map the vist driver name >> to the existing driver name on the server, using this article: >> >> 239088 - Windows 2000 or Windows Server 2003 Terminal Services >> server logs events 1111, 1105, and >> 1106http://support.microsoft.com/?kbid > =239088 >> >> _________________________________________________________ >> Vera Noest >> MCSE, CCEA, Microsoft MVP - Terminal Server >> TS troubleshooting: http://ts.veranoest.net >> ___ please respond in newsgroup, NOT by private email ___ >> >> HDI <hd...@hotmail.com> wrote on 03 sep 2008 in >> microsoft.public.windows.terminal_services: >> >> >> >> > Hi, >> >> > I've got a user who works at home with windows vista and he >> > has a brother hl-5240. >> >> > When he makes connection to our terminal server 2003 via RDP >> > he can't see the printer and we reveive event id 1111 in our >> > event log. >> >> > There is a driver installed on our terminal server 2003 for >> > windows 2000, xp and 2003. >> >> > How can we solve this? >> > Do I have to install the driver for windows vista on our >> > terminal server 2003? > > When I was checking the drivers I noticed that for the brother > hl-5240 there are two drivers: > 'Brother HL-5240' and 'Brother HL-5240 series' > > The event log shows 'Brother HL-5240' and on the server 'Brother > HL-5240 series' is installed. > > What is the difference? > Can I install the 'Brother HL-5240' on the server? Have you read the article? You don't have to install anything. This is exactly what I meant with a name mismatch. You have to tell the server that the two names mean the same. Example: HP LaserJet is *not* equal to HP Laserjet _________________________________________________________ Vera Noest MCSE, CCEA, Microsoft MVP - Terminal Server TS troubleshooting: http://ts.veranoest.net *----------- Please reply in newsgroup -------------*
Guest HDI Posted September 8, 2008 Posted September 8, 2008 Re: Windows Vista client printing on terminal server 2003 On 4 sep, 16:17, "Vera Noest [MVP]" <Vera.No...@remove- this.hem.utfors.se> wrote: > HDI <hd...@hotmail.com> wrote on 04 sep 2008: > > > > > > > On 3 sep, 15:13, "Vera Noest [MVP]" <vera.no...@remove- > > this.hem.utfors.se> wrote: > >> This is probably a name mismatch problem. You can use the > >> information from the EventID 1111 to map the vist driver name > >> to the existing driver name on the server, using this article: > > >> 239088 - Windows 2000 or Windows Server 2003 Terminal Services > >> server logs events 1111, 1105, and > >> 1106http://support.microsoft.com/?kbid > > =239088 > > >> _________________________________________________________ > >> Vera Noest > >> MCSE, CCEA, Microsoft MVP - Terminal Server > >> TS troubleshooting: http://ts.veranoest.net > >> ___ please respond in newsgroup, NOT by private email ___ > > >> HDI <hd...@hotmail.com> wrote on 03 sep 2008 in > >> microsoft.public.windows.terminal_services: > > >> > Hi, > > >> > I've got a user who works at home with windows vista and he > >> > has a brother hl-5240. > > >> > When he makes connection to our terminal server 2003 via RDP > >> > he can't see the printer and we reveive event id 1111 in our > >> > event log. > > >> > There is a driver installed on our terminal server 2003 for > >> > windows 2000, xp and 2003. > > >> > How can we solve this? > >> > Do I have to install the driver for windows vista on our > >> > terminal server 2003? > > > When I was checking the drivers I noticed that for the brother > > hl-5240 there are two drivers: > > 'Brother HL-5240' and 'Brother HL-5240 series' > > > The event log shows 'Brother HL-5240' and on the server 'Brother > > HL-5240 series' is installed. > > > What is the difference? > > Can I install the 'Brother HL-5240' on the server? > > Have you read the article? > You don't have to install anything. > This is exactly what I meant with a name mismatch. You have to tell > the server that the two names mean the same. > Example: HP LaserJet is *not* equal to HP Laserjet > _________________________________________________________ > Vera Noest > MCSE, CCEA, Microsoft MVP - Terminal Server > TS troubleshooting: http://ts.veranoest.net > *----------- Please reply in newsgroup -------------*- Tekst uit oorspronkelijk bericht niet weergeven - > > - Tekst uit oorspronkelijk bericht weergeven - Yes I have read the article and made the changes. I am now waiting for response from the user. I was just wondering why there are two drivers for this printer.
Guest Vera Noest [MVP] Posted September 8, 2008 Posted September 8, 2008 Re: Windows Vista client printing on terminal server 2003 HDI <hdinf@hotmail.com> wrote on 08 sep 2008 in microsoft.public.windows.terminal_services: > On 4 sep, 16:17, "Vera Noest [MVP]" <Vera.No...@remove- > this.hem.utfors.se> wrote: >> HDI <hd...@hotmail.com> wrote on 04 sep 2008: >> >> > On 3 sep, 15:13, "Vera Noest [MVP]" <vera.no...@remove- >> > this.hem.utfors.se> wrote: >> >> This is probably a name mismatch problem. You can use the >> >> information from the EventID 1111 to map the vist driver >> >> name to the existing driver name on the server, using this >> >> article: >> >> >> 239088 - Windows 2000 or Windows Server 2003 Terminal >> >> Services server logs events 1111, 1105, and >> >> 1106http://support.microsoft.com/?kbid >> > =239088 >> >> >> HDI <hd...@hotmail.com> wrote on 03 sep 2008 in >> >> microsoft.public.windows.terminal_services: >> >> >> > Hi, >> >> >> > I've got a user who works at home with windows vista and >> >> > he has a brother hl-5240. >> >> >> > When he makes connection to our terminal server 2003 via >> >> > RDP he can't see the printer and we reveive event id 1111 >> >> > in our event log. >> >> >> > There is a driver installed on our terminal server 2003 >> >> > for windows 2000, xp and 2003. >> >> >> > How can we solve this? >> >> > Do I have to install the driver for windows vista on our >> >> > terminal server 2003? >> >> > When I was checking the drivers I noticed that for the >> > brother hl-5240 there are two drivers: >> > 'Brother HL-5240' and 'Brother HL-5240 series' >> >> > The event log shows 'Brother HL-5240' and on the server >> > 'Brother HL-5240 series' is installed. >> >> > What is the difference? >> > Can I install the 'Brother HL-5240' on the server? >> >> Have you read the article? >> You don't have to install anything. >> This is exactly what I meant with a name mismatch. You have to >> tell the server that the two names mean the same. >> Example: HP LaserJet is *not* equal to HP Laserjet > > Yes I have read the article and made the changes. I am now > waiting for response from the user. > > I was just wondering why there are two drivers for this printer. Well, you mentioned that you installed the same driver for 3 different OS versions on the server. It's not uncommon that the driver name changes somewhat between versions, as in your case. _________________________________________________________ Vera Noest MCSE, CCEA, Microsoft MVP - Terminal Server TS troubleshooting: http://ts.veranoest.net ___ please respond in newsgroup, NOT by private email ___
Recommended Posts