Thanks for this fast reply! ... View more

@Rudy wrote: Why isn't everyone seeing this behavior?  Does everyone override the client name by manually entering one?  I doubt it... I agree, maybe, there is an explanation for it... I can only imagine, that other customers don´t really use this part of the dashboard to view information about the connected clients. Maybe, they are also only looking at IP or Mac address...?! Maybe it is also depending of how your device landscape looks like, what software and software firewallsettings are there?!   What I can say is, that I´m responsible for different meraki customers, with thousands of clients. And I see this in many networks....      ... View more

Probably you can forget it, I´ve come to a point to say, I do not care any more, because they want you to proof, that they are doing something wrong, you should show packetcaptures where this can be clearly seen. But that´s not to easy, because you cannot forget a client completely in the dashboard, the hostnames are kept in there, even if you use the "forget client" feature. So you cannot use one client to perform different tests. mDNS Hostnames can only be overwritten by new mDNS information. This makes testing very difficult, as you always need new clients.   My assumption: I think that code in software beeing used on the devices, is generating mDNS packets with hostnames in it. In this case, if you see this UUID like information in the dashboard as a hostname, it is not the operating system itself, but an application generating it. The problem here is: Meraki does not differentiate between "only" applications sending out some packets, that should not be analysed for the hostname to be displayed in the dashboard.   In general Meraki says, it is not an issue, its an isolated case:   Message from 11.09.2020:   "Greetings,   Thanks for your reply,   I've investigated this further with our internal product specialist teams and confirmed there are no reports of this issue currently and more so we would need to acquire further data from the case to troubleshoot this further."     So all of you, having problems, in real you don´t have no problems! Since a few month since creating this ticket and reading all the posts from users with the same issue, I can say, that they don´t really care.     ... View more

@ITPointeMan @Roux    Hey guys,   Meraki claims, that something on the client side supposedly changed. This could technically be, but I think it is very unlikely.   What for operating systems are affected in your network? Others than Windows10, iOS, Android?    Did you make packetcaptures to verify the claim, that MDNS is the root cause and the devices actually broadcast these strange names? I also do not believe, that clients do not have an uniqe identifier in the Meraki world.   I checked it and I could not see any packets containing these strange hostnames, I only found the correct ones. So up to know, there is no proof that could back up Meraki´s claims.   I´m still waiting for a logical explanation...     ... View more

Hi all!   Is somebody still experiencing this issue and can somebody say, what could be the root cause?   It affects different operating systems: Windows 10, Android, iOS. So if Meraki really didn´t really change anything, what change could be a root cause affecting all different systems?      @PhilipDAth   You are describing a "privacy" names feature. Do you have a source of information to this new feature?      Appreciate your feedback. ... View more

Hi & Thanks for the information. ... View more

Ok, seems to be like that, but why is that? What is the NPS doing different? ... View more

Hi all,   Im struggling with the same iPSK-NPS issue. I can tell you, that it is possible to generate a Radius Accept message, even if you have no AD users (theres a setting for that). But:  What I can see, that all the additional attributes are missing in the Access-Accept message. There´s only the t=Class(25) Attribute in it, nothing more.         Did someone ever managed to get this running? Seems to be like an NPS issue.       ... View more

Take a read: https://community.meraki.com/t5/Wireless-LAN/Updated-network-with-MR42E-to-26-6-1-causes-network-outtages/m-p/79306 ... View more