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?