Diary of a Network Geek

So, you want to build your own Linux server for home?

Okay, you’ve seen me write about it and many of you think it’s too geeky to do on your own, but I swear to you, it’s not. In fact, here is a list of easy howto sites:

Who needs Windows Home Server with Linux around?
Linux Home Server HowTo at LinuxQuestions.org
Build It: Linux Home Server
The Australian Linux HowTo

And maybe, just maybe, when I finally get around to doing this on my home network, I’ll write up some documentation on how to do it. Or, at least, how I did it.

I’m sure most of the hardcore WordPress people have seen this already.
But, for the few of you who haven’t, check out the downloadable WordPress Theme Generator. Please note, though, that it will only install on Windows XP or above.

Why you should always change default passwords…

I don’t always agree with the bloggers over at TechRepublic when they insist that they have the five or ten most important links on a subject, but, every once in a while, they get one that’s really good. I can’t say much about most of the links in Chad Perrin’s post, Five must-have security resources, but his link to the RedOracle Default Password list is great! They have default passwords for just about everything there and, while that might not mean much to all my readers, if you have to do an emergency reconfiguration on something and take it back to the manufacturer default, having that password can really simplify your life.

Also, since these are so well documented, it’s a good illustration of why the first thing you should do after configuring, or reconfiguring, something is to change the default password.

Trying to get back to basics.

So, as many of my long-time readers know, I used to write. Well, I used to write fiction. Oh, okay, I used to write a lot more fiction. But, I get distracted easily. Apparently, so do a lot of writers. It’s very easy for me to get obsessed with formats and customizing displays and so on. More so when I’m having trouble with plots. Or endings. Or, most often, beginnings.

So, when I saw an article on 43 Folders about Scrivener and other simple writing tools for OS X. Sadly, everything he talked about was for Mac only, but he linked to a Slate article on the same subject titled In search of the distraction-free computer desktop, which had a few more options.
Now, I’ve read more books and articles about writing and the writing trade than I care to admit, so I’ve seen a lot of information about different writer’s writing environments and choices. Steven Brust, who writes top-notch fantasy, uses Emacs and macros to export that to Word format to send to publishers. I tend to use OpenOffice Writer, because I can use it on any platform I might find myself and my backup laptop is running Linux. But, the articles talked about several options that I haven’t looked into yet.

One that seemed very popular is called Scrivener, but, sadly, it’s only available for OS X. Another was called WriteRoom and it has a “clone” for Windows called DarkRoom. I liked the look of DarkRoom because it was, well, simple and clean and I’ve just about convinced myself that’s what I need. A simple, clean interface with minimal distraction so that I can get to the business of writing. Finally, there was a Windows-only program called RoughDraft that one of the commenters suggested. It, too, has a clean, simple interface, though it looks more like a old-fashioned Windows file-manager than anything else. And, neither of those options truly addresses the fact that I really want to be able to write on my Linux laptop in a pinch with the same tools and configuration.
So, in the end, I’ll probably just stick with OpenOffice. Perhaps I can find a way to customize and simplify the interface on Writer to my liking. Surely, someone, somewhere, has done this and has a convenient HowTo. If not, maybe I’ll do that myself and write it up.

Then, of course, I’ll have to find another excuse not to write…

Advice from your Uncle Jim:
"Every experience that involves one of us, involves others who also need what the experience may teach. We are not alone, ever."

I don’t think I’ve mentioned this before.

Some time ago, I was having problems with traffic on my network. Something, somewhere was apparently causing some issues with bandwidth on our Internet connection. Or, at least, that’s what our ISP kept telling us. It was, I think, the excuse they were using to avoid dealing with an e-mail problem.
Regardless, I had to find a tool to monitor our network traffic. I ended up using Wireshark for that, but along the way, I discovered a number of OpenSource monitoring tools for various purposes. The one that impressed me the most was Nagios.

Nagios is, according to the opening paragraph on their website, “an Open Source host, service and network monitoring program.” While I never did configure anything to monitor the network, per se, I did configure this to watch both local servers and third-party web and mail servers.
First of all, it’s important to know that Nagios runs on Linux. So, to install the software, you first have to have an available Linux server on which to install it. I’m using an old workstation that I installed the latest version of Fedora, the free version of RedHat. Getting the initial install done wasn’t very hard at all. In fact, there were RPMs available, so all I had to do was use RedHat’s package manager to get the base install loaded on the machine.

After the initial software load, I mainly followed the Quick Install instructions that they link to on the first page. Then, since I was mainly monitoring Windows servers and workstations, I found the cleverly titled help page, “Monitoring Windows Machines“, and followed that. This page ran me through the basics of installing the NSClient++ on a Windows machine and configuring Nagios to connect to and monitor that client. One thing that I had to find out the hard way was that the entries for the monitored systems have to be duplicated for each host. In other words, there is no way to just list all the Windows systems you want to monitor. You have to created entries describing each host individually. That’s not a big deal, honestly, since you can open the configuration files in a text editor and just copy, paste and edit the required entries.
I did have a few false starts here, until I figured out the correct syntax and the fact that every host has to be part of a previously defined group. But, other than that little glitch, configuration was fairly simple.

It took a little more digging, but I later found instructions for passively monitoring services running on servers without a client. I now use my private installation of Nagios to monitor our company webserver, both POP3 and SMTP on our hosted e-mail server, as well as my two Windows 2003 servers. I can even check on the Microsoft SQL database, thanks to information I got from this post on the OSdir mailarchive. And, did I mention that all this software was free? Yeah, the documentation wasn’t the best and it took me a little while to figure out the install and config, but it was far easier than the other monitoring software I played with and I can let anyone who has the username and password check these stats from their own workstation via a web browser. How cool is that? Oh, and did I mention that this can be used to monitor Linux/Unix systems, Windows systems and even Netware systems? Nagios pretty well covers it all!
(Oh, and as a side note, if you’re messing around with the configuration and want to reset the statistics, just stop the service and delete /usr/local/nagios/var/status.dat, then restart the service. All your counts will zero and all the checks will start fresh.)
In short, if you’re looking for a low-cost but versatile monitoring system and aren’t afraid to read the documentation, I highly recommend investigating Nagios.

So, I figured it was about time for another hardcore geek post.

I’ve been using the Linux-based imaging solution that I detailed here and here for quite a few weeks now. Mostly, it’s been going very well.
Okay, once I figured out it was better to start with a small drive partition as my base system, from which I created the standard image, the process got easier. The thing is, it’s always easier to start with a small partition and then use tools built into the Knoppix live cd to grow the partition larger than to try and shoe-horn a big disk partition onto a small disk. And, by “easier”, I mean it’s the only way to do it. I spent quite a bit of time trying to make it work the other way, but I never did. On the other hand, starting with an image based on a 30 gigabyte or less partition then expanding it to fit a 150 gigabyte hard drive has worked just fine.
Incidentally, I used a bootable gparted cd to make that change.

Also, I had a small problem with a particular Intel motherboard chipset. Specifically, it was the Intel 965 chipset, and the problem may effect other motherboards. In short, the problem was that Knoppix didn’t see the SATA drive to mount it. If Knoppix can’t see the drive, it can’t image it or take an image from it. Luckily, there is a work around. If you’re using my method to image WindowsXP machines running the Intel 965 chipset, ensure the BIOS is set to AHCI. To do that, get into your system’s BIOS and go to Advanced > Drive configuration > Configure SATA as AHCI. Then, when booting into Knoppix, hit F2 and use the following command-line to boot:
knoppix 2 all-generic-ide pci=nommconf
This will start Knoppix in text-only mode, so you can run everything from there instead of opening up a terminal session.
After you put the image on the fresh machine, you need to ensure the BIOS is NO LONGER set to AHCI. To do that, get back into your system’s BIOS and go to Advanced > Drive configuration > Configure SATA as IDE. After reconfiguring the BIOS, you can boot into the new Windows XP clone and proceed as I’ve already described in the other posts.

Oh, one last thing on this…
I kind of cheated on reimaging machines in text mode with that Intel 965 chipset.  Because the tools I used to resize NTFS disk partitions were all GUI based and XWindows was having a problem running on those Intel 965 boards, I installed one machine from scratch and just grabbed the larger partition table and master boot record.  Then, when I made the new machines, I just used the larger partition and MBR images to get everything out of the disk.  I still used the smaller data disk partition images, but I used NTFSResize to expand the NTFS partition to fill the disk.  Worked like a charm.

Anyway, I apologize to my non-geek readers, but, hey, I am a professional network geek and I love this stuff.  I think I strutted around for a full five minutes after figuring out that set of little tricks the same afternoon.  Of course, it wasn’t long before some other stupid thing brought me right back to reality, but that couple of minutes where I was the king of the world, network geek genius extraordinaire, made it all worthwhile.

Free government guidelines.

When it comes to computer security, the National Security Agency is the shiznit. Or, at least they were. I think they’ve sort of fallen behind a bit, as government agencies tend to do.

In any case, they have a whole website of government-level guidelines on computer security that you can download for free. So, even if they’re not the cutting edge any more, they’re still good guides and free.

Simpler is always better.

As far as I’m concerned, the simpler things are, the better. My life gets complicated enough all on its own without me getting in the way and making things worse. As an example, within the same five years, I was out of work for one year, got divorced and survived cancer. I’m almost afraid to find out what God might throw at me next.
In any case, one of the more complicated things I’ve done over the years is manage remote users. Under the best of circumstances, it can be a real challenge. When you consider all the ways to do it and all the tools that exist to serve these folks, well, things can get out of hand pretty quickly.

So, you can bet I perked up when I saw this article over at TechRepublic: 6 Technologies to Enhance Mobile Workers and Take the Pain Out of Managing Them. I’m not sure I agree with all their choices, or how much pain some of them take out of remote user management, but it’s an interesting place to start.

I got a kind of Christmas bonus Friday.

So, Friday, after long resisting it, I finally cleaned up my office.
I had all kinds of junk there, most of which I threw out. But, there was this older iMac. It was in decent shape, outside of a temperamental wireless card. So, rather than get rid of it, I asked the boss if I could have it. Mac lover that he is, he was thrilled to give it to someone who’d appreciate it. And, I think maybe he thought he’d converted me to the Apple camp. He hadn’t, but now I have two versions of desktop Windows, Linux and OS X in my house. Not to mention Novell and Linux server systems. So, now, when someone asks me to convert files for them, format shouldn’t be an issue.

Now, that is what I call a Christmas bonus!

My laptop saved me.

As most of my regular readers know, my laptop really saved me when I was in the hospital getting my chemotherapy treatment. If I hadn’t had that, I might have just about gone crazy. For one thing, it kept me in touch with many of my friends via e-mail and blogs. For another thing, I was able to get some things done at work via that laptop and a secure, remote connection to our server. That wasn’t my intention when I bought it, but, still, it’s been a very good investment and I’m very, very happy to have made it. I’d even say it was worth going into a bit of debt to get it when I did. It was something I’d put off doing for… Well, for a very long time.

Anyway, if you’re thinking about getting a laptop, the upcoming Christmas season is as good a time as any. These days laptops go on sale just like all electronics do, at Christmas, after Christmas and at the beginning of the school year. But, with deference to the TechRepublic article from which I drew the main points, here are ten things to keep in mind when buying a new laptop:

#1: Operating system

#2: CPU#3: RAM

#4: Video card

#5: Ports

#6: Screen size

#7: Integrated wireless

#8: Integrated Bluetooth

#9: Track pad

#10: Battery life

So, if you’re taking advantage of the great sales at the last minute, keep that in mind.  And, if you’re in the market for a laptop, Microcenter is going to have some pretty great sales just after Christmas this year, it looks like.  They’ve always done right by me.
That’s NOT a paid endorsement, by the way.  They’ve just always done right by me.