Good evening, I felt I would share a quick fix for an issue that came up when we were trying to repair a brand new Dell Inspiron 2305 (the big touch screen computer). Long story short, if you are trying to check for Windows Updates and it is failing with the Error code 0x80072EE2 even after a factory image, please read ahead for a quick fix. Turns out that Dell misconfigured the factory image on at least one of the machines that got out of the factory. They are configured to use a WSUS (Windows Server Update Services) server that is internal to Dell (at the IP address 172.23.49.241 which is an internal IP). This obviously doesn't work once the computer leaves Dell. To fix this problem, follow these steps:
Hey everybody, you may (or may not) have noticed that I have been pretty quiet on my site here. I am still alive and well, and have been working on quite a few things in general which have prevented me from devoting pretty much any time to my site. I hope to get at least something new on here pretty soon but until then I will tell you what I have been working on:
Well, after getting fed up with using WordPress (don't get me wrong, it's a great platform but it was starting to run pretty slow), I have re-coded my entire blog engine from scratch. I believe that I have the site almost completely back to the way it was before, and everything should be completely operational. Please have a look around and be on the lookout for some new articles. I plan on covering a few new topics, including the following:
- Actual malware analysis/removal
- Some C# and ASP.net programming
- Possibly some ham radio and/or Wifi information
- Possibly something you ask me to!
I would love to cover topics that you
want to hear about. Please let me know what you want to know more about (regarding computers, and preferably Windows) and I will try my best to answer your questions or explain how things work. Let me know either through the comments, contact me, or my email: firstname.lastname@example.org
I am in the process of moving from wordpress to a self-programmed ASP.NET site. Because of this, some things
don't work, but I will be fixing the issues as time goes on. unfortunately, there are no comments or contact
me, so if you have any questions or concerns, feel free to e-mail me directly
I have comments
working now, they are still being moderated but you can let me know what you think...
If you ever find your self having issues getting connected to a network, one of the more obscure but common causes may lie within the Microsoft "6to4" adapter devices. These are hidden devices that assist in connecting to networks that use both IPv4 and IPv6 addressing (at least from everything I have read and heard, although I have not yet found a definite answer on their true purpose). They seem to cause problems in some cases, and they can accumulate quite quickly in your Device Manager, causing potential problems while booting the machine and while trying to connect to a network.
Because I felt it would be kind of hypocritical to talk about switching to https in my post about Internet Security when my site didn't even support it, I have revamped the site to allow for the use of https if you so desire.
In the first article in this series, we examined the anatomy of a web request, where the data goes before it reaches the target server, and why this communication is usually insecure. In this article, I will describe how we can ensure that our communications are secure even with the number of places our data moves through, focusing on the "https://" protocol (Transport Layer Security). As in the past, I will try to keep things as simple as possible, although I do intend on writing a more in depth article about the specifics of certificate based authentication in the future, so look out for that.
The internet has become an integral part of many aspects of our lives, but most people have no idea (or desire to know) how it works, when it is secure, and when it is insecure. In this series of articles, I seek to address this issue by going over the many ways data can travel through the internet, the security of that data, and how to make sure that data is secure. I will try to keep everything as basic as possible, so do not assume that you will not understand this article if you only have a basic understanding of computers.
It seems that anything that you do on a computer can give you a piece of malware. Click on a link on facebook...malware. Open the wrong search result...malware. At least that's how it seems if your job consists of removing malware from computers. The volume of malicious software that manages to infect the average user's machine should mean that it is fairly easy to get a hold of some samples of malware yourself, right? Well, let me issue you a challenge: open up your new virtual machine (I hope you have a snapshot taken) and try to find some malware to get infected with.
In our first post we covered the basics of setting up a VirtualBox Virtual Machine with snapshots configured to remove the need to reformat the computer every time you want to undo a change. In this next post I'll go over the basics of setting up a "Shared Folder" so that you can share files between your physical computer and the Guest Virtual Machine.
For many computer users, identifying and removing malicious software (malware) is something that they consider to be too complex or out of reach. Furthermore, actually practicing removal techniques can be difficult unless you have a spare computer that you don't mind reformatting over and over just to test out a new malware program. With the advent of virtualization software and free tools, these problems are a thing of the past.