Printing via Terminal Services-hangs

[Steven Gordon]

My client has a Windows 2000 Server computer running
Terminal Services. One employee (off-site) uses Terminal
Services (over the Internet) to connect and needs to be
able to print locally (back to a directly connected
printer on the client). They connect perfectly, the
remote printer is shown properly on the server
but "sometimes" when printing the job goes to
status "spooling" then status "blank" and nothing
happens. We must manually delete the print job.

After playing with the drivers I can sometimes make the
printing work properly for awhile. Then, it seems that
when the remote user logs off and subsequently logs back
in, the jobs will not longer print. The printer shows up
properly, however, the job stalls out after
status "spooling" again. The printer is a HP Laserjet
1300 and I have tried using the 1300, 1200 and 1150 print
drivers - all return the same results.

Any help would be appreciated.

 

[Matthew Harris [MVP]]

I would try using an HP LaserJet 4, or the HP LaserJet II
driver and see what happens. You also might want to
reference http://www.printingsupport.com/ for more
information and possible solutions.

If I recall, HP 1300 printers were giving other people
problems in this newsgroup. You might want to chech the
archives...

-M

 

[Will Williams]

-----Original Message-----
I would try using an HP LaserJet 4, or the HP LaserJet II
driver and see what happens. You also might want to
reference http://www.printingsupport.com/ for more
information and possible solutions.

If I recall, HP 1300 printers were giving other people
problems in this newsgroup. You might want to chech the
archives...

-M

.
You might also try to disable printer spooling on the TS

Client. Set the Advanced Tab option to "Print directly
to the printer". Hope this helps.