DOS Printing Redirection Not Working

I'm having an odd problem with DOS network printing. I have a DOS program
on a Windows XP workstation that I need to have its printing redirected to a
printer shared on a Windows 2003 server. I use the appropriate NET USE
command: "NET USE LPT1: \\bccg_server\laser3 /persistent:yes"... gives me no
errors. But actual printing goes nowhere. Sometimes, the print job DOES
show up in the workstation's print queue for that printer, but reports an
error and will not forward to the printer. The workstation can print to
that printer in any Windows program, and the network user has the
appropriate rights to that printer share. I tried the same NET USE command
on other workstations and other users (including Administrator), but had the
same issue.

Any thoughts?

"Ben Scaithe" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> I'm having an odd problem with DOS network printing. I have a DOS program
> on a Windows XP workstation that I need to have its printing redirected to
a
> printer shared on a Windows 2003 server. I use the appropriate NET USE
> command: "NET USE LPT1: \\bccg_server\laser3 /persistent:yes"... gives me
no
> errors. But actual printing goes nowhere. Sometimes, the print job DOES
> show up in the workstation's print queue for that printer, but reports an
> error and will not forward to the printer.

The DOS based program must prepare the job for the SAME
printer and driver as the LPT1 is mapped to.

Many DOS programs were restricted to the printers they could
use, e.g., the original LaserJet PCL only.

If you printer (that you mapped) were for instance the Postscript
driver of that device then you would get errors.

You have to do the Net Use command to a Printer (logical
print queue, not the hardware) that uses a compatible driver.

> The workstation can print to
> that printer in any Windows program, and the network user has the
> appropriate rights to that printer share.

Windows programs do not format print jobs, except in the sense
that they call the print driver functions without having such hard
coded.

> I tried the same NET USE command
> on other workstations and other users (including Administrator), but had
the
> same issue.

Give us the Driver of the Printer and compare that to your
DOS program documention.