One of the handier commandline tools for Windows XP troubleshooting is to blindly type “netsh int ip reset all” into the Start -> Run prompt. Here’s what it does, to my understanding:

• netsh: this is a Windows utility that allows one to display or change network settings locally or remotely. The first part of this command simply tells Windows which utility you wish to use; the rest of the command consists of arguments to this utility.
• int: this argument specifies that you wish to use the “interface” context within the netsh utility. An example of another context that could have been specified instead of “int” would be “winsock.”
• ip: this argument specifies that you wish to use the “ip” context within the “interface” context of netsh. An example of another context that could have been specified here instead would be “ipv6.”
• reset: this argument is an instruction within the previously-specified context and subcontext means what it says, to reset to default. An example of another instruction that could have been specified here would be “show.”
• all: this is an argument to the “reset” instruction. This should tell the “reset” instruction to set all of the settings in the “interface ip” context to default, but also specifies the file into which you would like a log of the “reset” instruction’s actions.

By resetting the Internet Protocol interface, a great many otherwise-mysterious problems can be made to disappear without complaint. Now we have a little better idea of what you’ve been telling your computer to do. Any additional light shed on such murky backwaters of Windows lore is always good, of course.

*Anecdotal evidence recommends a reboot after running this, though none should be strictly necessary.

Microsoft has officially released the minimum system requirements for the new Windows Vista operating system (formerly known as Longhorn). As we all know that minimum requirements aren’t worth the screenspace they occupy, here are the recommended system specs:

• 1 GHz 32-bit (x86) or 64-bit (x64) processor.
• 1 GB of system memory.
• A graphics processor that runs Windows Aero.
• 128 MB of graphics memory.
• 40 GB of hard drive capacity with 15 GB free space.
• DVD-ROM Drive.
• Audio output capability.
• Internet access capability.

For the love of God, please don’t try to cram this new system onto anything less. You’ll only cause yourself pain and misery, and earn the enmity of those who you seek help from.

Recently I’ve brought my own dedicated Linux server online, which has opened me up to a whole new world of technological problems that I had previously left to others to worry about. One of these problems is security. On November 29th, DYAD Security released an advisory regarding a exploit for the Webmin package. Happily, the Webmin folks were quick to patch it, releasing version 1.250 on November 30th. But what does one do if he has an older version? Upgrade.

Contrary to popular belief, the Linux intelligentsia are actually correct in their statements that it can be easy to set things up. Sometimes. To my surprise, this is one such instance:

Log into your webmin interface as root. By default this will put you into the Webmin category. Follow the link to “Webmin Configuration.”

In the Webmin Configuration page, follow the link to “Webmin Upgrade.”

You can be a Linux badass and upload your own copy of the RPM, or you could be a hardcore pencilneck and rebuild it from source. Personally, I clicked the “Upgrade Webmin” button.

Depending on the speed of your upstream connection, as well as the load on Webmin’s Sourceforge peers, it can take several minutes for the download to complete. The current version, 1.250, is only 9.02 megabytes in size (RPM version), but on the day or so after a bug-fix like this, don’t expect your 100Mbps connection to top off. The update runs itself all the way to completion by itself, and does not require you to restart anything manually.