Errors Auto-Creating Client Printers

[BryonB]

I'm geting errors each time a client tries to connect to my Citrix server, and the client printers are not being added.

The following error appears in the event log:
Event ID: 1103; Source:TermServDevices - An internal communication error occurred. Redirected printing will no longer function. Data: 0000: 00000003 00000376

This is a test server. I just repartitioned it, and reinstalled the OS and Citrix from scratch again recently.

It is running Windows 2000 Server SP2, Citrix MetaFrame XP 1.0 FR2, SP2.

The same printer drivers are installed both on the server, and on the client (client is Win 2k Pro SP2 as well). The printer drivers are set up via the Novell iPrint Client (network printers that use IP printing). These same printer drivers were installed on this machine previously, and were being mapped by clients without any problems.

The only information I could find in Microsoft's TechNet database for this error indicated that the device redirector isn't installed properly, and that I should uninstall and reinstall Terminal Services. I tried this, and it hasn't made any difference.

Does anyone have any other suggestions?

 

[chester27]

Are your Printers setup with PCL or PostScript, as we had an issue with PCL through Citrix, changed to Postscript and all was well.

 

[TexExpat]

FWIW, check out Universal Printer from Emergent OnLine at

http://www.go-eol.com/products/thinssentials.htm

. It is installed on the MF server and a client component is installed on the client. It automatically converts a print job to a .PDF format, passes it down to the client, then the client prints it locally using the client printer driver. The server component is not expensive, and the client component is free.

I have been using it for about 8 or 9 months now and it has performed very well. I no longer have printer drivers defined on my MetaFrame server nor do I have to mess with autocreated printers.

 

[BryonB]

I'm not sure if the driver is PCL or Postscript, but it was working OK at one point on this server prior to reinstalling everything.

I don't think pushing the job back on the client via a PDF driver is an option. We want to be able to eventually deploy to various thin clients, so I don't think we'll want to run much of anything on the client side other than the Citrix client itself (keeping Java client as an option).