Meraki Community

Bears · ‎Oct 31 2023

You nailed it! Wow! It is now responding to the ping. What's the effect basically in disabling this?

Bears · ‎Oct 31 2023

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.

Bears · ‎Oct 31 2023

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)

Bears · ‎Oct 31 2023

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

Bears · ‎Oct 31 2023

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

Bears · ‎Oct 31 2023

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

Meraki Community

About Bears

Bears

Community Record

Badges

Re: Unable to ping Biometric Device from PC of same VLAN

Re: Unable to ping Biometric Device from PC of same VLAN

Re: Unable to ping Biometric Device from PC of same VLAN

Re: Unable to ping Biometric Device from PC of same VLAN

Re: Unable to ping Biometric Device from PC of same VLAN

Unable to ping Biometric Device from PC of same VLAN

Re: Unable to ping Biometric Device from PC of same VLAN

Re: Unable to ping Biometric Device from PC of same VLAN