Thanks Brian,

For the moment I have cancelled the printer distribution by Windows Group Policy Object. Guys in different Windows forums do not recommend this approach because it doesn't work sufficiently. Now I have installed the network printer manually again. Will see what happen.

Using the printers as local TCP/IP printers would be my very last attempt, if nothing else works for all.

Hi guys,

Recently we experience frequent Pmail (4.72) crashes when trying to change the printer.

Pmail is installed in a multi-user environment where each user is starting his own instance from one pmail installation at a server. This server is also the print server (holding all printer queues) of our domain and hosts 4 printers. All Windows clients have installed the network printer from that server. One printer is the standard printer which is also set as the standard printer in Pmail.

Frequently, after changing the printer (special printer -> drop-down box -> choosing another printer) and pressing the OK button, Pmail freezes and must be killed manually. This happens irrespective of printing by the ordinary printer function or using the HTML editor (IE Renderer 2.4.9.13) printer function (Strg+Shift+P).

Has anybody a clue in this regard?.

Cheers

Joerg

Joerg,

I have had to install a number of network printers as local printers on workstations due to random problems when connected as a network printer.  Consider testing an installation of the problem printer as a local printer using a standard TCP/IP port to identify whether the problem is related to the printer driver or the printer as a network printer.

Hi Brian,

We have to carry out many many print jobs a day. That's why we prefer central printer queues for each printer. In case every computer maintain its own printer queue, the printer could get problems when different jobs reach it simultaneously. Additionally I don't feel like install all printers manually on each computer. Presently the Domain Controller distributes his shared printers (network printers) by a Group Policy Object to all user machines.

I completely understand your thinking.  Mine was the same until I

encountered printers that just didn't behave correctly as network

printers.  Those that I have set up using the TCP/IP port seem to handle

lined up print jobs just fine although our printing load is not heavy. 

You are correct that it's takes some effort to install them on every PC

but I don't know if it would solve the PMail crashing problem.  A test

of one might identify whether the problem is network printer related or

PMail related. 

I'm sure you've already checked for a different printer

driver but also look into power management.  I don't know whether PMail

tries to poll the destination printer when switching printers but if

it's sleeping it might not respond to a poll.