I have a very annoying problem with the configuration of several printers. Firstly the setup of the office.
We have a remote office setup currently as a workgroup of about 13 Desktops and 3 laptops. 3 of the desktops have small personal printers attached (Canon LBP 3000) - lets call it the Host machines. Each of these has another desktop accessing the printer via the usual printer sharing - lets call it the User. The Host machine has the account of the User setup and added into the local administrator group.
The setup works fine in as much that the User can access and print just fine so as far as I am aware I dont have an issue with permissions or accessibility. My problem is that I'm in a catch 22 position of printing from a program they use which runs from MS-DOS, don't groan too loudly I'm trying to find the time to rectify this.
The MS-DOS program prints to the LPT1 port which is mapped to the shared printer (both on the Host and User machine) using a batch file which runs at login. It simply uses the "net use" command to map it. For the MS-DOS program to print to this share I have to change the default data type of the print processor from RAW to TEXT. Simply done by going into the properties of the printer on the Host machine > advanced > print processor. The print processor is default selected to WInPrint and remains the same, but the default data type is changed from RAW to TEXT. This all works and allows the User to print from the MS-DOS program to the printer.
BUT... here it is the nuts and bolts of it... with this setup, after printing a normal word document, for example, to the printer it will continue to print out blank pages after blank pages until someone switches it off, lets it empty the buffer and then powers the printer on again. This happens on all 3 pairs of Host/User machines. If I change the data type back to RAW the white page business stops but I can no longer print from the DOS program. Hence my catch 22 experience.
We have the same setup in another office but those computers are in a Domain environment and not a Workgroup one. I still change the data type to TEXT and I have the sharing setup the same way, the only difference is one setup is in a Workgroup, the other a Domain setup. .. So maybe it is a security issue but I doubt that would explain the constant printing of blank pages. This is not only limited to the LBP 3000 printers, it also occurred trying to use this same setup with an LBP 2460.
If anyone can help out with this I would be forever in debt.