09-05-2014 11:00 AM
Just wondering if anyone has heard or experience the following issue. My desktop technician contacted me this morning about 3 users complaining their macbooks renamed themselves because it says there is another machine with the same name on the network.
An example of the valid machine name is US159903. This machine renamed itself to US159903-3. I see these entries in the controller but in Airwave I only see the entry for US159903. In the DHCP server I only see the entry for US159903 as well. As you can see it's using the same IP and has the same MAC address...I'm a bit confused at how this could happen...let alone the machine renaming itself without user/admin intervention...
Any thoughts/ideas or experiences are helpful!
(mtc-mc3b-wlc1) #show user-table | include 159903
10.66.9.128 b8:e8:56:06:c1:88 authenticated 00:04:03 d8:c7:c8:cb:91:70 Wireless RestrictedAccess/d8:c7:c8:39:17:10/a-HT AOL-RestrictedAccess tunnel OS X us159903-3
(mtc-mc3b-wlc1) #show user-table | include 159903-3
10.66.9.128 b8:e8:56:06:c1:88 authenticated 00:04:04 d8:c7:c8:cb:91:70 Wireless RestrictedAccess/d8:c7:c8:39:17:10/a-HT AOL-RestrictedAccess tunnel OS X us159903-3
09-05-2014 11:13 AM
I have seen that with my MAC when my wired interface and wireless interface are in the same subnet. Per Apple, its a behavior where OSX sees a bonjour annoucement for a device with the same name.
Regarding the output you supplied below, is that actually a duplicate entry? Since you're using pipe, an include of 159903 would match for both 159903 and 159903-3. I would do "show user mac b8:e8:56:06:c1:88" instead.
The hostname field in the user table is populated by the DHCP request of the client. It's possible that Airwave isn't accepting the updated information since everything else is the same.