Re: unable to print to locally attached printer

Tech-Archive recommends: Speed Up your PC by fixing your registry

I contacted Microsoft and the following solution was used to resolve our
problem:

Cause
======
The culprit is available terminal server ports and reported terminal server
ports in registry don’t match. The difference can be brought by either
unexpected disconnection or third party programs.

Resolution
========
We use the following method to consolidate these two values and this
resolved the problem.

1). Run regedit in the command prompt to open registry editor

2). Go to the following location where TS Ports are defined:


HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceClasses\{28d78fad-5a12-11d1-ae5b-

0000f803a8c2}\##?#Root#RDPDR#0000#{28d78fad-5a12-11d1-ae5b-0000f803a8c2}

3). Under "##?#Root#RDPDR#0000#{28d78fad-5a12-11d1-ae5b-0000f803a8c2}" we
removed
all sub keys starting with #TS (#TS001, #TS002 etc)

4). Then navigate the following registry key and set the "ReferenceCount" to
0 in the right pane.


HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceClasses\{28d78fad-5a12-11d1-ae5b-

0000f803a8c2}\##?#Root#RDPDR#0000#{28d78fad-5a12-11d1-ae5b-0000f803a8c2}\Control

5). After the modification, restarted spooler service and log on back to
terminal
session. Now we checked that redirected printers are working fine

Note: before changing any registry value take the backup of it


Also note that we first tried three steps which did not solve the problem,
although it may have been beneficial in the end. We removed 3rd party print
processors and then removed 3rd party print monitors, this being done after
we deleted the BUD files from following location:
C:\WINDOWS\system32\spool.

--
Buddy
Consultant
MCSE


"Makarand [MS]" wrote:

Buddy,

1) Could you ask client to save the related Events and post it here? perhaps
the data associated with events could help finding the issue.

2) Can you also try uninstalling all the Printer drivers from server
machine. Control Panel / Printer / Server properties / Drivers / Remove. and
retrying the printer redirection to see if it helps.

Thanks,
Makarand [MSFT]

"Buddy" <Buddy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:799FBFF4-1C1B-4EE0-BFCC-73388FE4BA88@xxxxxxxxxxxxxxxx
I have a client that recently experienced a power outage. Since that power
outage, they are no longer able to print to their locally attached
printers.
A variety of printers are affected - laser printers, ink jet printers,
parallel printers, usb printers. None are able to print to their attached
printer.
The printers all print fine locally from the PC. If their printer is
shared
from their PC, and then within terminal services if it is added as a
network
printer, printing is successful. In fact, all network defined printers
have
no problems being printed to within terminal services sessions.
They are running Windows Server 2003 as their terminal server. An upgrade
was made to SP2 in hopes that whatever failed in the power outage would be
replaced/corrected with the service pack install.
I have noticed in the server's system event log that there are multiple
occurrences of event ID 9 stating that the printer was set. I believe
this
is supposed to happen only once. In addition, event ID 42 appears later
indicating that the printer was successfully unpublished.
Printing was working fine prior to the power outage. My suspicion is that
a
file has become corrupted on the server that is key to printer
redirection.
But I don't know which one(s).
Any ideas?
TIA

--
Buddy
Consultant
MCSE


.

Quantcast