Archived from groups: microsoft.public.windowsnt.terminalserver.client (More info?)
Check the EventLog on the Terminal Server to see why.
Probably a missing or mismatched driver name.
If that is the problem, map the local printer driver name to a
native driver on the server, by creating a custom ntprintsubs.inf
file.
You are about to answer a thread that has been inactive for more than 6 months. If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.