Hello All,
I hope someone can help me with this issue.
Setup
Windows Server 2003
Citrix Metaframe XP FR3
Using NFuse
We have one remote user that has been using Citrix for over two years. They have always had a locally connected HP Deskjet 932c as thier default. Last week their printer stopped auto creating. They say they have made no changes. The printer previously was creating correctly, using the native 932c driver. The user has several network printers that are auto-creating correctly but unfortunatly these printers are located in other parts of his office building. Here is what I have tried:
Re-installed driver: No change
Deleted driver installed a different driver: No change
Tried mapping the client driver to the correct server driver: No change
Tried manually creating the printer while shadowing the user: This is interesting because when I look at the clients printers through the Add Printer menu, I see two of that printer. One listed normally and one listed with UPDCL5c behind it. I know the second is a Universal Print Driver but dont know why I would even get that since the native driver is installed. When I select the normal printer listing, it appears to install the printer but nothing is added to the printer list. If I select the UPD one, it does create but it does not print correctly.
I also have checked the Event Log. Most of the time I don't get anything show up but a few times I received:
Client printer auto-creation failed. The driver could not be installed. Possible reasons for the failure: The driver is not in the list of drivers on the server. The driver cannot be located. Driver mapping is incorrect. Client name: (WWS_T-.jhollan-mwboe) Printer: (Client/WWS_T-.jhollan-mwboe#/hp deskjet 930c series) Client Printer driver: (hp deskjet 930c series) Server Printer driver: ()
Looks like the driver is not mapping but I have tried manually mapping it and went back to auto mapping and it doesn't work either way. It did before.
One more thing. I can see that there is a Client printer port being created on login even though the printer is not. It lists it as a UPD printer though. I believe that is why I was able to manually map the printer as a UPD printer.
Thanks for any ideas. I am pulling my hair out with this one. I am out of things to try.
Daniel Joaquin
I hope someone can help me with this issue.
Setup
Windows Server 2003
Citrix Metaframe XP FR3
Using NFuse
We have one remote user that has been using Citrix for over two years. They have always had a locally connected HP Deskjet 932c as thier default. Last week their printer stopped auto creating. They say they have made no changes. The printer previously was creating correctly, using the native 932c driver. The user has several network printers that are auto-creating correctly but unfortunatly these printers are located in other parts of his office building. Here is what I have tried:
Re-installed driver: No change
Deleted driver installed a different driver: No change
Tried mapping the client driver to the correct server driver: No change
Tried manually creating the printer while shadowing the user: This is interesting because when I look at the clients printers through the Add Printer menu, I see two of that printer. One listed normally and one listed with UPDCL5c behind it. I know the second is a Universal Print Driver but dont know why I would even get that since the native driver is installed. When I select the normal printer listing, it appears to install the printer but nothing is added to the printer list. If I select the UPD one, it does create but it does not print correctly.
I also have checked the Event Log. Most of the time I don't get anything show up but a few times I received:
Client printer auto-creation failed. The driver could not be installed. Possible reasons for the failure: The driver is not in the list of drivers on the server. The driver cannot be located. Driver mapping is incorrect. Client name: (WWS_T-.jhollan-mwboe) Printer: (Client/WWS_T-.jhollan-mwboe#/hp deskjet 930c series) Client Printer driver: (hp deskjet 930c series) Server Printer driver: ()
Looks like the driver is not mapping but I have tried manually mapping it and went back to auto mapping and it doesn't work either way. It did before.
One more thing. I can see that there is a Client printer port being created on login even though the printer is not. It lists it as a UPD printer though. I believe that is why I was able to manually map the printer as a UPD printer.
Thanks for any ideas. I am pulling my hair out with this one. I am out of things to try.
Daniel Joaquin