ping printer times out when wireless, ok when wired

Question

I have been managing our home network now for many years, and this is the weirdest problem I have ever seen:

I have a router (Dlink DIR-655) to which a printer is connected directly via cat5e. The router also provides wireless access. Router has IP 192.168.0.1, the printer is .0.2. Now if I connect my laptop to the LAN via cat5e, I can ping the printer from laptop, but if I connect the same laptop via wireless (and disconnect its cat5e), it can no longer ping the printer.

Surely it is the laptop, right? Wrong: this happens with all 3 laptops we have the house: connect the laptop via cat5e, it can ping printer, otherwise via wireless it cannot. The laptops are all very different, two are work laptops from different companies, the third is the kids machine.

So surely ping over wireless is disallowed by router! Wrong: each laptop, independent of how it is connected to LAN (wireless or cat5e) can ping the other laptops. This means wired laptop can ping both wired and wireless laptop; wireless laptop can ping both wired and wireless laptop; but only wired laptop can ping printer.

How does this make sense?

Answer 1

Thanks for all the comments. Turns out that the problem was a wrong MAC address entry but you might be interested in how that could explain the behavior described in my question, because indeed the printer could be pinged and even printed fine from wired laptops. Turns out that my router supports complete blockage of wireless devices from my LAN by MAC address, but only partial restriction for wired devices. The partial is what I didn't know was a possibility, and I don't know if all routers are like that. The printer MAC address that was in the router's table was that of the old printer, but because of the partial non-restriction, the printer worked fine from wired devices. This bit from the router's documentation explains it:

Note that a wired device that is blocked cannot access the WAN and cannot access wireless devices on the LAN, but can still access other wired devices on the LAN.

That's the part that I was totally not expecting and explains all behavior listed in my question. I really thought I was missing something fundamental about networking so despite the silliness of the mistake, I'm glad as I learnt something.