Re: Strange printer Behaviour!!!
A crashing printer is nearly always a sign of a bad printer driver,
which isn't TS compatible. That situation is not solved by
installing SP2 and re-installing the drivers.
I would completely uninstall every 3rd party driver, then let users
connect. The EventLog will tell you which drivers are missing, and
you can then map them one after the other to a native driver.
239088 - Windows 2000 or Windows Server 2003 Terminal Services
server logs events 1111, 1105, and 1106
http://support.microsoft.com/?kbid=239088
Or you can define a fallback printer driver.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting:
http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
=?Utf-8?B?U2ViYXN0aWVu?= <Sebastien@discussions.microsoft.com>
wrote on 02 dec 2007 in
microsoft.public.windows.terminal_services:
> I've tried the latest RDP client too....no luck
>
> "Sebastien" wrote:
>
>> na, I installed the SP just because I realised while I was
>> doing the cleanspl.exe that this client was on SP1. the problem
>> I had originally with the server was the print spooler kept
>> crashing and I cleaned it with cleanspl.exe
>>
>> "Vera Noest [MVP]" wrote:
>>
>> > And the default printers are network printers, I guess?
>> > If so, update one of the workstations with the rdp client
>> > that comes with 2003 SP2, to see if that solves the problem.
>> > You can find the rdp client on your server, in
>> > C:\WINDOWS\system32\clients\tsclient\win32\msrdpcli.msi
>> >
>> > I'm also wondering what your previous printer problems were.
>> > Installing an SP seldom fixes an existing problem, unless
>> > there is a specific hotfix for the problem included in the
>> > SP. _________________________________________________________
>> > Vera Noest
>> > MCSE, CCEA, Microsoft MVP - Terminal Server
>> > TS troubleshooting: http://ts.veranoest.net
>> > ___ please respond in newsgroup, NOT by private email ___
>> >
>> > =?Utf-8?B?U2ViYXN0aWVu?=
>> > <Sebastien@discussions.microsoft.com> wrote on 02 dec 2007 in
>> > microsoft.public.windows.terminal_services:
>> >
>> > > actually, sorry. There are some event viewer entries for
>> > > driver mismatches, but not for the default printers. and
>> > > thats for all the users?
>> > >
>> > > "Vera Noest [MVP]" wrote:
>> > >
>> > >> No EventID 1111 and/or 1106?
>> > >> And the Print Spooler service is running?
>> > >> That means that the server doesn't even try to redirect
>> > >> the printers. Have you doublechecked the settings in
>> > >> Terminal Services Configuration about printer redirection?
>> > >> _________________________________________________________
>> > >> Vera Noest
>> > >> MCSE, CCEA, Microsoft MVP - Terminal Server
>> > >> TS troubleshooting: http://ts.veranoest.net
>> > >> ___ please respond in newsgroup, NOT by private email ___
>> > >>
>> > >> =?Utf-8?B?U2ViYXN0aWVu?=
>> > >> <Sebastien@discussions.microsoft.com> wrote on 02 dec 2007
>> > >> in microsoft.public.windows.terminal_services:
>> > >>
>> > >> > Good morning All
>> > >> >
>> > >> > I've got a 2003 Server which I updated to SP2 yesterday.
>> > >> > I also cleared the printer spooler using cleanspl.exe as
>> > >> > I was having problems with the printer queue.
>> > >> >
>> > >> > I've reinstalled the printer drivers, etc and printing
>> > >> > from the server directly to the printers works fine. But
>> > >> > now, when a client logs in via TS, their printers are
>> > >> > not brough across. I've made sure the drivers are
>> > >> > identical, etc but nothing. Nothing in the error logs
>> > >> > either.
>> > >> >
>> > >> > I've also ensured that all ports are forwarded as per
>> > >> > kb302361.....
>> > >> >
>> > >> > I'm about to tear my hair out now!!! Not sure what else
>> > >> > to do for this customer
>> > >> >
>> > >> > Anyone ever experience this?