Timeline for How should I respond to an unrecognized client in my DHCP logs?
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 15, 2017 at 2:09 | vote | accept | CommunityBot | ||
| Apr 14, 2017 at 19:41 | history | tweeted | twitter.com/StackSecurity/status/852970155000909825 | ||
| Apr 13, 2017 at 1:25 | answer | added | anon | timeline score: 0 | |
| Apr 13, 2017 at 1:24 | comment | added | anon | Well, I'm embarrassed. Your comment reminded me that I briefly hooked up an old desktop with an ASUS motherboard this weekend. Sure enough, it has the same MAC address as I saw in my logs. I'd completely forgotten about it. False alarm -- but that said, I have no idea where the hostname, "DESKTOP-NE0L00T", came from. Some sort of bizarre randomly generated Windows 10 default, perhaps. | |
| Apr 12, 2017 at 11:57 | answer | added | Miguel | timeline score: 2 | |
| Apr 12, 2017 at 6:20 | comment | added | schroeder♦ | Change passwords? 'Asus' might merely be the manufacturer of the NIC, and not the whole machine. | |
| Apr 12, 2017 at 3:30 | answer | added | Trey Blalock | timeline score: 3 | |
| Apr 12, 2017 at 3:18 | history | edited | anon | CC BY-SA 3.0 | edited title |
| Apr 12, 2017 at 3:14 | review | First posts | |||
| Apr 12, 2017 at 6:20 | |||||
| Apr 12, 2017 at 3:12 | history | asked | anon | CC BY-SA 3.0 |