Vista, 2003 Terminal and printing

[Freaky]

Hey there,

we're having issues with Windows Vista and printing from terminal
server. This works fine when using WindowsXP.

We have the issue with multiple printers. For example the Brother
HL-2030. The Brother HL-2030 works fine with 2000/XP/2003 over terminal,
but not with Vista, in the system logs there are also entries that a
driver for Brother HL-2030 could not be found.

According to the helpdesk this probably has to do with the different
driver model for Vista. For 2000/XP/2003 the drivers are the same, but
this isn't the case with Vista, therefore 2003 probably sees it as a
different driver than the one it has.

Can anyone shed more light on this and perhaps a solution? A better
understanding of where it goes wrong would be great, but solving it
would be better .

TIA

Regards

 

[Vera Noest [MVP]]

Re: Vista, 2003 Terminal and printing

Try mapping the Brother HL-2030 driver for Vista to the existing
Brother HL-2030 driver on the server. Be carefull to use the
*exact* driver name which is reported in the EventLog, driver names
are case sensitive.
Detailed instructions here (applies to 2003 as well):

239088 - Windows 2000 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 ___

Freaky <wontsay@ondeja.com> wrote on 12 jul 2007 in
microsoft.public.windows.terminal_services:

> Hey there,
>
> we're having issues with Windows Vista and printing from
> terminal server. This works fine when using WindowsXP.
>
> We have the issue with multiple printers. For example the
> Brother HL-2030. The Brother HL-2030 works fine with
> 2000/XP/2003 over terminal, but not with Vista, in the system
> logs there are also entries that a driver for Brother HL-2030
> could not be found.
>
> According to the helpdesk this probably has to do with the
> different driver model for Vista. For 2000/XP/2003 the drivers
> are the same, but this isn't the case with Vista, therefore 2003
> probably sees it as a different driver than the one it has.
>
> Can anyone shed more light on this and perhaps a solution? A
> better understanding of where it goes wrong would be great, but
> solving it would be better .
>
> TIA
>
> Regards