Re: Printers not auto created in W2003 SP1
- From: "Vera Noest [MVP]" <Vera.Noest@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 03 Mar 2006 07:37:10 -0800
OK, can you log on to the TS through an rdp session and then
connect to a shared network printer? And can you print then?
I'm trying to find out if you cannot print at all any more, or if
the printers are not redirected anymore.
If you can print to a printer which is setup locally on the TS,
then many someone has temporarily disabled printer redirection
completely?
Have you checked the settings on the rdp-tcp properties tabs?
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
SQL troubleshooting: http://sql.veranoest.net
*----------- Please reply in newsgroup -------------*
=?Utf-8?B?TWF1cmljZSBXYWxzaA==?=
<MauriceWalsh@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on 03 mar 2006:
It was "Working OK" (most clients were able to print) compared.
to now (no one can print).
The spooler service is running, I think someone yesterday ran
the cleanspl.exe to try and sort out the issues with the spooler
needing to be restarted, but since then nothing can print.
I've set up the FPD, so once we get it printing again things
should be better.
Maurice
"Vera Noest [MVP]" wrote:
Is the spooler service running?
I find this an interesting remark:
that was working ok (the spooler service died every now and
then)
I would say that it was *not* working OK!
In 99,99% of the cases, a crashing spooler is caused by a 3rd
party printer driver on your Terminal Server. Those are usually
not TS compatible and are known to crash the spooler or the
whole server.
So I would start to uninstall every driver on your system which
didn't come with the OS.
Then map all printers which are not autocreated to a native
driver, or use a Fallback driver.
239088 - Windows 2000 Terminal Services Server Logs Events
1111, 1105, and 1106
http://support.microsoft.com/?kbid=239088
How Microsoft's Windows 2003 SP1 Fallback Printer Driver Works
- by Stefan Vermeulen
http://www.brianmadden.com/content/content.asp?ID=438
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
SQL troubleshooting: http://sql.veranoest.net
*----------- Please reply in newsgroup -------------*
=?Utf-8?B?TWF1cmljZSBXYWxzaA==?=
<MauriceWalsh@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on 03 mar 2006:
Hi All,
I have a Windows 2003 server with SP1 running terminal
services that was working ok (the spooler service died every
now and then) until a couple of days ago, something happened
(i.e. someone tried to fix it and I can't find out what they
done) and now we can't get it to print at all.
When I connect using RDP there are no printers setup
automatically, there is nothing in the event viewer about the
printers.
I've rebooted the server but that has not helped.
Any one got any idea ? or pointers to how to debug this ?
Thanks
Maurice
- Follow-Ups:
- Re: Printers not auto created in W2003 SP1
- From: Maurice Walsh
- Re: Printers not auto created in W2003 SP1
- References:
- Re: Printers not auto created in W2003 SP1
- From: Vera Noest [MVP]
- Re: Printers not auto created in W2003 SP1
- From: Maurice Walsh
- Re: Printers not auto created in W2003 SP1
- Prev by Date: Re: Printers not auto created in W2003 SP1
- Next by Date: Re: Printers not auto created in W2003 SP1
- Previous by thread: Re: Printers not auto created in W2003 SP1
- Next by thread: Re: Printers not auto created in W2003 SP1
- Index(es):
Relevant Pages
|