Incorrect client identification in event log

[JonP]

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 to track a malicious actor through our network (it's just porn, not hacking but could easily be) and it just doesn't work. You find the client in the event log just fine, but when you click on them you are either taken to a (seemingly) random device, or a "Sorry we could not find that client. Please go back and try again".

I've had a case open with support since May and we are no closer to a resolution. They even confirmed it happens to them, too!

Does anybody else have this problem, or is it something peculiar to our network? I just need to be able to click through on the event log page and a) get a client, and b) be sure that this is THE client I clicked on.

[cmr]

I see this occasionally, but not usually.

• What client identification mode are you using on the network?
• What devices do you have? MX, MS, MR etc.
• Does it work some of the time, but not at other times? i.e. wired clients are okay, but not wireless etc.

[JonP]

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 MR44s

3. It has worked previously intermittently with no pattern such as you suggest. Now it doesn't work at all for any device type. I either click the device and get taken to a different device, or click the device and get "Sorry...".