LAN machine can't ping printer

bmeeks

If I am interpreting your posted information correctly, then it seems neither the PC (computer) nor the VM router (pfSense) can ping the printer at 192.168.1.160. So, that points to an issue with the printer itself.

Three things to check:

First verify the printer's physical network connection. Maybe try swapping the network cable, unplugging and plugging back in the cable, etc.
Double check and verify that you set the IP subnet correctly on the printer. Maybe you have a typo in either the printer's IP address or its subnet (assuming here that it's not DHCP enabled).
Validate the printer is actually using the IP address you think it has. The printer may actually be using DHCP and has assigned itself a different address from the LAN.

johnpoz

@eiger3970-0 said in LAN machine can't ping printer:

192.168.1.255.

what is this suppose to represent?

[24.03-RELEASE][admin@sg4860.home.arpa]/root: ping 192.168.9.42
PING 192.168.9.42 (192.168.9.42): 56 data bytes
ping: sendto: Host is down
ping: sendto: Host is down
ping: sendto: Host is down

Host is down would point to can not arp for that IP, ie no response from the arp.. I have no 9.42 device - so yeah nothing is going to answer arp for that IP. You sure your printer is connected? Is it connected to a wire or wifi? You sure its IP just didn't change.

But no trying to talk to something on the same network that you can not arp for would mean no your not going to be able to ping it.

eiger3970 0

Thanks, I'll triple check the cable tomorrow in the daylight.

The computer did say Cable Unplugged, so I checked and the computer Ethernet cable was in, but after a wiggle the computer said Wired tick mark.

I've messed up my Home Assistant Zigbee to Wi-Fi network settings, so no lights except the monitors.

eiger3970 0

@eiger3970-0 I unplugged and plugged back in the printer Ethernet cable, but was already firmly in.
Nothing happened, but right now 5 hours later this computer suddenly started pinging the printer at 192.168.1.160 and added the printer.

Think I'll test the printer Ethernet cable with a VDV Multimedia tool to confirm the issue isn't the computer or VM router software.

JonathanLee

off topic bit, but I wanted to share something. I had to block all internet access to my printer because it was passing way to much data every time I printed or scanned to a server in Japan. I submitted a request to disable this and they said it was analytics based and I agreed to it. I did not so I simply blocked all external access. I do not understand why it needed that much analytics information for every single usage of it.

Anyway pfSense spotted it and blocks it now

JonathanLee

@eiger3970-0 did you set up a dns host override for its ip address and host name? that helped me a bunch with access to it

johnpoz

@JonathanLee if you can not arp for an IP, doesn't matter if you resolve some fqdn to the IP or not.

JonathanLee

@johnpoz with my AirPort Extreme that was the only way it would work with the proxy it needed that name stored because it would access it from the url for the scanner part of it.

johnpoz

@JonathanLee Which has zero to do with trying to ping something on the same network as you and not getting back an arp response.. Do you think this guy is running a transparent proxy between host X on network A and host Y on the same network A that proxies icmp traffic?

Both errors he showed, dest host unreachable and host is down scream - hey I tried to arp for that IP and got no answer!

JonathanLee

Do you have icmp allowed on the firewall for that subnet?

JonathanLee

@johnpoz you know me I assume everything is proxies

bmeeks

@JonathanLee said in LAN machine can't ping printer:

Do you have icmp allowed on the firewall for that subnet?

@JonathanLee, he has already said both devices are on the same subnet. There is no network firewall in play at all. The only possibility would be a host firewall in place on the PC or printer, but I've never seen a printer with a built-in host firewall.

johnpoz

@bmeeks yeah me neither.. Even if it did have a firewall, for sake of argument.. The error would of been timeout vs those errors. Since even firewalls allow for arp.

JonathanLee

@johnpoz said in LAN machine can't ping printer:

192.168.1.255.

You mean 255.255.255.0 right @eiger3970-0

johnpoz

@JonathanLee my guess is he just posted the numbers he saw on an output of ifconfig or something without really understanding what it was

inet 192.168.2.253 netmask 0xffffff00 broadcast 192.168.2.255

That is just showing the directed broadcast address.

eiger3970 0

This post is deleted!

eiger3970 0

@JonathanLee I'm confused?
My printer did have network settings:
192.168.1.160/24 255.255.255.0, but I changed it to:
192.168.1.160/24 192.168.1.255, because the output of the LAN computer and VM router both show:
192.168.1.120/24 192.168.1.255 and:
192.168.1.170/24 192.168.1.255 respectively.

I have always used 255.255.255.0, so I'm a bit unclear why this changed to 192.168.1.255?

johnpoz

@eiger3970-0 nothing changed the mask should be 255.255.255.0 or /24.. That 192.168.1.255 is the directed broadcast address.. See the netmask there in my example 0xffffff00, that would convert to 255.255.255.0

No wonder your having issues if you changed the mask to 192.168.1.255 - which to be honest not sure why the printer would even accept such a number, its not a valid network mask.

eiger3970 0

@johnpoz thanks.
I changed 255.255.255.0 to 192.168.1.255 after the problem, as a fix attempt.

Yes, somehow it's working, but I'll change back to the typical 255.255.255.0 on the printer.

JonathanLee

@eiger3970-0 Don't change that it should be 255.255.255.0 as your subnet with the cider notion of /24