I’ve been asked time and again to do something about computers and internet connections, I’ve always refused because you can’t possibly cover everything, there are always outliers and exceptions, and of necessity any how to for dummies is going to be pedantically incorrect for those in the know, and there is another whole avenue of criticism opened up.
So this is more a guerilla guide, quick and dirty.
Malware and shit.
Windows PC, Start > run > type “msconfig” press return, (windows key + r key will also open the run dialogue) “Startup” tab, click disable all, services tab, check hide all microsoft services, click disable all, click ok, computer will want to restart, let it.
Download and run COMBOFIX as administrator by right clicking on the downloaded file, let it run, then ditto for MALWAREBYTES ANTI MALWARE and !AVAST (free) ANTI VIRUS.
Apart from this it is mainly command line stuff, windows key + r, type “cmd” press return..
eventvwr.exe – starts the event viewer, which records issues and suchlike with your windows machine or server
compmgmt.msc – computer management from the control panel
devmgmt.msc – device manager from the control panel
services.msc – services from the computer management panel
ipconfig /all – what all your network adapters are currently doing or set to
getmac – gets the mac address of any connected / used network connections on your computer, eh what’s my mac address
whoami – what it says, currently logged in domain / user
systeminfo – what it says, system hardware info
tracert – traceroute, google DNS is 8.8.8.8 so a handy one to trace to
nslookup google.com – gives the ip address(es) of nameservers for the specified domain, in this case google.com
wmic os get lastbootuptime – does what it says
ncpa.cpl === Network Connections panel from control panel
arp -a === IP address and Ethernet address for hosts your machine knows of on the network, emphasis on that your machine knows about, if your machine does not know about your router or printer or whatever you are having issues with
pathping === traceroute that collects detailed packet loss statistics. 275 seconds, ping will test connectivity, pathping gives much more info, for example basic windows machines do not handle encapsulation as used by cisco and other “pukka” kit, so you can connect to a cisco box and *know* that everything should work, but you can’t ping the cisco, this command will tell you a lot more than “shrugs, nobody answered man” which maybe what you need to convince whoever runs the cisco box the problem is their end, not yours.
putting > results.txt (>ping 8.8.8.8 > results.txt) will pipe the output of the ping (or any other) command to a new document/file called “results.txt” (or any other name you choose) which will be located in the root of the user name folder for the user you are currently logged in as, in C:\users
putting >> results.txt will APPEND the output to that file, not overwrite it with a new one, single > vs double >>
=============================
Quick and dirty shit but the three windows apps at the top really comprise enough for people with a malware infected pc, to get it back to the point where they can start a proper cleaning and backup process, ok, it gets you to a starting point, it isn’t a solution, in 99% of cases I don’t wanna know, you or your kids or whatever are the cunts that downloaded and installed all the crapware, now you can go and solve it… this is the equivalent of “give a hungry man a fishing rod and tell them to fuck off” as opposed to giving them fish all the time.
The windows command line commands, they are the only ones I use, 99.9% of the time, I look at these lists of essential commands on various websites and never agree with them, they always seem to list useless ones, and omit useful ones, the commend line commands to bring up things like the services dialogue will work even when trying it with the mouse and pointer will NOT work, some malware deliberately blocks access to this stuff via mouse and pointer, the others are all about getting that PC to talk to something else over a network connection, so you are either diagnosing the pc itself, or the LAN, or even identifying that the issue does / does not lie with the router itself.
If you have two devices on a network, it really does not matter what they are, device A and device B, just because you can ping device B *from* device A, does *not* mean you can ping device A *from* device B, so if you only test from one device, you can sit there and scream why doesn’t it fucking work, I can *see* the other device from here, the answer is it takes two to tango, and just cos you can see it, doesn’t mean it can see you… and as you can see from the encapsulation thing above, if it cannot see you, that may not be its fault, it may be yours, eg you have your firewall turned on, and it is set to block that thing you are trying to do.
+++++++++++++++++++++++++++++++++++
What this is all about is that the SYMPTOM and the CAUSE are two different things, “help my email is not working” is a symptom, there are various possible causes, indeed there may be more than one, and the console commands above are, in my own personal experience, enough of a swiss army knife to get you started on identifying the causes.
If you learn those 14, or carry them around on a scrap of paper in your wallet, and you STILL cannot identify the problem, then quite frankly speaking, you’re not good enough to understand the information that the system is presenting you with, so some extensive googling on another working machine, or talking to someone who does know, is in order….. poke and hope is likely to break more than it fixes.
del, rd, mountvol, diskpart, syskey and many other windows console commands can *thoroughly* destroy a system, for example “Mountvol c: / d” where the d is a typo, windows will continue to work on the surface, giving no indication whatsoever of the destruction that is taking place right beneath your nose… I actually know of one cunt who was told that this command was used to fix windows sounds / volume issues, oops…
====================================
When in doubt, provided you are already ahead of the curve and have your important data readily backed up, provided you are ahead of the curve and have all your hardware drivers handy, provided you are ahead of the curve and have a PC with a proper BIOS or a ***full*** UEFI BIOS that you know for a fact will do an win7 install in legacy mode without needing to slipstream USB3 drivers, fuck it, do a fresh install and tell the installer to delete all partitions on the root disk and start again.
It will fix *****all***** your computer problems, unless they are hardware related.