[x]
Posted via EE Mobile

Search, ask, and monitor your questions on the go with EE Mobile. Visit Experts Exchange from your mobile device and never be out of touch again.

09/30/2009 at 04:05PM PDT, ID: 24775503
[x]
Attachment Details
[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

9.6

Printing via RDP - Terminal Serviecs

Asked by robbcharlton in Remote Desktop/Terminal Services, Printers

Tags: Terminal Server, Printer, Driver

I'm having a problem on a small network with printing via terminal services. Here is the scenario:

Desk A connects to one of their client's systems via terminal services to collect billing data. They are able to connect to the client's terminal server using the built in RDP client in Windows XP. When they connect, they are able to access the client's database and print to a local printer at Desk A. No problems whatsoever.

Desk B can also connect to this same client's system, but cannot print. When they establish the RDP connection, their local printer is not detected/install in the terminal session.

Both desks are using Windows XP, are members of the same domain, have the same permissions, same network configuration (including firewall) and both are using USB ports for their printers. Desk A is using an HP All-in-one printer and Desk B is using a Dell 1720.

I'm told by the owner of the company that their IT people installed the driver for the Dell 1720 on the terminal server, but not the driver for the HP All-in-one. Why the HP at Desk A works, but the Dell at Desk B does not is very confusing.

The only indication I have of an error I've gotten is in the attached screenshot. This occurred when Desk B logged into the client's terminal server. The research I've done says that this is a drive mapping error, but still unsure if it could be related.

Thanks in advance for the help.
Attachments:
 
system error 85
system error 85
 
[+][-]10/05/09 12:46 PM, ID: 25498888

View this solution now by starting your 30-day free trial. Setting up your free trial is quick, easy, and secure. We will return you to this solution, unlocked, when you're done.

 

About this solution

Zones: Remote Desktop/Terminal Services, Printers
Tags: Terminal Server, Printer, Driver
Sign Up Now!
Solution Provided By: tsmvp
Participating Experts: 1
Solution Grade: A
 
 
[+][-]11/04/09 07:24 PM, ID: 25746516

Experts Exchange has a courteous staff of administrators who help members get the most out of the website by means of administrative comments like this one.

Start your 30-day free trial to view this Administrative Comment or ask the Experts your question.

 
 
Loading Advertisement...
20091111-EE-VQP-91 - Hierarchy / EE_QW_3_20080625