I found a weird IP address on my network that had transmitted an insanely small amount of data. I put the address in my browser and got this. what the heck am I looking at?
UPDATE 10/4 6:47 EDT
I have been going through all the comments. THANKS!!!!!!
I did not know about the techniques listed, so they are extremely helpful.
Sorry for the slow update. As I mentioned below, I got behind with this yesterday so work cut into my evening.
I ran a port scan. The first syntax, -p, brought no joy. The nmap software itself suggested changing to -Pn. That brought an interesting response:
Failed to resolve "1-9999".
Nmap scan report for <Local IP Address>
Host is up (0.070s latency).
All 1000 scanned ports on 192.168.0.46 are in ignored states.
Not shown: 990 filtered tcp ports (no-response), 10 filtered tcp ports (host-unreach)
Nmap done: 1 IP address (1 host up) scanned in 6.03 seconds
Just to be absolutely sure, I turned off my work computer (the only windows box on my network) and reran the same syntax with the same results.
As I read this, there is definitely something on my network running windows that is not showing up on the DHCP.
UPDATE 10/6
I am working through all these suggestions. I am sorry for the slow responses, but I have my hands full with family weekend. I will post more next tomorrow.
But I did do one thing that has me scratching my head and wondering if this may be a wild goose chase.
I ran the nmap again per below with a completely fictional IP address within my normal range. It gave the exact same results:
nmap -A -T4 -p- -Pn <Fictional IP>
Starting Nmap 7.93 ( https://nmap.org ) at 2024-10-05 13:36 BST
Nmap scan report for <Fictional IP>
Host is up (0.054s latency).
All 65535 scanned ports on <Fictional IP> are in ignored states.
Any device can decide to set it's own IP so that's not too far fetched. Have any IoT crap like a water softener or colorful lights or speakers or cameras?
So, as others have saId this is just an unconfigured IIS server, which implies it's either a windows machine, or a windows based VM, well or someone put the default IIS files on another server, but that's unlikely.
When you say "weird" IP I'd wonder what you mean by that.
I think since it's probably a windows machine, from another windows machine typing nbtstat -A <ip> should give you the computer name and workgroup or domain they belong to. See if it matches anything you expect on your network.
If not, maybe it's time to change your WPA wifi key.
Edit: Also, I am big on wired networks. I mostly save WI-FI for smart and mobile devices. There is a lot of stuff on Ethernet that does not need a password.
Hmm. That would mean it's likely one of the following (well perhaps more options, but these spring to mind)
A windows machine that has the network set as a public network, or netbios specifically blocked on LAN.
A windows machine that has all the netbios services disabled.
Not a windows machine, or a container as others suggested that's running some kind of IIS install
Not a windows machine at all but for some weird reason IIS files and a web server setup.
I think you suggested in another comment, that it's not in your DHCP client list but has an IP in your normal range. Which suggests it is setup with a static IP. That is odd.
Some other people suggested it could be a container that is using a real IP rather than the NAT that docker etc usually use. I do know that you can use real IPs in containers, I've done it on my NAS to get a "proper" linux install on top of the NAS lite linux that is provided. But I would have expected that you'd know about that, since it would require someone to actually choose the IP address to use.
If you have managed switches you could find which port on which switch the MAC address (as found by lookuping up the arp record for the IP using arp -a) is on (provided the switch allows access to the forwarding tables). Of course, if they're on Wi-Fi it's only going to lead to the access point they're connecting to.
If you can, power stuff off and check if that web page is still available. Start with any Windows machines. It could be a virtual machine running inside of something else though.
I'd go around unplugging anything that might be connected to the network, like game consoles, smart TV, etc. It's unlikely, but maybe something has copied that same screen to throw you off.
does your router give you the MAC address of the device? You can look it up to see who manufactured it and then narrow down. This could be a device that has a web service running is all you are seeing right now.
Don't need the router. If you're on windows or linux, you just ping the ip then enter 'arp -a <ip>' it will show the MAC address for the IP from your machine's arp cache.
You can always start looking at how to use WireShark to sniff the packets and learn more about what is coming and going from that system. WireShark can be a daunting tool but if you look at some videos or walk through you should be able to get a handle on how to make it reveal only the one devices network traffic
Windows IIS probably from around the time of windows 8 so maybe 2012. Probably running on either windows server 2012 (like exchange, an active directory domain controller, or if you are unlucky sharepoint) or some weirdly configured appliance running windows 8 ish enterprise.
There was an appliance where the wifi chip was at the end of the power cable, embedded inside the plug. From the outside, you couldn't really tell. It was there so radiation inside the box couldn't affect the wireless signal as much.
I can imagine some genius thinking it's a good idea to run a server from inside a cable or a connected home appliance.
Depending on your router, it could have a docker setup with Windows on it. I've seen some strange shit on cheap routers with far too much processing power and storage.
Get the MAC address from the ARP table, and look up the OIN, should help you determine if it's virtual or physical, and if physical the type of NIC it's using.
The first few octets of the Mac address are unique to a manufacturer. This may at least help narrow which device it is. You can look it up at https://macaddress.io/
This is interesting. I had to modify it to nmap -A -T4 -p- -Pn <IP>.
It said the host is up with 0.077 seconds of latency. All 64k ports were scanned with 7 filtered tcp ports (host-unreachable) and the rest (no-response).
77ms of latency is pretty slow. Based off that I'd assume (but not rule out) that it's not: on the machine you used to run nmap, not on ethernet, probably wifi with a shitty connection
So, some really dumb, likely irrelevant, questions that might spark an idea:
Do you see anything weird connected in the wifi client list? (You said it wasn't given a dhcp lease, but it would still show as a wireless client even if it were static)
Are you running a VPN server or using VPN to bridge any networks?
You said you're running dual WAN, are those configured properly and not leaking random internet shit into your LAN?
Do you have anything that might be running some kind of out-of-band management system like DRAC on a dell server?
What's your IoT situation?
Do you have an on-site NVR for security cams?
Did you find the mac? If so what are the first 3 octets? Even if the vendor can't be found, there's always the chance some crazy ubernerd is going to recognize it. (If it's 00:d0:2c or 44:d9:e7 I got ya covered)
Again, most of those are probably irrelevant, but throwing the thoughts out there :)
If it is, look at the certificate. Which hostname is it for primarily? Which SAN (Subject Alternative Name - basically a list of all other hostnames the certificate is valid for) are set, if any? Which Certificate Authority issued the certificate or is it self signed?
Fun story, I live in a townhome, I had so bizarre network issues going on. Not able to stream to TV etc. finally started unplugging shit. Unplugged the router and saw the computer still happily downloading something WTF! Turns out a neighbor also had Ethernet over power and devices were randomly connecting to their network. Crazy ass shit.
nmap's seeing the 1-9999 as the next argument (expecting an IP address). In -Pn, the n is a placeholder for the port numbers you want to scan, so you want -P1-9999