Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 4073
  • Last Modified:

XP RDP Easy Print problems


I'm having a problem with an XP Pro machine connecting to a remote terminal server.  The machine suddenly can no longer print.  The event logs on the terminal server are showing error event id 1111 saying the driver for printer <printer name> is unknown but the real problem is because Easy Print is working.

Please keep in mind this is not just a simple "load the drivers and you're fixed" scenario.  The remote server does not belong to the company and we have no control over what drivers are loaded.  The remote terminal is running Windows Server 2008 R2 x64 and is not a domain controller.  It's only function is terminal services.

The reasons why I know it's the local XP machine:
It used to work perfectly.  Only recently have the printers become unavailable for this one XP machine.
The printers in question are network printers.  The user is connected to a network print server so she is getting the same drivers that all of the other users are getting.
All other users in the office mapped to the same printers on the same print server can all connect to this particular remote terminal server and get mapped printers with no problem via Easy Print.
The event's with ID 1111 showing up on the remote terminal server only show up when this particular XP machine connects.  The machine right next to it with the same printers can login and there are no errors in the event log and the printers map normally.


Here's what I've tried:

Multiple user accounts, admin accounts, new accounts, etc.
I've also tried completely removing the drivers, cleaning up any remaining files and registry entries and finally reloading them from the print server with no luck.
I've tried setting the RDPDR filter queue to FFFFFFFF in the registry (MSKB 302361)
The printers we're trying to map are all using PCL drivers (not PS drivers)
.NET Framework 3.5 SP1 is installed on the XP client (along with .NET Frameworks 1.1, 2.0SP2, 3.0SP2, 4.0)
I've tried adding the fEnableRDR and fEnablePrintRDR entries on the client with both set to 1 but it didn't help.
The RDP client is the latest available for XP SP3 (that I'm aware of) from KB969084 which says it's 7.0.  If I go to "About" on the RDP client it shows Control Version 6.1.7600 but then beneath it it says Remote Desktop Protocol 7.0 supported.
I've tried removing and re-installing the terminal services redirector via device manager but that didn't resolve the issue.  The driver version is 5.1.2600.5512.

I'm out of ideas.  The XP machine having the problem is setup like every other machine with the same software installed, same patches and updates, same service pack, same configuration, etc.  The problem appears to be that Easy Print isn't working so the machine is falling back to the old driver mapping technique which of course is failing since the terminal server doesn't have the drivers loaded (which I can't do on a server I don't control).  Obviously fixing Easy Print on the problematic XP machine will resolve the problem.

Any ideas out there?
0
tekrage
Asked:
tekrage
  • 3
  • 2
1 Solution
 
WakeupCommented:
Just some possibly helpful reading:
http://blogs.msdn.com/b/rds/archive/2009/09/28/using-remote-desktop-easy-print-in-windows-7-and-windows-server-2008-r2.aspx

Not sure if it'll help...it's 3am here...and I need to go to bed in like -30 minutes ago!  I'll come check on this sometime tomorrow.
0
 
tekrageAuthor Commented:

Hi thanks for the link.  I read up on it but it's pretty much the same stuff I've been going through.  I ended up opening up a case with MS PSS which is currently still open and pending.  So far they don't know what's wrong either.  Guess I'll find out soon enough!

I'm open to any and all ideas to put this pain in the rear behind me for good.

-Tim
0
 
tekrageAuthor Commented:
For those interested - I was able to talk to PSS today and get the problem resolved.  It turned out to be a combination of a corrupted .NET Framework and adding two hotfixes.  The support rep had me remove .NET Framework 4.0, 3.5, and 3.0 (but we left 1.1 and 2.0).  After the reboot I reinstalled .NET Framework 3.5 SP1 which apparently includes .NET 3.0 SP2 so I didn't need to re-install .NET 3.0 first.

.NET 3.5 SP1 - http://download.microsoft.com/download/2/0/e/20e90413-712f-438c-988e-fdaa79a8ac3d/dotnetfx35.exe

Afterwards I installed hotfixes for MSKB 954743 & 954744.  Oddly enough you have to install 954744 first, then 954743.

http://support.microsoft.com/kb/954744

http://support.microsoft.com/kb/954743

Then I re-installed RDP 7.0 (although it's really still 6.1 on XP)

http://support.microsoft.com/kb/969084

Problem was fixed!  There seemed to be a problem with TsWpFwrp.exe which looks to have been the culprit behind the whole thing.  The current file version is 3.0.6920.1201 which has the machine working perfectly.  I have all of my easy print printers again.  Life is good.

-Tim
0
 
tekrageAuthor Commented:
Worked with MS PSS to get a solution.
0
 
WakeupCommented:
Great...glad you got it fixed...and sorry I did not make it back on to help ya....been a rough week!
0

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now