JetAdmin Discovery Failures

[Raymond Gauthier]

For MOST of my printers JetAdmin works incredibly well. However, two printers, both very local, do not show up in the general discovery, do not appear when I do an IP-specific JetAdmin search, and do not respond to Internet browser addresses. Yet the printers work fine, and respond to PINGs.

Any ideas?

[Peter Nikitka]

Hi,

please tell us the type of the printers and the type of network card/box!

Try to telnet to their IPs in that two ways and tell us the results (n666 is my example):
1)
telnet n666

should tell something like this:
Trying 10.10.233.20...
Connected to n666.
Escape character is '^]'.
HP JetDirect
...

2)
telnet n666 9100
Trying 10.10.233.20...
Connected to n666.
Escape character is '^]'.
...


mfG Peter

[Raymond Gauthier]

Peter,

Thanks for the prompt support.

The devices are an HP LJ5Si and an HP LJ8150. Both, as well as the other devices on our network, are connected to the network via external HP JetDirect boxes, model 300X.

When I try to telnet to any HP JetDirect print server, I get back "Could not open connection to the host on port ##" and the number is either 23 (if I don't specify a port) or 9100, if I do specify, per your example. Either I'm doing something wrong, or corporate IT mgmt blocks telnet.

Ray

[Peter Nikitka · Accepted solution]

Hi,

without an access to Port 910x (x may be different from 0 for network boxes supporting multiple devices) you won't get a working printer connection.
You should check that with your networking staff.
Perhaps the WIN$-standard repair (reboot) of the 300x will have effect.

Print an output of the network configuration of the 300x - there is a switch on them to create this information, if I rembember correctly.

mfG Peter

[Raymond Gauthier]

Pete,

You did it! You pointed me to the right answer. And I feel so asahmed. All I had to do was reboot the JetDirect print servers, and JetAdmin found the printers/JetDirect print servers.

Big Thanks.

Ray