Diary of a Network Geek

They’ve been waiting for me.
I can tell that the folks at my company have been waiting for a guy like me to show up. Today, I had three different persona PCs from three different employees in my cube. Mind, I mean three machines that they brought from home to have me look at for them, not machines from the office. Mostly, they just needed to be defragged and have their anti-virus files updated, but, c’mon, three? Obviously, these people have just been waiting for a “real” computer person to show up so that they can get me to do basic maintenance for them. Actually, come to think of it, I need to update my anti-virus signatures myself!
But, that doesn’t mean I have any less work that’s work related, either. Just this morning I was setting up a PC for yet another person from New Orleans. Which is a good thing, I guess, when you consider some of the alternatives. Of course, it would have been nice if they hadn’t promised that same cube to two different people without telling anyone. I was about to try and move his e-mail from the Windows 2000 machine he had in the office to his G4 Powerbook, but then we decided to take a “wait-and-see” stance instead. With all the miscommunication flying back and forth, we thought that was better. The chaos from Katrina has everyone sort of “runnin’ and gunnin'”, if you take my meaning, and that makes things extra challenging sometimes.
So, with all this craziness going on at the office, I find myself asking, “Should I be doing all this for people?” I mean, it’s not really my job, but the folks asking me to do this for them are the top-level managers. Should I be telling them “no”? I’d really rather not do that, since everyone seems to like me and the work I do for them. Granted, I’m not sure that most of them have any idea what I actually do on a day-to-day basis, but still, they seem pleased, so I’d rather not rock the boat.
Oh, and in recent updates, I did finally manage to get the satellite phone working, but now, since it took so long, we’re trying to return one. Not sure if we can do that at this point, but we’re trying. And, I’ve been messing around with all kinds of Windows 2000, NT and XP issues on the network. Getting all the folks from both offices working has been a bit of a challenge. In fact, if not for the DMZ port on my firewall, I’m not sure I could have had the two domains working together, since they’re named the same. I’m sure that would have caused problems if they’d seen each other on the network.
And, I really should be looking more closely at the version of Linux I want to run on that mythical server that I should be getting spec on. I’m leaning toward either Red Hat or SuSE, possibly even SuSE with all the Novell Open Enterprise Server stuff on it. I have to admit, if I were to get good install media, that could be really cool. All the stability and flexibility of Linux with the way cool administration tools from Novell. Those tools are, after all, what they’re known for developing. It’s the best “value added” product for Linux that I’ve seen so far.
Well, I guess I have some time before we’re really ready to do all that, so, while I wait, I’ll probably just read Sams Teach Yourself UNIX System Administration in 24 Hours, so that my skills are sharp when the time comes. But, now, I’m tired, so I think I’ll just go to bed.

Yes, gentle readers, wardriving is alive and well and living in New Orleans.
At least, that’s what the folks over at BoingBoing claim in this entry/article. Honestly, though, in many places, wouldn’t it be warboating? And, yes, I found myself wondering as I skimmed the article, just how many live wifi hotspots there were running along all happy and unknown as power gets restored to parts of the city that were either relatively unscathed or have cleaned up quickly and well.
I really think it’s neat that there’s someone out there doing this. I mean, think about all the search and rescue teams, or police, or FEMA officials, or whatever that could use some kind of connection out there. I really think this is where something like wifi can shine. This kind of disasterous situation is just the right time for open access all over the city with little to no restrictions. But, without knowing where the hotspots are, they can’t be used.
I really hope this is helping, though, and not just a couple of geeks grabbing headlines for the “fun” of it, or under the guise of “citizen journalism”.
Either way, it’s an interesting article.

Do you have one?
Why not? In my case, it’s because I just started at this company, but I really should have gotten on this ASAP when hurricane season started. We got lucky. Everyone got out and we were able to get all our essential equipment (ie. server and associated drives) out of our New Orleans office. But, what if we hadn’t been?
I was thinking about that a lot as I ran around Thursday and Friday trying to quickly, with little notice, cobble together a network for the folks from NOLA to use. At least they’re able to bill, so we have some income and can keep some of the folks from over there employed. Not sure how long we can maintain that, but at least it’s something. I actually made them their own, isolated network with their own hub. (Yes, “hub”, not “switch”. I didn’t have any spares laying around!) We had to buy a printer and wait until some of the equipment came over from New Orleans to test everything, but I did get them working. It’s a bit of a mess, too, with cables hanging all over the three cubes that they’ve occupied, but it’s better than nothing. This way, we can keep at least some of the people who made it through employed.
It’s a little sickening to me when I think of it, but this disaster is going to make my company a lot of money. There are all kinds of things out in the Gulf that need to be repaired and, frankly, to get the oil flowing again, price isn’t much of an object. I hope we keep it from getting too out of control, though. I’m all for making money, but I’d hate to see gouging going on.
Oh, and our Iridium phones came in, though there were some parts missing. Still I managed to get them charged up and teach the two guys who needed to know, how to use them. It’s amazing to me how small they are. Not really any bigger than the old-style cell phones. The antenna, however, is gianormous! Need to do funky stuff to call to and from these bad boys, too, but I got dialing instructions off the Iridium website. All in all, very cool. Now, if we could just get past the “Emergency Calls Only” message, we’d really have something!

You know, I’m getting invaluable experience here, but I’d really rather not. I’d rather this never happened. This is going to mess up the local economy for years and years, not to mention the national economy. This disaster shut down the busiest seaport in the United States. That impact will be felt for a very long time, all over the world.
If you’re the kind that prays, now would be a good time.

Well, I survived the daytrip to New Orleans.
Barely. Not that the flight was bad, because my boss is actually an excellent pilot and the weather was good. In fact, it was better than most commercial flights I’ve taken, except for the fact that I felt like I couldn’t take a nap. I learned a long time ago to work hard while I was on-site and sleep on the plane.
No, the problem was the “little” problem I thought I was going to fix. See, what I thought was a little problem with some spam e-mail turned into virus hell. Of course, I prepared for that and I brought a copy of our Symantec Corporate Anti-Virus to install. No problem, right? Wrong. When I installed it an old version of Norton Anti-Virus was still installed and the resulting conflict led to the dreaded Blue Screen of Death on the server. Not good. So, I finally get that worked out and discover that the machines are all in a workgroup. None of them sign into the Domain on the server. That meant going from machine to machine and installing the anti-virus program by hand on each one, which, of course, I did. All day long, until about 6:00pm when a break in the weather sent us scooting home.
We got in about 8:30pm, which got me to my door at about 9:15pm, or so to find a puppy with her little legs crossed! I sent a friend who has a key, in case of emergencies, over to let her out, but she was afraid of him and wouldn’t do anything. Silly dog. Just like always, she’s daddy’s girl and wouldn’t do anything for anyone but him. Gotta’ admire that loyalty, even if it’s a little co-dependant.

Advice from your Uncle Jim:
"Whatever the majority of people is doing, under any given circumstances, if you do the exact opposite, you will probably never make another mistake as long as you live."
   --Earl Nightingale

Actually, I think it’s a prop plane, but, you get the idea.
Well, the boss told me we’re off to the New Orleans office tomorrow to work out some of their computer issues. Mainly, it seems like they need to get their anti-virus software automatic update more, er, automated. And, of course, they need to get all their machines cleaned of spyware. And, while I’m there, I’ll do a bit of inventory. Since they seem to have a Windows 2000 server, I have a script that claims it will gather all the information on all the machines in the domain. We’ll see. If it works, I’ll post about that tomorrow.
So, it’s off to bed with me, since it’s an early morning tomorrow flying with the boss. Oh, didn’t I mention? The boss has his own plane. I’ll be flying in a single-engine prop plane and my boss is the pilot.
Pray for me.

Advice from your Uncle Jim:
"A pessimist is one who makes difficulties of his opportunities; an optimist is one who makes opportunities of his difficulties."
   --Reginald B. Mansell

The Patron Saint of Geeks?

Well, according to this article on Wired, maybe so! Of course, that depends on whether or not he’s really a saint at all, but, it sounds good.
Apparently, there are quite a few urban legends surrounding this Saint, but he’s still revered by hackers and other computer consultants. At least, he is in New Orleans. And, according to the testimony in the article, praying to him works! At least one person claims to have gotten a tech job fast after praying to good, old Saint Expedite.

Well, it can’t hurt, can it?

Well, it looks like I’ll be a Road Warrior again.

At least, to a lesser degree. I got word this week that I’ll be doing some travelling for Loomis Fargo & Co. It’s nothing real complicated, just a PC upgrade, but they’ve got a deadline of September 15. Frankly, that deadline is somewhat artificial, but, still, it’s good motivation to get everything done.
I’ll be going to the Chicago area first, later this month, then I’ll be back off to New Orleans in September. I have to admit, it will be nice to see Mom and Dad back in Chicago for dinner at least once while I’m there. And, I’ve never actually stayed in New Orleans, just the airport, so I’m looking forward to that, too. Maybe I’ll finally get my “voodoo rattle” that I’ve been joking about since I got into IT!
In any case, I don’t really like business travel, but at least I’m going to major cities. And, of course, I’ll get paid fairly well for my trouble because I’m still a contractor, so I punch a clock. Anyhow, you can bet you’ll see entries about being on, and from, the road.
Stay tuned!

Well, it sure has been a long time since I did any updates on this page! In fact, it’s been literally months!! I can explain…

First off, I’ve been pretty damn busy at work. After my little adventure in the New Orleans airport, I hardly had a chance to sit down. Not only have I had to roll out two sets of patches, or “Service Packs” as they’re called now, on our Novell servers, but I’ve had to set up a Novell BorderManager Proxy server. Man, the troubles I’ve had with that! The initial setup was okay, but getting the VPN (Virtual Private Network) working has really bedeviled me. It’s been so bad that my boss, the CIO, had to raise some ruckus with our sales reps at Novell. He’s finally gotten me a connection with our local Support Engineer, who’s promised to come take a look at our configuration for me. Hopefully, he can find what a CNE (Certified Novell Engineer) with more than eight years experience has missed.
Second of all, I finally got my gorgeous girlfriend/fiancé to marry me. On Saturday, March 10th, 2001, Anne and I got married in the Canterbury Wedding Chapel at the Excalibur Hotel in Las Vegas, Nevada. Allie, Anne’s daughter, was our ring-bearer/flower-girl. The service was nice, short and attended by the photographer. We thought it was the perfect way to get married. No one hassling us or telling us what to do and how to do it. No meddling mothers or aunts or sisters to make us miserable. No seating charts or receptions to worry about planning. Just a cool, quick wedding and a great steak dinner afterward. After that, we spent most of the week running around Las Vegas doing tourist stuff. We went to see Sigfried & Roy, Tournament of Kings and The Blue Man Group. We also went to see Star Trek:The Experience, where I bought “genuine” Romulan Ale and Klingon Blood Wine. But, of course, work intervened and I had to come back a day early to “fix” something that had gone wrong. What would they do if I ever quit?
Finally, now that we’ve done all that, we’ve been looking for houses. It looks like we found a nice four-bedroom, two-bath, two-story house on a lot that’s almost double-deep! And, even with all the flooding that we’ve had here in Houston, it stayed dry. What could be better?!? Two koi-ponds, that’s what. That’s right, the property already has two koi ponds on it, complete with koi. There’s a fireplace with a Ben Franklin stove in it and a partially finished garage. There’s a covered car port that’s connected to the house by a covered walkway. It’s really great and I hope the sale goes through okay. We’re scheduled to close this Friday, 6/29/2001!
And, of course, I’d be remiss if I didn’t mention my kidney stone. That’s right, as if all the work I’ve been doing isn’t enough, I was doubled over in pain by a kidney stone last week Monday, 6/22/2001. It got so bad, that I had Anne take me to the emergency room. We ran into Charles, our paramedic friend, there who told the nurses to take good care of me, which they did. I got moved through as fast as I’ve ever been. And a nice, young doctor gave me some great pain medication. I still haven’t passed the damn thing, but I’m off to see the friendly urologist tomorrow. I plan on demanding that he “do something” about it because I’m tired of peeing through a strainer!
Until next time….

On a *really* positive note, the nightshift police took a real interest in my Palm and my folding keyboard. They were totally amazed at my typing into such a tiny device. Hey, at least they kept me company for a few minutes. I think I’ll ask them about vending machines and then go back and play some Area 51 in the video arcade. At least there’s that to do while I wait. Afterward, maybe I’ll take a nap. (As if that could happen with the noisy cleaning crew!) I wonder what they serve for breakfast in the airport?

Here I sit, at 12:25am, in the lobby of the New Orleans airport waiting until 6:00am so I can go home. “Why?”, you ask. Well, I’ll tell you. If for no other reason than to look busy so that the nice police officers stop looking at me like I’m some kind of vagrant. It all started a couple of weeks ago, when I noticed that the chuckle-head who was the Network Admin before me had not gotten all the servers onto the latest set of service packs. When I asked my boss about this, he was somewhat surprised, since he’d been told that everything was up to date. Not hardly. In fact, I had servers that went back at least two revisions! So, two weeks ago I prepared to get all the servers updated. Behold, my true troubles begin! I try to get the patches copied to all the servers and discover that it takes literally *days* to copy the files! That’s right, the patches are so big, and our bandwidth is so small, that it takes almost five days to copy the Novell patches to all the servers. But, wait! They didn’t really copy to all the servers!! Yikes! So, the re-copying begins. Now, this is when it starts to get really fun. You see, in most of the cases, the reason the Novell Service Pack didn’t copy, is because there just wasn’t enough room on the main volume. (That’s SYS: for all you Novell CNEs out there. Not that there’s many of us left. Certified Netware Engineers are a dying breed, I’m afraid.) Well, I try the obvious solution and recopy everything to one of the other volumes (that’s a “disk drive” to you non-network engineer geeks.) At first, that seems to work well, but, on closer examination, I discover that one of the servers has still refused to copy everything. It turns out that this server lost it’s wide area network connection. *sigh*
Okay, so I try copying the patches yet again, but this time I send them in a compressed format. So far, so good. While all that copying was going on, I started installing the patches on the other servers. Again, most of them worked just fine, but those few with teeny, tiny SYS: volumes don’t all work. So, at this point, I’ve ended up with four that don’t quite have enough room on the main volume to install patches and one that finally has the patches *copied* , but not installed. This is where the problems that actually led me to the New Orleans airport began. We recently purchased a nifty utility called ServerMagic from PowerQuest. This darn program is the best thing since sliced bread! Among other things, it lets you resize Netware volumes without having to destroy them first! Totally cool, and totally impossible before this tool. So, never having used this before, I installed it on one of the remote servers. I ran it and it asks to reboot the server. (GULP!) I took a deep breath and tell the program, “okay”. Bang! The server goes away. Poof! It never comes back up. *sigh* Well, that was just the beginning. I let my boss know what was going on, and then we sat back to wait for Monday morning when that office discovered their crashed server. In the meantime, of course, I installed the patches on the rest of the servers. Or, at least, I *tried*. Some of these servers **still** didn’t have enough room to install all the patches!! Well, I figured that I’d eventually get the space problem worked out, and just left it alone. Oh, boy, was that a mistake! Monday, the first office called to get the server up and running. We got the first signs of life about 9:30am, with some errors, of course. About then, that office’s answering service lets them know that I know about the server and that they should call me. *sigh* So, okay, we get this pretty well squared away, when the development department tells me about this new, totally redesigned piece of misson-critical software that *I* need to get rolled out. Being the kind of guy I am, I start getting this all configured to run, from scratch. Now, we’ve survived until Tuesday morning without a tragedy.
Well, about the time that I start to work on finishing the big, new, shiny software rollout, another site calls to tell me that their server is down. “How did that happen?”, I wonder. No time to worry about that, though, because we’ve got two whole companies down while this one fileserver is off-line. So, like I always do, I started trying to figure out what happened so that I can undo it. It turns out that they took it upon themselves to reboot the server because there were users having problems logging in. Aha! The new patches had partially loaded, because they were partially installed, and some of the new files didn’t like some of the old files. Blamo! One crashed fileserver. Well, I banged away at it for most of the afternoon, one way or another. I tried loading files from backup directories, and copying files from the backup directories, neither of which worked. Then I tried to use ServerMagic to resize volumes so that I could come up with the extra space I needed to install the patches. Well, that *almost* worked. Apparently, the old disk drive just couldn’t quite handle the new utility and just decided to stop working.
By this time, it’s after 4:30pm and I’ve already figured out that I’m flying out to the remote site. Shortly after I suppose I’m going, my boss confirms it for me. We agree to try a couple more things, but not past 5:30pm. So, now, it’s do-or-die time. Let’s just say that I didn’t “do”. My boss helps me get the travel arranged, and we decide that a day trip should be enough. I gather my tools together and scare up a 4Gig external drive that I can add on to the ailing server. Then, I got the brilliant idea to burn a CD-ROM that has the patches on it. After all, since I have to add diskspace anyway, I might as well install the patches while I’m there! That was easier said than done. *sigh* I finally downloaded the required files to my PC and used my own CDR to make what I needed. It took over 6 hours to get the complete download. I got out of the house with just enough time to make the first flight from IAH to OLY. That’s at 6:50am, just in case you’re interested. It gets into New Orleans at about 7:00am. I then spent almost 45 minutes getting from the airport into my rental car. After that, I was ready to drive more than an hour to get to our site in Houma, which I finally did after a few wrong turns.
Finally, I was ready to start working on the server at about 10:30am. It took all of about 15 minutes to get the extra drive installed, configured and running. The fileserver itself took a little longer. I got enough of the new drive allocated to the SYS: volume and then I got the new patches installed from my CD. So far, so good. In fact, at this point was planning to try and catch an earlier flight home than the 5:20pm flight I was scheduled to fly back on. Oh, well, maybe next time. I rebooted the server, so that the new patches were activated, but started getting errors right away. Apparently, the USR volume, where most of the actual data existed, was damaged. Damn! So, I try every repair utility that I can think of, without any improvement. Eventually, we had to delete most of the data because it was too badly damaged to actually use. Unfortunately, that volume also stored the GroupWise e-mail system data. Whoops! So, now, it was about 2:00pm and I was wolfing down an oyster poboy while trying to get the USR volume back online, when it hit me to try and use ServerMagic to fix the problem. Well, that *almost* worked, but it recovered the drive at the expense of the data it contained. Double damn! We don’t back up the GroupWise data for legal reasons, so now we can’t restore it. But, wait! The local remote admin ran a backup last month that accidentally included the e-mail directories. Hooray!! Well, to shorten a *very* long story, we managed to recover and rebuild the mail databases so at least they’ll have user accounts and mail going back a couple of weeks. Not ideal, but better than nothing.
But, how did I end up missing my flight? Well, to prove that we give the best customer service, I stayed while the Arcserve restores ran. (Okay, it was more like they ran, then got totally screwed up, then we deleted them and recreated the jobs and *then* they ran.) And, the next thing you know, it’s 9:30pm and I’m running to try and make a 10:30pm flight. Obviously, I missed it. *sigh* On a more positive note, I do have a flight booked for 6:00am. Of course, that means that I’ll have just enough time to shower and change before I head back into work so that I can get the super-duper software rollout working. Blech! I plan to get the most out of the damn company picnic on Sunday!