Reply to thread

Message: [QUOTE="Guest, post: 4812728"] The idea of using terminal server or any kind of "Server Based Computing" is to make the client machines replaceable so you get the same experience no matter where you connect from. The only time I would see it beneficial to share someone's local printer is if others need to print to your printer What if your computer is not on the same network as the Terminal Server If you get a new computer then a new share needs to be setup Not everyone know how to setup file & print sharing or has the sufficient rights to do so What if you're logging onto the Terminal Server from home Setting up print queues for always available printers and auto-creation of local printers just serve different purposes. If only you need to print to the printer, then there's no need to share your printer Patrick Rous Microsoft MVP - Terminal Serve [URL]http://www.workthin.co[/URL] ----- John wrote: ---- Environment: Windows 2000 SP4 server, Windows 98SE clients. Variou clients have parallel printers on their LPT1: ports. No network (TCP/I capable) printers. Wide area network over a variety of network link (different speeds) When I log in to the server from a client. Terminal Services creates me "Session" printer pointing to any locally attached printer I may have; thu allowing me to print from my session on the server back to my local printer My question is why would I want to do this? As opposed to sharing m printer on my 98SE client, and setting up an old fashioned printer queue o the server to point to the printer attached to the client PC Can't I just achieve my printing with old fashioned print sharing as oppose to the "session printer" that terminal services creates for me? Is there performance issue - there seems to be from my initial playing around.. please advice regards John Kruiniger [/QUOTE]

Verification