HP-UX 11.0 can not ping printer, everything else works

[Matthew Couper]

Odd problem here...we have a new(ish) HP4100 setup on the network and is pingable by everything but our HP-UX system. Win2000, Win98, WinXP and even a Linux station are able to ping the printer.

I can send print jobs to it from the HP-UX and even telnet all by IP (we do not setup names on the printers themselves, they are all IP based) but the HP-UX just can not ping it.

This causes problems such as, the print requests stay in the spooler because it doesn't think the printer got the request and I can't use jetadmin to set it up.

Any ideas would be helpful, thanks!

[Steven E. Protter]

Is there a firewall between you and the printer blocking icmp requests(pings).

If you can't ping, you can't print as far as HP-UX is concerned.

tracerotue printer_ip

See if something is holding up the request.

The configuration for Linux iptables firewalls might be blocking ping's

No pingy, no printy as my 4 1/2 year old repeats now.

SEP

[Matthew Couper]

One hop straight to the printer IP...but no pingy

No iptables setup, straight from a HP-ux 11.0 on HP N4000 server...the printer is setup like every other printer on the network (even other HP4100s)

Unless we are missing something on the printer settings that I can not think of...

[Ron Kinner]

If the HPUX can telnet and you are sure it's getting to the correct printer (disconnect it to verify that the telnet attempt fails) then the networking and routing appear OK. Is there a router in the way which might block ICMP?

Does
traceroute -I ipofprinter
perform any differently?

Can you ping (from 11.0) to another device on the same network as the printer? On a different network?

Perhaps something is wrong with the ping file.

ls -l /usr/sbin/ping

-r-sr-xr-x 1 root bin 40960 Aug 24 1998 ping*

on my 11.0.

Some LINUX pings require a name resolution before they will work. I don't think HPUX does but it wouldn't hurt to try putting the printer in the /etc/hosts file with a dummy name just so it can find it.

Ron

second attempt. First came back with 404 and a refresh of the post showed nothing from me.

[Tony Willis_1]

I am not questioning anyone's understanding of TCP/IP. I have found the following in my years:

1. DNS from a Windows system not resolving.
2. Using address 0,64,128,255 for printers.
3. Subnet Mask.
4. Typo errors.
Printing and pinging are so simple that when there is a problem we spend far too much time correcting, when I believe it is easier to remove and start over.

Use the commands traceroute and nslookup
to assist you. You can even go to the MAC level
with JetDirect.

check to see that the JetDirect allows unix and windows. Turn AppleTalk off.

[Geoff Wild]

Can you:

hpnpadmin -v printerip

Do you have netscape on your HP-UX box?

Try connecting to the ip address with Netscape.

Use the linkloop command to test connectivity to the MAC address...


Rgds...Geoff

[Matthew Couper]

Turns out to of been a bad JetDirect card, once the card was replaced it now works 100%