sijmensijmen@shrimp.vijf.life
Nov 16, 2026, 6:07 PM turned out the issue was that a colleague stuck the printer on the incorrect vlan, which put it on a different subnet
it wasn't actually the printer's, or Windows', fault!
it wasn't actually the printer's, or Windows', fault!