We have problems with print jobs jamming in the queue. Win2K/MF FR3, with UPD, but was also happening without the UPD. We find a job partially downloaded in Print Manager (e.g. 1.8K of 123K bytes), with all the other jobs that user has tried to print stuck behind it. If you retry the print job it fails at the same point (always between 1 and 5 K in to the file) The spooler is still running and other users are not impacted. My initial thought was that it fails when a user disconnects, but this has not proven to be the case. If I stop the spooler, delete the jobs and restart the spooler they continue successfully. Any Suggestions? David Finch ******************************************************** This Week's Sponsor - RTO Software / TScale What's keeping you from getting more from your terminal servers? Did you know, in most cases, CPU Utilization IS NOT the single biggest constraint to scaling up?! Get this free white paper to understand the real constraints & how to overcome them. SAVE MONEY by scaling-up rather than buying more servers. http://www.rtosoft.com/Enter.asp?ID=147 ********************************************************** Useful Thin Client Computing Links are available at: http://thin.net/links.cfm *********************************************************** For Archives, to Unsubscribe, Subscribe or set Digest or Vacation mode use the below link: http://thin.net/citrixlist.cfm