• 9point6@lemmy.world
      link
      fedilink
      arrow-up
      16
      ·
      edit-2
      10 hours ago

      Hmm

      I’d maybe try systematically turning any other devices off you think could potentially have the grunt to run windows server in a container or VM.

      Do you have a Mac/Linux machine handy? If you run arp -a in one terminal and ping the unusual IP in another, that should give you a corresponding MAC address for the device. You can then look up the MAC address and see if it gives you any more info about the device running it—it might not but you never know. You can use something like https://dnschecker.org/mac-lookup.php

      I guess next you could look at taking that MAC and blocking it in your router control panel and see if anything starts complaining

      • thermal_shock@lemmy.world
        link
        fedilink
        English
        arrow-up
        3
        ·
        4 hours ago

        I guess next you could look at taking that MAC and blocking it in your router control panel and see if anything starts complaining

        I love the “see who screams” method, my coworkers do no. it’s usually instant.

      • Agent641@lemmy.world
        link
        fedilink
        arrow-up
        9
        ·
        10 hours ago

        In addition, you might like to do a portscan on that IP address to see if any other ports reaveal something more interesting.

        You can run this in cmd prompt, I think, if nmap is available on your windows machine:

        nmap -p 1-9999 192.168.1.1

        IIS can only run on a windows OS, so it must be a windows physical machine or VM connected to your network.