Local Printing Problem

Hello,

I am trying to get enable a user to print to his local printer (Dell A920)
when he Remote Controls into our Windows 2003 Terminal Server. I loaded the
print drivers onto the server and a printer sesssion is established when the
user connects, but his is unable to print. A Communication error pops up and
the document just stays in the que of the printer. Any suggestions on how to
troubleshoot and resolve this issue would be appreciated.

Thanks,
Bobby

I will also mention that in the event log the Event ID is 61 and it says that
the "Win32 error code returned by the print processor: 0. The operation
completed successfully."

"Bobby B" wrote:

> Hello,
>
> I am trying to get enable a user to print to his local printer (Dell A920)
> when he Remote Controls into our Windows 2003 Terminal Server. I loaded the
> print drivers onto the server and a printer sesssion is established when the
> user connects, but his is unable to print. A Communication error pops up and
> the document just stays in the que of the printer. Any suggestions on how to
> troubleshoot and resolve this issue would be appreciated.
>
> Thanks,
> Bobby

Hello Bobby ..

I have the same problem .. Event 61 ...can you print with administrator
permission???

Jana

"Bobby B" <BobbyB@discussions.microsoft.com> escreveu na mensagem
news:C59E00EC-44AA-4A49-904C-06C74349A6A6@microsoft.com...
> I will also mention that in the event log the Event ID is 61 and it says
that
> the "Win32 error code returned by the print processor: 0. The operation
> completed successfully."
>
> "Bobby B" wrote:
>
> > Hello,
> >
> > I am trying to get enable a user to print to his local printer (Dell
A920)
> > when he Remote Controls into our Windows 2003 Terminal Server. I loaded
the
> > print drivers onto the server and a printer sesssion is established when
the
> > user connects, but his is unable to print. A Communication error pops
up and
> > the document just stays in the que of the printer. Any suggestions on
how to
> > troubleshoot and resolve this issue would be appreciated.
> >
> > Thanks,
> > Bobby

Hi Janaina, no I cannot print with Administrator permissions. I think Event
61 is referring to the deletion of the document in the que.
The user can see the printer in his Terminal Server session, so does that
mean the printer was redirectly successfully? But if he tries to print, he
gets a communication error. It is listing the port as a TS port in the
printer properties.

"Janaina Rodrigues" wrote:

> Hello Bobby ..
>
> I have the same problem .. Event 61 ...can you print with administrator
> permission???
>
> Jana
>
> "Bobby B" <BobbyB@discussions.microsoft.com> escreveu na mensagem
> news:C59E00EC-44AA-4A49-904C-06C74349A6A6@microsoft.com...
> > I will also mention that in the event log the Event ID is 61 and it says
> that
> > the "Win32 error code returned by the print processor: 0. The operation
> > completed successfully."
> >
> > "Bobby B" wrote:
> >
> > > Hello,
> > >
> > > I am trying to get enable a user to print to his local printer (Dell
> A920)
> > > when he Remote Controls into our Windows 2003 Terminal Server. I loaded
> the
> > > print drivers onto the server and a printer sesssion is established when
> the
> > > user connects, but his is unable to print. A Communication error pops
> up and
> > > the document just stays in the que of the printer. Any suggestions on
> how to
> > > troubleshoot and resolve this issue would be appreciated.
> > >
> > > Thanks,
> > > Bobby
>
>
>

Sounds like the printer driver is not TS compatible.
Have you tried to map the printer to a native driver? Details are
here:

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
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---

"=?Utf-8?B?Qm9iYnkgQg==?=" <BobbyB@discussions.microsoft.com>
wrote on 17 dec 2004 in microsoft.public.win2000.termserv.apps:

> Hi Janaina, no I cannot print with Administrator permissions. I
> think Event 61 is referring to the deletion of the document in
> the que. The user can see the printer in his Terminal Server
> session, so does that mean the printer was redirectly
> successfully? But if he tries to print, he gets a communication
> error. It is listing the port as a TS port in the printer
> properties.
>
> "Janaina Rodrigues" wrote:
>
>> Hello Bobby ..
>>
>> I have the same problem .. Event 61 ...can you print with
>> administrator permission???
>>
>> Jana
>>
>> "Bobby B" <BobbyB@discussions.microsoft.com> escreveu na
>> mensagem
>> news:C59E00EC-44AA-4A49-904C-06C74349A6A6@microsoft.com...
>> > I will also mention that in the event log the Event ID is 61
>> > and it says
>> that
>> > the "Win32 error code returned by the print processor: 0. The
>> > operation completed successfully."
>> >
>> > "Bobby B" wrote:
>> >
>> > > Hello,
>> > >
>> > > I am trying to get enable a user to print to his local
>> > > printer (Dell
>> A920)
>> > > when he Remote Controls into our Windows 2003 Terminal
>> > > Server. I loaded
>> the
>> > > print drivers onto the server and a printer sesssion is
>> > > established when
>> the
>> > > user connects, but his is unable to print. A Communication
>> > > error pops
>> up and
>> > > the document just stays in the que of the printer. Any
>> > > suggestions on
>> how to
>> > > troubleshoot and resolve this issue would be appreciated.
>> > >
>> > > Thanks,
>> > > Bobby