Re: Remote Desktop to Server 2003 Printer Issue
I hope this explanation helps.
The server that we are trying to RDP into is just a server that Sys Admin's
in our business connect to. Normal users never end up connecting to it
through RDP and it is not a terminal server. We are using "terminal
services" to Remote into the server but this is not a terminal server. We
actually don't have a terminal server in our business, that is to say we only
use the client to client terminal services on our internal network through
RDP.
As for errors. We aren't seeing any errors on the server we are "remoted"
into or on the PC that we are "remoting" from.
So maybe the best way to describe this, is step by step.
-So first I open a remote desktop connection and type in the server that I
am connecting to. Which does happen to be the print server for most all of
the printers in our network.
-Once I am logged in remotely to this server from my PC, I start to see
print jobs popping into this printer's queue on MY PC. You can also see this
print jobs accumulating on the print server by going into printers and faxes
on the server and checking this particular's printers queue.
-If I log out of the remote session these print jobs will stop being queued
up.
They will eventually say they are printing and will take themselves out of
the queue when finished but the wierd thing is, the printer printed nothing
from these jobs. It didn't even print a blank sheet of paper, it just never
printed anything. Yet the jobs are cleared out of the queue like they had
been printed.
In regards to your question about the print drivers for this printer and if
they are terminal services compliant, I will have to do some more research to
find that out. If I do find something in regards to this from the
manufactuer I will let you know what happens when installing those new
drivers. Although I have noticed that this issue will send these "ghost"
print jobs to other printers listed in my local printers and faxes, such as
the Adobe PDF printer or another network printer.
I hope this clears things up. Again, let me know if you need more
information.
Thanks for your help,
--
Jake
"Anthony [MVP]" wrote:
> Which server is the Terminal Server that people are using? Is it also the
> Print Server?
> What errors do you have on the Terminal Server for all the failed print
> jobs?
> Does the printer/copier have terminal services-compliant drivers?
> Anthony,
> http://www.airdesk.com
>
>
>
> "jacob@nowhere.com" <jacobnowherecom@discussions.microsoft.com> wrote in
> message news:CE0A49F7-0AE0-4D8D-A88A-E06290CDB61F@microsoft.com...
> > I will try and answer all the questions you just sent but if I miss any
> > just
> > let me know and I will respond as quick as I can.
> >
> > So right now the printer that keeps getting these print jobs is a color
> > laser high output printer/copier in our office. This printer is available
> > through a print server. This print server just so happens to BE the
> > server
> > that I am connecting to via RDP.
> >
> > The print jobs are all remote desktop redirected print jobs. They all get
> > sent to the printer but they never end up getting printed or even look
> > like
> > they are in the printer/copier's queue at it's console.
> >
> > Let me know if you need any more information.
> >
> > Thanks for your help,
> >
> > -Jake
> >
> >
> > --
> > Jake
> >
> >
> > "Anthony [MVP]" wrote:
> >
> >> Jake,
> >> We should be able to narrow this down.
> >> Who is creating the print jobs and on what printer? They are obviously
> >> not
> >> receiving their job.
> >> What is the connection, if any, between the printer the print jobs were
> >> sent
> >> to and the printer on your local PC that they are arriving at?
> >> How is your PC connected to the printer that is receiving the print jobs:
> >> is
> >> it directly connected or a network printer? If network, what is the print
> >> server? Is it the server you are RDPing to?
> >> Anthony,
> >> http://www.airdesk.com
> >>
> >>
> >> "Roger" <Roger@discussions.microsoft.com> wrote in message
> >> news:87FF1870-C460-4EC3-AF0A-A3536071D64D@microsoft.com...
> >> > Jake,
> >> > This is not an answer to your question/problem, I have exacty the same
> >> > issue and I am tearing my already in short supply hair out! Did you
> >> > find
> >> > a
> >> > solution, r has any one out there got a solution t mulltiple Remote
> >> > Desktop
> >> > Redirected Printer Doc 's eing produced when logging in to our 2003
> >> > Windows
> >> > Server, we use a SBS server as a Domain controller and Exchange server.
> >> > Thanks in advanve!
> >> > Roger
> >> >
> >> > "jacob@nowhere.com" wrote:
> >> >
> >> >> Hello,
> >> >>
> >> >> I am having an issue where I am logging in to a Windows Server 2003
> >> >> server
> >> >> from a Remote Desktop Session and have checked the option to use the
> >> >> local
> >> >> printers installed on the PC I am "RDPing" from as resources in my RDP
> >> >> session.
> >> >>
> >> >> Once I get logged into the server I start receiving a huge amount of
> >> >> "Remote
> >> >> Desktop Redirected Printer Doc" entires(print jobs) in at least two of
> >> >> my
> >> >> print queues on my local machine. This happens everytime I RDP to
> >> >> this
> >> >> server and I am not creating any print jobs on the server at all.
> >> >> They
> >> >> never
> >> >> stop being sent and they will eventually bring one of my print queues
> >> >> down
> >> >> till I clear out all the excess print jobs.
> >> >>
> >> >> Of course if I uncheck the box to use the printers on my local machine
> >> >> as
> >> >> a
> >> >> resource during the RDP session, the issue will not occur but I would
> >> >> like to
> >> >> see some type of better solution than this as I would rather not have
> >> >> to
> >> >> worry about doing that every time I need to RDP to this server. If
> >> >> anyone
> >> >> has any information regarding this it is much appreciated.
> >> >>
> >> >> Thanks,
> >> >>
> >> >> --
> >> >> Jake
> >>
> >>
> >>
>