Your comment on printing is unfortunately correct. The typical kludge for client-side printing is to actually share the local printer, then manually map back to the client printer from the server session - the process is documented in a paper by Claudio Rodrigues on his site at http://24.42.144.161/tsnet/Links.htm
----- Original Message ----- From: "Michael Milette" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, 2002-04-12 17:58 Subject: Re: print redirection > Upgrade the remote PC to WindowsXP - A single user terminal server is built > right in and can be accessed from any 32 bit version of Windows including > your Windows 2000 Pro machine. It's cheaper than going out and buying > Terminal Server. > > Just one note. I recently saw something that said that printing is still > done though Microsoft Networking and not though the Terminal Services. I am > not positive on this point as I wasn't really paying attention to that part > of the article so you might want to look into that before you put out the cash. > > Michael Milette > > ----- Original Message ----- > > win2k pro is the platform > --------------------------------------------------------------------- > To unsubscribe, mail [EMAIL PROTECTED] with the line: > 'unsubscribe vnc-list' in the message BODY > See also: http://www.uk.research.att.com/vnc/intouch.html > --------------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, mail [EMAIL PROTECTED] with the line: 'unsubscribe vnc-list' in the message BODY See also: http://www.uk.research.att.com/vnc/intouch.html ---------------------------------------------------------------------
