I am likely mis-reading your problem, but here goes.
You install the "Simple TCP/IP Services" from Windows Components, Network Services to the sharing machine for the printer.
You "Add" printer and designate the device as local, with the IP you have assigned the printer.
You then create a new printer definition as Network, the printer being the locally shared device name done previously, and give it a new sharename.
You then share the last name for the remote clients.
For local workstation use of the printer you can either use the local sharename, or the given remote name, or if you have DOS applications use NET USE LPTx: \\printer_server\sharename to handle the chore.
It would be a mistake to try to use the local physical port rather than using Windows as a host for a virtual device; e.g. lpt1:
We add the printers via IP as you have suggested. However, in our current environement, we have Novell print queues. To capture to a port (LPTx) etc. we then use the Capture printer port to accomplish this.
We have to apps that MUST have LPT printing, an old DOS app and a very robust 32 bit healthcare application that nobody considered to change.
So, we are now attaching to the IP printer. What we need to do is capture LPTx to the same printer installed to the machine.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.