Device: Meraki MX 100
VLan ID 100: 192.168.100.x (Printer installed here)
VLan ID 200: 192.168.200.x
VLan ID 300: 192.168.200.x
Printer ID: 192.168.100.64
Test PC: 192.168.200.1
Can you telnet the printer on some port ? 515 , 9100 or any other printing ports used by your printer ? Are you sure that you don't have any L3 firewall rules blocking that type of trafic ?
Go to your firewall settings of that MX100 :
Do you see any L3 firewall rules ? :
You will need atleast one rule to allow the flow between your workstations on vlan 200-300 to your vlan 100. You can add an 'allow any any any' rule to see if that works , and adjust the details later.
Yes, currently, all sources are set to deny. I've added an 'Allow' rule for VLAN 10, which is connected to the printer. However, I'm still unable to Telnet from the other VLANs.
Yes, I changed it to 'Any,' but the issue remains. The strange thing is that I can't use Telnet from 192.168.1.191, which is on the same network as the printer, but I can print from this laptop. It appears that the Telnet feature is not enabled on Meraki. Do you know how I can confirm?
23 is the default telnet port but you can use any port. It's basically a basic way to check that the port is reachable without sending a print. Although telnet to 9100 can be used to spit output directly to a printer and have it print. Not every device will allow telnet from a remote network. So there could be something going on with the printer.
You would likely want to allow more ports for the printer, 9100 is a RAW port but they often have other ports or use Multicast like WDS/Airprint if you want it discoverable. If you don't know which ports you need open doing an allow-all to the printer and printing with a packet capture going filtered for the traffic might be a good idea to find which ports you need to have open. If you need the printer discoverable on other VLANs bonjour forwarding can be used.
I had to deal with a similair issue and spent hours with Meraki support. Turns out the NBar was misclasifying the traffic and blocked the communications and reset those connections. The rule in our case was detected as "webmail".
After upgrading the firmware to the latest. The issue is resolved.
What makes it frustrating is that. If you reboot the MX it works for a short while then randomly stops working until another reboot. This happens on many network all runing on the exact same firmware (part of a template).
Try the Event Logs under network and look for Nbar events.
Hey, amabt Thanks for taking time to read my question.
The firmware was updated a while ago. (Current version: MX 18.107.2)
Actually, I had no problems using the printer before with the current VLAN setup, but something happened that I don't even remember. The printer suddenly stopped communicating over the VLAN. It could be a device issue, but I want to verify whether this is a device issue or a problem with the functions.
I searched for 'NBar' in the event log, but found no results. Any ideas?