Question : Printer redirect in Terminal Service!

I have a site that has a Win2K server with Terminal services on it with a public IP address so the remote site can terminal service into that server and use an application on it.  The remote site has the Win2K version of terminal Service, which I guess I should upgrade to the XP version.  My problem is that the remote site has a local printer attach and when they are using the application on the server via TS at the main site, they can not print back to the local printer.  It doesn't show up.  The terminal server is in remote administrator mode.  Any Ideas?  Thanks!

Answer : Printer redirect in Terminal Service!

The first thing you need to do is go to Start>Administrative Tools>Terminal Services Configuation.  Double click on RDP-TCP.  Click on the Client Settings tab.  Uncheck 'Use connection settings from user settings.'  Check 'Connect client printers at logon' and check 'Default to main client printer.'  Also uncheck LPT port mapping if it is checked.  Once you click okay if you are logged in, log out and re-logon so that the settings take affect.

Check to see if the printer is now created.  It should look something like this:  HP LaserJet\Session1.  With the settings we've just configured it should make that printer you default printer as well.  

I worked a lot with terminal services and I've seen from expierence that a lot of printers do not work properly.  Sometimes they connect and sometimes they don't.  HP printers work great almost 95% of the times.  Other printers you have to play with.  If the printer does not work let me know and I will show you how to map that printer to a HP Driver so that it does work.

***Post Question Start****

Is the remote site a Windows 2000 Professional machine?  You clearly explained that you have one site with Windows 2000 Server, but I wasn't to sure on what you meant for the other site.  The instructions I noted above are for a Server on one site and a remote machine on the other site with Windows XP Home/Pro or Windows 2000 Pro.  Basically a remote machine with the Terminal Services client or the new Remote Desktop Client.  Which is an upgarde to the old Terminal Service client.    The Remote Desktop Client now comes natively with XP Pro.

***Post Question End****

***Curious Question Start***

Why do you have a terminal server on a live public IP Address?  Do you have a firewall?  Configure the server behind a firewall so that you don't expose that server on the internet?  If you had a firewall on both ends you can create a VPN tunnel.  I can guide you on how to set that up if you like.  There are so many things you can do to get your issue resolved.  I will try and help you as much as I can.

***Curious Question End***

Thanks,
Rob