Cannot Printer via RDP on SBS 2003
Hey everyone, hope someone has some insight for me here.
I have a fairly new installation of Windows Small Business Server 2003, SP2, fully up to date. When I connect through terminal services or Remote Web Workplace, I am unable to print back to my local printers.
I have verified that RDP is configured to connect my printers, hard drives, clipboard, etc when connected to the SBS 2003 server and that the printers are showing up in Control Panel > Printers and Faxes as <printer_name> on <remote_pc_name> <session_name>.
However, when I attempt to print from any program I receive errors and the page does not print. If I'm printing from Notepad I get "The handle is invalid". If printing from MS Office I get "Windows cannot print due to a problem with the current printer setup". I've verified all of the suggestions this error gives me. If I try to print a simple test page from the printer properties I'm presented with "Test page failed to print".
I have used the TSPDRW_Package.exe provided by Microsoft to ensure that the TS Printing is redirected properly.
Any suggestions? I am at a loss and need to get this resolved ASAP.
I have a fairly new installation of Windows Small Business Server 2003, SP2, fully up to date. When I connect through terminal services or Remote Web Workplace, I am unable to print back to my local printers.
I have verified that RDP is configured to connect my printers, hard drives, clipboard, etc when connected to the SBS 2003 server and that the printers are showing up in Control Panel > Printers and Faxes as <printer_name> on <remote_pc_name> <session_name>.
However, when I attempt to print from any program I receive errors and the page does not print. If I'm printing from Notepad I get "The handle is invalid". If printing from MS Office I get "Windows cannot print due to a problem with the current printer setup". I've verified all of the suggestions this error gives me. If I try to print a simple test page from the printer properties I'm presented with "Test page failed to print".
I have used the TSPDRW_Package.exe provided by Microsoft to ensure that the TS Printing is redirected properly.
Any suggestions? I am at a loss and need to get this resolved ASAP.
MSWarrior
Just to ensure that you have printer drivers installed on both your local and the SBS server, right?
If you have drivers on both and it still doesn't work then try this:
Install "Remote Desktop Client" Version 6, lots of multifunction printers don't work with the previous versions.
Install "Remote Desktop Client" Version 6, lots of multifunction printers don't work with the previous versions.
What model printer is it?
ASKER
Yes the drivers are correct. There are no multifunction printers but there are a slew of different ones. I've tried a simple HP LaserJet 4 up to a newer model laserjet with the exact same results. I have been using RDP Client v6 the entire time.
Thanks for the responses so far.
Thanks for the responses so far.
Look in the Event Viewer on the Server under System Log--look for Event ID 1111 named TermServDevices.
ASKER
I see the event and it says the driver for <PRINTER_NAME> is unknown. But the drivers are installed.
The drivers need to have the EXACT same name. If the client driver says, "HP Laserjet 4" and the server driver is called "HP Laserjet 4N"...then the printer will not get mapped.
ASKER
I know this. I have set up RDP printing dozens of times at other clients. This one is the first to give me trouble. Drivers are identical.
Have you tried re-install the driver on the Server?
ASKER
Yes. I have removed every driver and re-added them individually. No luck.
What model printer?
ASKER
It doesn't matter. None work. Nothing from a simple Laser jet 4 as stated earlier in this post to anything newer.
Well, not all printers are compatible with SBS 2003. Is this a multi function printer? I can't help you unless you give me the model number of the printer.
ASKER
Like I said above no printers work. Any make any model and I'm not using any MF or AIO devices. This particular client is using only HP and I've tested a 4, 4000 series, and a 1200. All of which work from other servers I RDP to.
OK, so AT ONE TIME or ANOTHER...you had a Laserjet 4 printer installed and printing correctly on a client machine. But, when you RDP to the SBS from that cleint; that same HP Laserjet 4 printer doesn't get mapped or get's mapped but you cannot print to it??
ASKER
That is correct. I've never been able to print to a perfectly fine functioning printer on a local workstation when that same workstation connects to the server through RDP. I get the errors listed in my original post.
does the pritner get mapped?
ASKER
Yes. Everything shows up as as should and for all intents and purposes it should work. It just doesn't. It gives me errors. If it wasn't mapping I wouldn't be able to test it only to get an error.
Thanks
Thanks
Have you checked the System Log for any errors RE: the Print Spooler.
ASKER
Please read all my previous posts.
Hah! I did. Your original post refers to errors while printing. Not actual Event ID's referring to Print Spooler errors. I asked if there are any Print Spooler errors in the System Log during the time you try to print. No where in your original post does it say, "I checked the System Log for Print Spooler errors"...
good luck
good luck
I don't know if this will help or not just cause I use thinprint but also with that I use their native free driver printing. If microsoft has this option basically it is simple from there. Add your printer on the server, use the native free driver printing to create another printer que, share this printer out and map your workstations to it. When they print it will it the share que then be redirected to original printer que and then printed.. it seems like there is alot of work but I use this for another area located 600 km's away from the actually server and print jobs are sent instantly. As well with this setup you do not need the driver on the local machine.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.