Solved

Problem with Remote Desktop printing

Posted on 2010-11-26
6
1,802 Views
Last Modified: 2012-05-10
I am unable to print to a new Brother MFC-8680DN printer through Terminal Services.  Printing to other local printers through TS works as does printing to the Brother locally.

The server (single server, runs DC and DNS) runs Windows Server 2008.  The workstation has Vista Home Premium with SP2.  Both are 32-bit.  I just installed the latest Remote Desktop Client from Microsoft.

When I try to do a test print locally, it works fine.  If I try the same through TS, I get the error:0x000003e3

I have done/tried the following:
1) enabled rights to users on the \Windows\System32\spool folder
2) tried disabling bi-directional printing, but that was greyed out on both ends
3) have set up the Brother both through the network (by IP address) and by USB, same results
4) Removed the Brother printer installation, installed the latest Brother driver on the server (XP/Vista/2008 use the same file from Brother) as if the printer were on LPT1:, just to get the drivers on the server, then re-installed the Brother locally
5) tried TS on another Vista workstation with same errors
6) shared the printer on the Vista workstation, tried to connect to it directly both through TS and at the server; neither connection was allowed
0
Comment
Question by:CompProbSolv
  • 4
6 Comments
 
LVL 38

Expert Comment

by:Adam Brown
ID: 34218954
http://social.technet.microsoft.com/Forums/en-US/winserverTS/thread/3230549f-2e1f-43d0-b323-23104fd06604 suggests that there is a known issue on printer redirection on Domain Controllers using Remote Desktop Services. The recommendation is to modify the ACLs on the Spool folder, though I haven't tried this. http://www.ditii.com/2007/08/24/terminal-server-and-printer-redirection/ has a number of additional resources on managing TS Printer Redirection. Might be worth a look.
0
 
LVL 20

Author Comment

by:CompProbSolv
ID: 34219042
The first reference has to do with setting rights on the spool folder, which was mentioned in my item 1.  The second reference had some interesting information that didn't apply here.  Most had to do with situations where redirection doesn't work at all, vs. working with some printers and not others.  There is a reference in there to Microsoft's Terminal Server Printer Redirection Wizard, but that is not supported in 2008 with Easy Print.
0
 
LVL 10

Expert Comment

by:Wolfhere
ID: 34219250
As referenced from Microsoft, I think you have nailed the issue with the word "Vista Home Premium". As stated in this Microsoft document - http://windows.microsoft.com/en-US/windows-vista/Connect-to-another-computer-using-Remote-Desktop-Connection

Notes

    * You cannot use Remote Desktop Connection to connect to computers running Windows Vista Starter, Windows Vista Home Basic, Windows Vista Home Basic N, or Windows Vista Home Premium. You can, however, connect from those editions of Windows Vista to computers running other versions of Windows.
    * You cannot use Remote Desktop Connection to connect to computers running Windows XP Home Edition.
0
Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

 
LVL 20

Author Comment

by:CompProbSolv
ID: 34220437
I may not have been clear here.  This should sort it out:

The printer is attached to the Vista computer.

The Vista computer attaches to the Server 2008 computer using Terminal Services/Remote Desktop.

The application runs on the server.

I'm trying to print to the Vista computer while using Remote Desktop on the Vista computer to connect to the Server 2008 computer through an application on the Server 2008 computer.

There is no problem printing to a different printer on the Vista computer while in the same Remote Desktop session using the same program on the server.

0
 
LVL 20

Accepted Solution

by:
CompProbSolv earned 0 total points
ID: 34323785
Problem was resolved by installing generic HP Printer Family drivers on the server and on the workstations.
0
 
LVL 20

Author Closing Comment

by:CompProbSolv
ID: 34358873
The responses indicated that the original posting was not read thoroughly.  The solutions provided had already been addressed.  The solutions suggested did nothing to solve the problem.
0

Featured Post

Zoho SalesIQ

Hassle-free live chat software re-imagined for business growth. 2 users, always free.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
AD Replications issues 12 87
Active Directory delegation of control to a user 3 81
Windows 7 won't join domain 4 42
Remove LogMeIn from machines at user login 5 60
To effectively work with Diskpart on a Server Core, it is necessary to write some small batch script's, because you can't execute diskpart in a remote powershell session. To get startet, place the Diskpart batch script's into a share on your loca…
The recent Microsoft changes on update philosophy for Windows pre-10 and their impact on existing WSUS implementations.
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
This tutorial will show how to configure a new Backup Exec 2012 server and move an existing database to that server with the use of the BEUtility. Install Backup Exec 2012 on the new server and apply all of the latest hotfixes and service packs. The…

895 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

12 Experts available now in Live!

Get 1:1 Help Now