Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Greetings fellow community'ers.I am at my whits end with Meraki to the point where I want to rip it out and put in a real solution from their better half.We have a recurrent issue where clients are incorrectly identified in the event log. I am trying...
Hello Community,I've set up daily reporting on our network for a variety of things, but one thing I continually see is odd applications listed in the "Top applications by usage" section.Dotted amongst the usual Office 365, Microsoft SQL Server etc ar...
Hello all,Does anyone know when Meraki are planning to fix the false positives in the event logs for IP conflict Source IP and/or VLAN mismatch? We're still seeing this in our logs on a daily basis and we can't tell any genuine issues apart from the ...
Hi folks,We have content filtering set up on our MX, and it has suddenly started reporting that our Domain Controler is trying to reach pornographic sites at 3:33am most mornings. Our PDC is also our DNS server for the network.We can't find any obvio...
Hello team,We are investigating an issue in our backup environment. We utilise Veeam and a job is supposed to run every night to copy our backups into PeaSoup cloud. This copy job has recently started failing.We spoke with Veeam who said that our fir...
Greetings,1. Unique client identifier. Tracking by MAC makes no difference.2. All of the above. MX105's, mixture of MS switches, MR 36s and MR44s3. It has worked previously intermittently with no pattern such as you suggest. Now it doesn't work at al...
Did you get anywhere with this? I appreciate I am reopening a 12+ month old thread, but I am having the same problem and don't see a fix anywhere online.I've tried formatting the cells in Excel as custom mmm dd hh:mm:ss as it appears on screen in the...
Hello - This is Cameron's colleague We had on average 300-400 clients from memory and the MX only supported up to 300. It took an inordinate amount of time to get Meraki to see this as the issue. We had the device replaced and it still happened. Eve...