« Cousins - Madison, MS - 12/22/2010 | Main | Fixing the Beamer »
January 29, 2019
PeenieWallie Lives!
Wow. So, that really sucked. Still not sure what happened, but my best guess at this point is that every single network card connected to my LAN failed at the same time. I was able to get PeenieWallie running again by ordering 2 USB to Ethernet adapters, which were supposed to be delivered yesterday, but got here today.
So, I was able to bypassthe failed ethernet connections on two of my computers:
1) Upstairs notebook running Windows 7. The old ethernet card was IP address 192.168.2.107. The new ethernet card has the IP address of 192.168.2.14.
2) Changed the My Essentials Firewall > Virtual servers to route incoming traffic on port 80 to the new address of 192.168.2.14.
3) Downstairs desktop running XP.The downstairs PC has so many ethernet ports displayed on the taskbar that I'll never begin to grasp how/why it is the way it is. However, I pretty much don't use that PC anymore, so not overly concerned with this.
4) Wasn't sure why I couldn't see my NAS (Network Addressable Storage) devices downstairs, but when I looked at it again tonight, I saw that my switch was disconnected. So, I reconnected my switch to the router, and now I have my network back, along with all of my NAS, and both computers working, and PeenieWallie running. Lord. There's a reason other people don't do this. It's because they're smarter than me.
Many thanks to Robert Racansky for helping me to diagnose/troubleshoot the issues I was facing. Don't think I'd have figured it out without his help.
Posted by Rob Kiser on January 29, 2019 at 9:10 PM
Comments
"Upstairs notebook running Windows 7"
https://arstechnica.com/information-technology/2019/07/explainer-for-exploiting-wormable-bluekeep-flaw-posted-on-github/
Chances of destructive BlueKeep exploit rise with new explainer posted online
7/22/2019
A security researcher has published a detailed guide that shows how to execute malicious code on Windows computers still vulnerable to the critical BlueKeep vulnerability. The move significantly lowers the bar for writing exploits that wreak the kinds of destructive attacks not seen since the WannaCry and NotPetya attacks of 2017, researchers said.
The vulnerability affects Windows prior to version 8. Anyone who hasn't patched the vulnerability, tracked as CVE-2019-0708, should do so immediately. Patches for vulnerable versions still under support can be downloaded here. Updates for Windows XP, Vista, and Server 2003 are here.
Posted by: anonymous on July 23, 2019 at 8:01 PM