How do I setup Local printing with Windows 2003 Terminal Server
Posted on 2005-04-11
I am familair with windows 2000/2003 server Networking but not as familair with the Terminal server piece.
I have a 2 Doctor's office Network. The primary office has the 2003 Server running Terminal server. The local 3 users do not need to take advantage of Terminal Services. The remote branch also has 3 users and connect via VPN (using 2 Netgear FVS318 VPN routers, one at each end thru a broadband cable connection). The remote users have mapped drives using \\192.168.28.2\share (I have not applied any LMhost files) to connect to their shares. The issue is with one user who needs to connect to a Medical program on the server and be able to print to her locally attached USB printer. The user can map to the location and run the program over the wire, but it takes several minutes to execute the program and several additonal minutes per any key funtion. The company that designed the program says you have to use TS to connect to the program. So what I did is created a Remote Desktop connection to the Server's Medical program to allow her to funtion normally but I can not print. I also created a mapped connection to the program to allow her to print - meaning, this person is currently running two connections to the program, one thru a mapped drive and the other thru RDC (TS connection) I made sure I had the printer box checked in her RDC configuration.
I have been all over this site to find clues. I found several little pieces that makes sense but nothing complete. All user's PC's and the server are in a workgroup (decided not to use AD), I shared out this one users printer but can not see it from the workgroup. Also, I read that I may need to use either a parallel cable or place this printer on Jetdirect device.
What is/are the best recomendations to allow this user to print locally? Any input is very much appreciated