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.
No, you just stop telling everyone else about it.
Technically, no. The last few have been significantly below either measure of inflation. So in real terms, I've had a wage cut!
Raises where you work are still based on merit? Damn!
Packets are lost all the time. Especially when uploading or downloading.
Anyone running a webserver and looking at their logs will know AI is being trained on EVERYTHING. There are so many crawlers for AI that are literally ripping the internet wholesale. Reddit just got in on charging the AI companies for access to freely contributed content. For everyone else, they're just outright stealing it.
It's specifically implied? :P
Hah, we used to have some of those AUI to 10Base2 transducers back in the day in the office. Definitely had one on the IBM RS6000/220 box.
"it goes up to eleven"
Yep, less overheads! This is the way.
The only way that immediately springs to mind is so unlikely to happen. It requires multiple faults/mistakes.
1: The chassis of one of the two units became live (connected to "hot" for you Americans) but was also not grounded in any way.
2: The chassis of the other WAS grounded and created a circuit for the current to flow.
3: There was no RCD (GFCD or whatever you guys call it) on the circuit.
In this way, that pipe would be the only thing connecting the two devices, and the resistance is causing a huge amount of heat (just like an incandescent bulb, or a heating element does by design).
Probably other possibilities, but it's just the first thing I could think of that could potentially produce this result. But, that's a lot of safety features to have either failed or just simply not been in place for this to be possible. So, frankly I hope I'm totally wrong.
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.