Unable to ping Biometric Device from PC of same VLAN

Solved
Bears
Here to help

Unable to ping Biometric Device from PC of same VLAN

Before migrating to Meraki switch (MS120) and access points (MR36), the PC which acts as Time and Attendance Server (IP- 192.168.2.250) can ping the Biometric device (192.168.2.10). They are in the same VLAN.

 

After replacing the switch and AP, said biometric is no longer accessible. Other hosts in same subnet are pingable from said server, only this biometric device is not. I made sure the IP,SM,GW are correct. We're using Palo Alto firewall and again, no changes made in the firewall or network aside from replacing the switch and AP.

DHCP comes from the firewall.

Anything I need to look?

 

MS Switch Firmware 16.6.1

MR AP- Firmware 30.5

1 Accepted Solution
PhilipDAth
Kind of a big deal
Kind of a big deal

Under Wireless/Access Control, have you got Mandatory DHCP disabled?

 

PhilipDAth_0-1698811066764.png

 

View solution in original post

11 Replies 11
ww
Kind of a big deal
Kind of a big deal

Can you check the MR firewall settings.

Is L2 isolation disabled? Are there no deny rules?

Bears
Here to help

Bears_0-1698770116032.png

 

hello, i just changed the status to Allow and still not pingable.

ww
Kind of a big deal
Kind of a big deal

Did you set that on the correct ssid ?

Any acl on the switch maybe?

Port isolation is disabled on the switch ports?

 

If both devices are in the same vlan and ip range they should be able to ping eachother ( if the client itself allows  te be pinged) if above mentioned setting allow them

Bears
Here to help

Thanks for reply.

Yes, the rule applied to correct SSID

ACL in switch has policy "Allow" all Any

Port isolation is "Disabled"

 

Biometric has static IP and is connected to WiFi

PC is connected over wired (DHCP client)

BlakeRichardson
Kind of a big deal
Kind of a big deal

Have you checked VLAN settings for both ports?  Can the MS see the biometric device attached to the port? It should be listed under the Current Clients information.

 

Screenshot 2023-11-01 at 7.45.22 AM.png

If you found this post helpful, please give it Kudos. If my answer solves your problem, please click Accept as Solution so others can benefit from it.
Bears
Here to help

Thanks for reply.

Biometric has static IP and is connected to WiFi

PC is connected over wired (DHCP client) to switch

 

Only the biometric is visible in Current clients table.

PhilipDAth
Kind of a big deal
Kind of a big deal

The troubleshooting so far indicates to me the issue is with the biometric device.

 

Does the biometric device attach via WiFi?

 

Because you have replaced your switching, every device would have had to get a DHCP address again.  Is there any chance you have an IP conflict? If your biometric device has a static IP address (is this the case?) - is this address excluded from DHCP?

Bears
Here to help

Thanks for your reply.
The biometric is connected over Wifi while the PC is wired. Biometric has static IP settings in the device

PhilipDAth
Kind of a big deal
Kind of a big deal

Under Wireless/Access Control, have you got Mandatory DHCP disabled?

 

PhilipDAth_0-1698811066764.png

 

Bears
Here to help

You nailed it! Wow! It is now responding to the ping.

What's the effect basically in disabling this?

alemabrahao
Kind of a big deal
Kind of a big deal

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.

I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.
Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.
Labels