New
#21
I found that out the hard way when I used to have a Nook and Windows would see it as something different.
Manufacturers for phones and tablets are using the same chips and circuit designs, because there really is not much difference any more between the two devices, other then size and RAM.
Also you have to flush the DNS and reset Winsock, since Windows 10 tends to remember old stuff on the network, not forget it when you reboot.
The other is turning off Smb 2 & 3, which is fixing a lot of these issues.
Microsoft felt in their stupidity of wisdom, that SMB/CFS had to be crippled in 10586.
See the last part for Client and enter in Powershell as an admin(right click and choose "Administrator") the following:
To disable SMBv2 and SMBv3 on the SMB client, run the following commands:
sc.exe config lanmanworkstation depend=bowser/mrxsmb10/nsi
sc.exe config mrxsmb20 start=disabled
It should hopefully fix some issues. The handsets if they are out there. The MAC's should be showing up in your router log.
Anytime you see this and question. Go into the router and check for what MAC matches what IP. Then if you are able to label the devices in the router, put a label for you to be able to know active devices are live.
I really do not know if Microsoft will ever get their game together with the Networking side. Since 10 has continued to have problems in the network side, depending on the person and their setup.