Printers Unable to Communicate Across VLANs with Static IP Assignment

[AdnanKhan]

Hello

I'm experiencing an issue with my Meraki network where printers assigned static IP addresses aren't able to communicate across inter-VLANs. Strangely, everything works perfectly fine when the printers are set to obtain IP addresses via DHCP. I've conducted packet tracer tests, and it seems that traffic is reaching the port on the switch and receiving responses. Interestingly, pinging the devices from the same network isn't yielding any responses either. Users within the same VLAN as the printers can connect to them without any issues.

Has anyone encountered a similar problem with Meraki networks? Any insights or troubleshooting steps would be greatly appreciated.

Thank you!

[alemabrahao]

It's connected across WiFi?

[alemabrahao]

Mandatory DHCP

Mandatory DHCP requires client devices use DHCP for IP assignment. All 802.11ac Wave 2 capable MR access points running MR 26.0 firmware or later support this feature.

Enabled: Wireless clients associated to an AP (either new associations or clients that roamed from another AP) that have not requested a DHCP address are placed in a blocked state and are not able to send any traffic on LAN and WAN.

Disabled: The default setting for this feature. Wireless clients configured with static IPs are not required to request a DHCP address.

https://documentation.meraki.com/MR/Access_Control#Mandatory_DHCP

[AdnanKhan]

I have mandatory DHCP enable on VLAN that printers are as well as on AP, and users VLAN

[cmr]

@AdnanKhan if you have mandatory DHCP enabled and then set a static IP on the device it will not connect.  You should use Fixed IP assignment in the DHCP scope to achieve this, or disable mandatory DHCP.

[AdnanKhan]

No, the printers are connected to MS125 ports, not via WiFi. They are connected directly to the network switch.

[alemabrahao]

So make sure you have configured the correct Gateway on the printer.

Troubleshooting VLAN Printer Sharing Issue on Meraki Network - The Meraki Community

[AdnanKhan]

I do have the correct gateway pointing to VLAN default ip 

[alemabrahao]

Who is the network's default gateway (ie: an L3 switch, an MX?).

[AdnanKhan]

VLAN interface IP is the default gateway for these printers. 

[alemabrahao]

Another question, you are not setting any VLAN when you configure the static IP on the printers, right?

[AdnanKhan]

That's correct, VLANs are not configured on the printers themselves when assigning static IP addresses. VLAN configuration is managed at the network level under MX."

[AdnanKhan]

I can ping any other device just not these 3 printers I have in this office. 

[ww]

Some devices dont respond to ping.

If you can print within the same vlan, but cant ping them from a client in that same vlan, then they just dont respond to ping.

[GreenMan]

MS125s aren't routing switches...   How are you routing between the two VLANs?   I'm wondering if this is multicast discovery-related?  Something along these lines?   https://documentation.meraki.com/MX/Other_Topics/Configuring_Bonjour_forwarding_for_the_MX_Security_...

[AdnanKhan]

My understanding is that Banjour is a protocol that leverages mDNS for network discovery of other Bonjour enabled devices. Only apply to Apple devices. These are 2 Xerox and 1 HP printer. Printing from Win11 machines. 
I can get to any other device across any VLAN just not these devices. 

[ranslobo]

As far as I know, Bonjour protocol doesn't support L3.
https://www.cisco.com/c/en/us/solutions/collateral/enterprise-networks/dna-service-for-bonjour-dg.ht....

[PhilipDAth]

>I'm experiencing an issue with my Meraki network where printers assigned static IP addresses aren't able to communicate across inter-VLANs.

#1 issue - wrong subnet mask on printer.

#2 issue - wrong default gateway configured on printer.

Are you 100% sure these are both correct?

Another easy solution - keep using DHCP but make a DHCP reservation for the printer.

[AdnanKhan]

I have confirm 
#1. subnet mask is correct on the printer. 

#2. default gateway is configured correct on the printers. 
I even had Meraki Support look into my network to make sure I am not doing anything wrong. But after spending an hr of troubleshooting they think it's the printers. I got tech from Xerox coming out tomorrow to see if they have an answer. I personally don't think this is the case. 

I did the DHCP reservation for these printers from the switch port earlier, which seems to be working for now. 

I am new to Meraki. This is the first office we converted to Meraki from traditional Cisco gears. This is a small office with less than 50 users with very basic network. Hopping to iron out all the issues before moving our bigger offices under Meraki with lot more complexity. 

[AdnanKhan]

Thanks everyone for trying to help me with this issue. If I find the answer I will post it here. 

Since I am new to Meraki. I am sure I'll be back 🤖 with other issues. 😂

[DarrenOC]

Jumping on this late but assume you’ve hooked your laptop into the same printer port and given yourself the same IP etc and tested that way?

[AdnanKhan]

Thank you. 

I didn't but we did move the printers to different ports on the switch and on the patch panel also on different VLANs just to roll out any hiccup with ports but no go. Seems working fine since we switch the NIC to DHCP. Using Meraki switch DHCP reserve option to keep the same IP address like PhillipDath mention earlier in this post.

[Mike6116]

Just go to devices tab  and then  clic on Fixed IP for that device and the DHCP will always assign the same ip for that device

[IAMTLOG]

We saw this same issue and it was the oddest ever. We found using a /22 for the VLAN interface caused the issue. The issue is gone just by changing the interface to a /24 or /21 (please consider the network implication before doing this).