Dear MS Forums,In my office, we use software housed on a server running Windows 2003 and access them through Windows XP machines via RDC. We have 2 printers on ourlocal network that we use for printing tasks. One of them is a USB printer, the other is anetwork printer connected to our LOCAL LAN.The USB printer attached to "workstation 2" is fine. It works everytime. Its carried over through RDP flawlessly. All of the workstations can use it whether or not they are in RDC or on the client machine.The other printer (the network printer, HP P1505N) which is also installed on "workstation 2" is not being carried over through RDP anymore. It was at one point but it has been finicky in the past 3 years. I can find the printer and print to it from any machine on the local network, but not when connected through RDC.Manually adding the printer using the correct port and drivers results in the printer appearing on the list, but I am still unable to print anything to it. After adding it manually, I cannot delete or modify it. On a few occassions I was able to print a test page to it, but it took about 5 minutes to print. A few other times, when looking at the printer on the host machine (workstation 2), there was a rapidly changing amount of spooled documents that were being added and deleted. In addition to that, the machine serving our RDPs is adding copys of the printer to the list which behave the same way.I am figuring that this not an issue on the client computers, rather the server we are connecting to. Trying to restart the printer spooler in services.msc results in a warning that the service "fax" depends on the spooler. If you look at the service "fax", it stuck on "starting" and therefore, I cannot stop the printer spooler or "fax", they just time out.Unfortunately, I am not the network admin. I cannot gain access to the server. The current admin is not the admin that created the setup we are using. I have spoken to him about the issue, and I feel I am getting the cold shoulder from him. He is working on a newly implemented system, but it could be a year before we begin using it.Any ideas would be greatly appreciated, even if they require the network admin to make changes. I will pass the info along to him. -Ryan McGonigal1 person needs an answerI do too

RDC printing to local printers is a little problematic in Windows Server 2003.One thing that really seems to help is making sure you have the most recent RDC client on the workstations. See if this helps: http://support.microsoft.com/kb/969084 -B- http://www.officeforlawyers.com Author: The Lawyer's Guide to Microsoft Outlook