Start Free Trial

asked on

How to print to my local priner via a RDP session?

Hi I have a local printer that I have attached to my network on the same subnet as my workstation. I am using that workstation to connect to another machine in another office using RDP. The remote machine is running Windows SBS 2003 and have a copy of office 2007 standard installed to it. I would love to be able to use word on the server and print to my local printer as word connecst to our reporting tool on our companies Database which is located on the server!

Any ideas?

I have ensured that the local printer option is checked on the RDP session byt still cant seem to you my printer?

Thanks Gurus

Simon

ASKER CERTIFIED SOLUTION

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

ASKER

Hi Rob

Have installed to the server and followed all of the above and still no joy! I have tried through RWW and all I get when connecting to the server via RWW are errors which I have checked on Technet they point to a port not open on my firewall TCP 4125 but it is and its not being used by MAD.exe.

Any other idea's?

Cheers

Simon

ASKER

Hi

Its not a DOT4 or USB printer and just found a sbs update for rdp v6 for 2003

Simon

ASKER

oh and not using a VPN just a direct rdp!

Thanks

What make and model printer is it?

ASKER

HP officejet J4680 if that helps

Hey Cybersi,
Login in to the RDP session with an account that have local administrative rights on the target RDP server, should install your printer drivers automatically, unless they are kernel mode drivers.

Cheers,
Danny

ASKER

Hi Danny

The machine the user is connecting to is a SBS server! I dont really want to give a user local admin rights to server! Any other ideas?

Thanks for your input

Simon

So this is a USB connected printer? Not connected by a network cable?
Very possible it will not work. RDP prior to server 2008 has issues with USB connected devices, and multi-function devices, though many will work. Have you tried the "fixit button" in the link provided earlier? This is often necessary for newer non-commercial printers
http://support.microsoft.com/default.aspx?scid=kb;en-us;q302361

ASKER

Hi rob

Sorry for taking so long to come back to you had problems at another site!

Re the printer its configured using Ethernet and not USB as its a shared networked printer!!

Simon

Hi again Simon,
Simply just connect those network printers that is used (one of each model) to your network admin account and then login to the RDP session.

RDP will automatically install drivers needed for each model and as soon as that is done, all your users connecting with that type of printer can connect it and use it.
It is simply the easiest solution. :)

Cheers,
Danny

ASKER

Sorry if im sounding thick but this is for a user not a administrator?

RDP to the SBS server as an Admin. Install the printer drivers. Once SBS 2003 has the baseline drivers for your officejet installed, other users which connect to it should be golden. 2008 mitigates this differently, but that is your best bet with 2003.
Justin

ASKER

Hi Justin/guys

Will give it a go on Monday when I'm back in the office!!

have a great weekend

Simon

Hi All, another thing to consider when installing the driver on the server, you will have to make sure the same driver version is being used. I have a lot of clients who connect their printers in session and if the versions mismatch then the printer will not show up either. A check of the event logs should indicate the driver is unknown if you get it wrong.

ASKER

Hi All

This is driving me absolutley bonkers and thinking of putting in a call to Microsoft! I have the same drivers installed on the server properties as the workstation and I have tried making the user a domain admin and still no joy.

Please help me OB1 Kenobi your my only help! :)

Cheers

Simon

have you added the user as a member of the print admins group for testing? or logged on as domain admin from that PC? As stated previously, if the driver matches(eg you download the same file from the website) on both client and server, extract the driver and install, then it should show up on the server when the client connects.

If you go to printers and check in print server properties that the logging level is set to full, you should see in the event log of the server an error when the client connects. this will point you to whether it is a permissions issue or it will state that the printer is unknown, which means wrong driver.

Can you let us know what the event log is stating when the client pc is connecting?

To Confirm:

you downloaded the basic print and scan driver from HP ( http://h10025.www1.hp.com/ewfrf/wc/softwareCategory?os=228&lc=en&cc=us&dlc=en&sw_lang=&product=3692888) extracted it to a folder
you installed on the SBS using; by open printers and faxes, on the menu bar go to file, server properties, add, and point to the diver .inf file.
You have confirmed the driver version and driver name are EXACTLY the same on both devices. Even and extra space between words in the driver name will cause it to fail

Is this an actual Ethernet connection to the device? The web site only shows a USB connection and on some a wireless connection

ASKER

Hi Rob

Thanks for the above! I have spoken to one of my suppliers re this problem and one of his customers has the same problem! He has suggested that I used the Xerox generic printer driver as that is what fixed his problems and aparently its loads the driver 10x faster then the HP drivers so will try that first before your fix.

Im going to go to site soon and do some more testing as its a 4 hour round trip. I have to install a new swtich and firewall/router so will have ago when I'm up there. If the worst comes to the worst Ill put a terminal server in with a DC and a GC.

I have uploaded the setupfile with the xerox drivers just in case it can help anyone else.

Ill let you all know how it works out.

Simon aka stress head lol
Setup.exe

SOLUTION

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

ASKER

Hi Rob

I cant get RWW to work properley for some reason. I can connect but cant connect to a machine via rrw!

Im just waiting for a new laser printer so will go up and make some checks!!!!

Thanks
Si

ASKER

Hi Guys

Just to give you an update. I have replaced the MFP with a CP3525 hopefully this will solve the problem.

ASKER

Hi All

I still cant get the above to work. I have tried all of the above solutions and still I cant get the printer to redirect to the local PC over RDP and even the clipboard will not work.

I have tried a large number of different drivers from PS to PCL and have tried a number of different Universal drivers including the HP Driver and Xerox drivers.

I now have the company LAN-LAN VPN working now so as a get around shall I install the printer to the server creating a TCP port and opening port 9100 on the firewall and forwading to the IP address of the printer?

Simon

ASKER

Hi All

I think I might have found the problem. In terminal services Configuration, connection, RDP-TCP properties, Client Settings, you can select your security preferences regarding RDP. One of the options is clipbook, printers, drive mapping, LPT, COM and audio. I have just changed the appropriate setting and about to reinstall the driver to the server and client and test. Will let you all know my results.

Regards

Simon

ASKER

IT WORKS!!!!!!!!!!!!!!!! If you could only see me know jumping around the office hands in the air kissing everyone!!!!

YIPEEEEEEEEEEEEEE!!!!!

Thanks everyone for your help and effort on this one! It was the server config that was blocking/stopping the printer redirection!!!!

ASKER

It was a group effort!!! :)

Thanks cybersi.
Glad to hear you have it working.

Sorry I have been away. I was reading your posts in order and as soon as you said the clip board wouldn't work I was going to suggest the security settings. These are set to allow by default with 2003 but must have been changed. For future reference they can be disabled in 3 places; terminal services configuration (as you discovered), local group policy, and domain group policy.

Cheers!
--Rob

ASKER

Rob

All I can say is thank you!

Si