This is a common symptom of a printer driver which is not TS-
compatible.
Installing 3th party printer drivers on a TS is *not* recommended.
Most of these drivers are not completely TS compatible, and are
known to crash the printer spooler or the whole server.
I would uninstall the printer driver from the TS completely.
If your client printers are not autocreated, check the EventLog to
get detailed information. If the server doesn't recognize the
printer, map the printer to a native driver on the server, by
creating a custom ntprintsubs.inf file. Details are explained here:
239088 - Windows 2000 Terminal Services Server Logs Events 1111,
1105, and 1106
http://support.microsoft.com/?kbid=239088
You can check the recommended native driver substitution for your
local printers here:
Client Printer Autocreation Matrix
http://www.printingsupport.com/matrix.htm
If you are running 2003 SP1 on your Terminal Server, you can
configure a Terminal Server Fallback Printer Driver. For more info,
check:
http://www.thelazyadmin.com/index.php?/archives/18-Terminal-Server-
Fallback-Printer-Driver.html#extended
--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---
Post by AlexI'm having trouble printing via terminal services, when I
connect to my terminal server and try to print something to my
mapped session printer it only prints a blank page. Why is this?
I've tried installing the latest drivers at both ends but am
still having difficulty.
Please can someone advise me on this issue.
Regards,
Alex Saager