I have a strange situation concerning a server which I use for remote access to our office.
We have an old DOS program on a Windows 2003 server. We run it on this server because 1) it works and 2) the server can handled multiple people connecting from home.
First Attempt:
I setup the 2003 server with a generic printer and the print to file port. This didn't work and it never asked me for a file name or location. I checked My Documents and found nothing with the *.prn file.
Second Attempt:
I setup the 2003 server with a generic printer and set it to LPT1 with the option to print to file. I shared the printer and I used the command NET USE LPT2 \\servername\printershare /persistent:yes However this didn't work
Third Attempt:
I setup the 2003 server with a generic printer and set it to LPT1 with NO option to print to file. I shared the printer and I used the command NET USE LPT2 \\servername\printershare /persistent:yes When I tested it I got an error and the print job got stuck in the queue.
Fourth Attempt
I setup the 2003 server with CutePDF and used their printer plugin for the printer. This didn't work.
Fifth Attempt
I setup the 2003 server with a laser printer on the network. I shared it and I used the command NET USE LPT2 \\servername\printershare /persistent:yes When I printed I got the print job stuck in the queue again.
So it seems that the problem lies with the print job getting stuck in the queue. I can't figure out why because I use the NET USE command on all my workstations to make the printer work inside the office. However with this remote access server I can't get it to function correctly.
Is there a way to force the print jobs to go to a specific location and give it a specific file name? I would like a command line option because that is what seems to work with this old DOS program.
Thanks!
Patrick