Continuing printing problems in RD

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

We use RD to connect 2 veterinary clinics for database sharing purposes. We
got a new computer and printer, and had the connection running successfully,
and printing successfully. However, something changed (I don't know what
changed, I do not work in the offices; only from home)

The printer attached to the local computer is behaving oddly over the
connection. We started out with the printer showing up in the "printers and
faxes" window on the server. When we print, the job shows as printing,
but never actually prints. We cannot delete this job. We tried logging
off and logging back in. The printer and stuck job were still there, but we
then had an additional printer labeled "Dell AI0 946 [From Companion] (copy
1)".

Repeat several times, and now we have 4 copies of the same printer, none of
which will print. We cannot delete either the stuck jobs or the printers
themselves. Net stop/start spooler command has no effect.

I'm assuming this is a problem with either the local printer or computer,
since I can RD in to the server from my home laptop and print to my home
computer with no problems.

How can I troubleshoot why the printer does not print, and how can I remove
the "dead" copies of the printers?
 
hi,
for deleting printers do the follow on terminal server :
stop print spooler; delete all files from %windir%system32/spool/printers ;
start print spooler and now you can delete that "shadow" printers.
 
Thanks for the reply. I have done this. While it provides a temporary
solution and removes the "shadow" printers, it still does not fix the
original problem, that the print job just sits in the queue on the server,
and never prints to the client computer's printer. If I could get the
printer to actually print, that would be GREAT! I'm banging my head on the
wall here! :-)

CJ

Dragos CAMARA said:
hi,
for deleting printers do the follow on terminal server :
stop print spooler; delete all files from %windir%system32/spool/printers ;
start print spooler and now you can delete that "shadow" printers.

--
Dragos CAMARA
MCSA Windows 2003 server


Huskies4all said:
We use RD to connect 2 veterinary clinics for database sharing purposes. We
got a new computer and printer, and had the connection running successfully,
and printing successfully. However, something changed (I don't know what
changed, I do not work in the offices; only from home)

The printer attached to the local computer is behaving oddly over the
connection. We started out with the printer showing up in the "printers and
faxes" window on the server. When we print, the job shows as printing,
but never actually prints. We cannot delete this job. We tried logging
off and logging back in. The printer and stuck job were still there, but we
then had an additional printer labeled "Dell AI0 946 [From Companion] (copy
1)".

Repeat several times, and now we have 4 copies of the same printer, none of
which will print. We cannot delete either the stuck jobs or the printers
themselves. Net stop/start spooler command has no effect.

I'm assuming this is a problem with either the local printer or computer,
since I can RD in to the server from my home laptop and print to my home
computer with no problems.

How can I troubleshoot why the printer does not print, and how can I remove
the "dead" copies of the printers?
Click to expand...
Click to expand...
 
hi,
somethings like this it was happend to me about 2 month ago, it was because
on the client it's was installed the pcl 6 driver and on the server was pcl
5e. The server it map the printer but it happening like you said. After i
install on the client pcl 5e the problem was solved. so check to see if the
server and client have the same driver and if the driver is TS compatible.
--
Dragos CAMARA
MCSA Windows 2003 server


Huskies4all said:
Thanks for the reply. I have done this. While it provides a temporary
solution and removes the "shadow" printers, it still does not fix the
original problem, that the print job just sits in the queue on the server,
and never prints to the client computer's printer. If I could get the
printer to actually print, that would be GREAT! I'm banging my head on the
wall here! :-)

CJ

Dragos CAMARA said:
hi,
for deleting printers do the follow on terminal server :
stop print spooler; delete all files from %windir%system32/spool/printers ;
start print spooler and now you can delete that "shadow" printers.

--
Dragos CAMARA
MCSA Windows 2003 server


Huskies4all said:
We use RD to connect 2 veterinary clinics for database sharing purposes. We
got a new computer and printer, and had the connection running successfully,
and printing successfully. However, something changed (I don't know what
changed, I do not work in the offices; only from home)

The printer attached to the local computer is behaving oddly over the
connection. We started out with the printer showing up in the "printers and
faxes" window on the server. When we print, the job shows as printing,
but never actually prints. We cannot delete this job. We tried logging
off and logging back in. The printer and stuck job were still there, but we
then had an additional printer labeled "Dell AI0 946 [From Companion] (copy
1)".

Repeat several times, and now we have 4 copies of the same printer, none of
which will print. We cannot delete either the stuck jobs or the printers
themselves. Net stop/start spooler command has no effect.

I'm assuming this is a problem with either the local printer or computer,
since I can RD in to the server from my home laptop and print to my home
computer with no problems.

How can I troubleshoot why the printer does not print, and how can I remove
the "dead" copies of the printers?
Click to expand...
Click to expand...
Click to expand...
 
Back
Top