Jay Shilstone
04-07-2004, 11:33 AM
I have checked the archives and this message has come up before, but
apparently never answered completely. Please help.
I have a customer who is trying to get our DOS application to print to
an HP LaserJet connected to a network via JetDirect from a Windows XP
computer. We can't do the typical:
NET USE LPT1: \\Servername\printername /persistent:yes
because there is no servername. When we look at the printer properties
for the port, we see "IP_192.168.1.45". If I type:
NET USE LPT1: \\IP_192.168.1.45
I get an error message.
If I type "NET VIEW \\192.168.1.45" I get an error message.
I suppose I need to say that the printer works fine with Windows apps.
Unfortunately, I can't easily get all the error message because my
client is in another state (while I currently reside in the state of
"confusion").
From what I can tell, I may be running into a problem with not being
able to communicate with the printer or it may relate to the problem
about getting XP to capture a printer port that exists as a physical
printer port on the computer.
Any ideas?
Thanks,
Jay Shilstone
apparently never answered completely. Please help.
I have a customer who is trying to get our DOS application to print to
an HP LaserJet connected to a network via JetDirect from a Windows XP
computer. We can't do the typical:
NET USE LPT1: \\Servername\printername /persistent:yes
because there is no servername. When we look at the printer properties
for the port, we see "IP_192.168.1.45". If I type:
NET USE LPT1: \\IP_192.168.1.45
I get an error message.
If I type "NET VIEW \\192.168.1.45" I get an error message.
I suppose I need to say that the printer works fine with Windows apps.
Unfortunately, I can't easily get all the error message because my
client is in another state (while I currently reside in the state of
"confusion").
From what I can tell, I may be running into a problem with not being
able to communicate with the printer or it may relate to the problem
about getting XP to capture a printer port that exists as a physical
printer port on the computer.
Any ideas?
Thanks,
Jay Shilstone