LPD on JetDirect J3113A

G

Guest

Guest
Archived from groups: comp.periphs.printers (More info?)

Can the HP JetDirect J3113A interface be configured as a Line Printer
Daemon using port 515? If so, how?
 
Archived from groups: comp.periphs.printers (More info?)

Yes. We flashed the latest firmware and we used the JetAdmin Web
interface but saw that the LPD PRINTING box was greyed out and can't
seem to get it to appear so it can be checked on. We figured LPD was
not an option on this JetDirect card. Using Telnet, the command LPD:1
returns "Illegal Entry."
 
Archived from groups: comp.periphs.printers (More info?)

bforward@texarkanacollege.edu <bforward@texarkanacollege.edu> wrote:
> Can the HP JetDirect J3113A interface be configured as a Line Printer
> Daemon using port 515?

Yes. (Future reference: that's a JetDirect 600N.)

> If so, how?

LPD should be enabled by default. If it's been turned off, you can use
a web browser to get to the JetDirect's configuration pages. Under
Networking, Configuration, Other Settings, make sure LPD Printing is
checked, then click Apply.

Or just telnet to it and type

lpd:1
exit

and save settings.

--
Warren Block * Rapid City, South Dakota * USA
 
Archived from groups: comp.periphs.printers (More info?)

In article <1114444710.729112.65640@o13g2000cwo.googlegroups.com>,
bforward@texarkanacollege.edu wrote:

> Yes. We flashed the latest firmware and we used the JetAdmin Web
> interface but saw that the LPD PRINTING box was greyed out and can't
> seem to get it to appear so it can be checked on. We figured LPD was
> not an option on this JetDirect card. Using Telnet, the command LPD:1
> returns "Illegal Entry."

BF-

Sometimes an entry is grayed-out when you don't have permission to change
it. Either you need to log-in with an admistrative password, or/and there
is a different screen where the change can be made.

If the printer/JetDirect has an IP address, I don't see why you can't
print to that address using LPD printing via the default port.

Fred
 
Archived from groups: comp.periphs.printers (More info?)

Well...now we think the printer DOES operate as a LPD whether or not
the box is greyed out in the network configuration. We found the source
application was sending fragmented data packets. Apparently, the
printer didn't know how to handle this and was ignoring them. The
sending application kept on sending fragmented packets until the
printer simply timed out. We are now addressing the problem with the
sending application.

Thanks for all your suggestions.