Anyone have terminal services printing registry keys to share? 1

[Yeastman]

Recently having a problem with remote clients printing to thier local printers. After some research, it seems that im missing some registry keys. This post

http://www.tek-tips.com/gviewthread.cfm/lev2/3/lev3/19/pid/48/qid/177648

lists what I need to do.

Anyone have a Win2k Server with Terminal Services installed where client printer redirection is working fine? If so, can you export these reg keys listed in that post so I can add them? (and anyone else with same problem)

Ive been trying to add them manually but im not sure if i'm adding the right data type for each line.

Thanks in advance

 

[rszabbage]

If printer redirection WAS working, and then stopped:

One uncompleted print job can screw up the server print spooler for all printer clients. Seems as how the server spooler runs a COMMON thread for all print jobs in que - not one thread per client.

on the Server -
:theTOP
STOP the SPOOLER SERVICE
Explore to \winnt\system32\spool\printers
Delete the oldest 'to be printed' file - assumed to be the culprit. (but not necessarily so)
reSTART the SPOOLER SERVICE
get a workstation to try to print anything via Terminal Services. (I usually leave a very short notepad hello-world.txt file and on the common desktop for testing printer functionality)
if it prints OK you're done
if not, goto theTOP

Note that workstations can have a similar problem.
Check their local \winnt\system32\spooler\printers folder for hung print jobs. Stop their SPOOLER service - kill any rogue print jobs, and restart the SPOOLER service.

If you havn't successfully managed to get printer redirection to work ever -
There is a bit of an art to adding UNLISTED print drivers to Win2K Server (i.e. for printers that have hit the market since 5/8/2001 when the NTPRINT.INF file was published) (You may have a different version than I do - but that's all I have seen, so far)- in particular when the NAME of the driver on the workstation (WinXP? version) differs in any way from the name of the driver on the server (Win2K version). That requires a minor registry entry, and creation of a small .inf file to handle the cross reference. Don't try to edit the NTPRINT.INF file as that is a digitally signed file, and any modification will blow the authentication. You'll have to reload it from the Server CD.

Let me know if you need more on adding unlisted printers.

 

[Yeastman]

Thanks rszabbage - lots of great info in there. The spooling thing never even occurred to me. Makes perfect sense now that you mention it though!

Good info on the ntprint.inf file too, I had no idea that it was a digitally signed file.

Incidentally I manually input all the registry keys in that post I referenced - and it didnt work, even after making some changes more specific to my system. It may have worked in the case of the person who posted it, but for me all it did was force me to revent to 'last known good configuration' to get the thing to boot again!

Uninstalling Terminal Services and Reinstalling it did the trick. Printer redirecting works now. I hope I dont have to reinstall the TSAC CAL's though, yuck... MS licensing is fun as a root canal. I still have yet to confirm high encryption too, but so far so good.