Amazon Device randomly showing up on Network.

Anonymous
2017-10-08T00:11:54+00:00

* Moderator note on Jan 2, 2021.

This old, long thread is being locked.

See posts by Steve-D-M on page 19 and by jamesdelwood on page 20.

The websites appuals.com and thewindowsclub.com may be recommending programs you shouldn't download or install. The information on the pages is safe, but the programs are often classified as PUPs (Potentiall Unwanted Programs.)

-   -   -   -   -   -   -

Original question:

I've got a random Amazon KFAUWI device showing up on my network as a device beside my driver for my router. Can anyone help? I am sure it is not a device in my house, as everything is set to something we've done or one of our names. Can anyone tell me if i'm stupid or if this is a general happening?

Windows for home | Windows 10 | Security and privacy

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

214 additional answers

Sort by: Most helpful
  1. Anonymous
    2020-09-23T13:35:26+00:00

    I'm definitely not advising that people ignore unknown devices appearing on their network....but....what I have learned is that despite UPnP (Universal Plug & Play) being as old as dirt, some devices still don't bother setting themselves up to communicate what they are.

    Sometimes they fall back on the manufacturer, like when I see something called "Arris" and I realize that my ISP uses Arris equipment, so that's one of their many plastic wedges they require me to have in my home for Cable or Internet.

    Sometimes they pass along the name of the software that's communicating, like the device I have named "GainSpan" - that's a software company that makes various Wi-Fi chipsets, in devices like my FitBit scale that calls itself "GainSpan" because somebody at FitBit didn't tweak the settings somewhere to report "I'm a FitBit Aria" (or better yet, "I'm a FitBit Aria Digital Scale").

    Some devices are temporarily generated, like the one that brought me to this thread today:  I needed to make some changes to my network settings and it looks like my router temporarily created a device called "csm_biscuit", used that to get done what it needed to do, and then deleted it.

    I've learned to do a simple set of steps to figure this out:

    1. In Windows Explorer, see if I can connect to the thing - some have web pages that tell you what they are and/or let you access their settings
    2. If I can't connect that way, I see if I can find the IP address, either in the properties in Windows Explorer or via my Router's Admin console.  Then try to hit that IP in a browser and see if it comes up with a web page.
    3. I do a web search for the device name and leave off any numbers that look like they're generated.  For example, if I saw "csm_biscuit14231ABCD" then I'd just search for "csm_biscuit" and see what other people have found.
    4. Once I figure out what it is, I make a note of it, log into my Router, and give it a name there to help me know at a glance what it is and not have to track it down again.
    5. For extra credit, I save my router settings to a file and put that on a thumb drive so I can get all this work back if I need to.

    Hope this helps!

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2018-01-20T15:21:59+00:00

    Is any all all of you have a Amazon device on their network, like a Kindle Fire, echo, etc., and use Alexa?

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2018-01-05T16:38:37+00:00

    I have the same device showing up on my Surface Pro (windows 10), Computer shows as Austin or Douglas with an Amazon manufacturer. It seems to be random.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2017-11-17T20:05:10+00:00

    My pc has an AMD cpu. I wonder if that is relevant. One of the recent insider builds couldn't be installed on systems with AMD cpus.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments No comments