Try, just as an experiment, removing the printer AND DRIVER from the client, then re-adding it. Test the mapping again. This will let you know which side you need to troubleshoot. -----Original Message----- From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Turman, David C. Sent: Wednesday, April 12, 2006 8:46 PM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: Another Printer Problem Ha, (not that it's funny) I have the same problem. Started abou 2 weeks ago. Driving me crazy When did yours start? _____ From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Michael Boggan Sent: Wednesday, April 12, 2006 1:14 PM To: thin list Subject: [THIN] Another Printer Problem We are running W2k3 and XP FR3/SP4. We have some printers out there using the UPDs but most do not. Lately we have been having issues where the UPD is used even though the printer driver exists on the servers. We have checked that the driver names match. We have tried MAPPING the drivers to themselves. Nothing seems to work. If we log in via RDP the driver is loaded and the printer created without a problem, but if we go through Citrix, the UPD is used and not the native driver. We also, do not see any errors in the event log on the servers, about problems creating printers. Has anyone seen this before? Thanks, Michael Boggan XO Communications