I’ve been MIA since Monday morning trying to solve a crisis with my home office network servers. Of course, being the tech idiot and geek that I am, I run my own Microsoft Exchanger Server and maintain a domain controller, yadda yadda yadda. What happened Monday morning? Well, I got a new MacBook Pro. Cause for celebration, yeah? I started by trying to setup Active Directory services on the new computer, and me, being the tech idiot and unnecessarily rushing the process while looking after my daughter, inadvertently specified my domain controller’s computer name as the MacBook Pro’s name when I added the the new computer to the domain. Well, SHEEEEAT! All hell broke loose with Active Directory–so much that Active Directory’s DNS zones registered the MacBook Pro’s IP as the IP for the lookup of my domain controller, and I only have one primary DNS service running on my network. I have a secondary DNS, but that doesn’t allow me change jack, and that secondary DNS is running Windows 2000 Server, not Windows Server 2003.

It’s now Wednesday and every tech note I could find on Microsoft won’t help me get rid of the error messages I’m seeing on my poor domain controller. Luckily, I have an older domain controller that’s been offline for the last eight months, but I don’t make many changes to Active Directory, so rolling back to that data shouldn’t be a problem. BUT, and here’s the huge but, that machine has been on the fritz, not completing boot cycles, hanging randomly, etc. So, I cloned that machine’s hard drive to some a new drive and put it in a Pentium 4 box and ran the Windows Server 2003 install CD and performed a repair. So far, everything looks intact, but I haven’t rebooted the monster domain controller that’s run amuck yet. All e-mail @theMakers.com is down at the moment, and I’m hoping to have it resolved tonight.

BTW, I should mention that I did have backups on the monster domain controller, but the last backup was CORRUPT! The damn BKF file couldn’t be read by NTBACKUP and the most valuable information there–System State–could not be extracted “as is” by all of these damn popular BKF repair utilities. Those are great if you need to recover documents, but system recovery? FORGET IT!

As if getting taxes done this year wasn’t enough (doing the books for [theMAKERS], etc.), I’ve had the misfortune of two different drives heading south. The first one was a Western Digital 500GB My Book USB/Firewire edition, and the second one was an internal Toshiba 80GB laptop drive–at least three years old if not five!–that I had in a USB enclosure. I don’t know exactly what went wrong with the former drive, but it failed to mount on my Windows XP Media Center. I was able to run chkdsk and I thought all was well, but I wasn’t able to copy files from the drive without errors, and the system would hang/lock up for long periods of time while trying to access the drive. I took the drive out of the Western Digital enclosure (not easy! no screws… had to google that one), and used my nifty newertech USB 2.0 Universal Drive Adapter to connect the SATA internal drive to various systems. I’m still in the process of using Stellar Phoenix Windows Data Recovery software (about $100) to recover the files. Many of the files have been recovered without errors, but it’s a painfully long and slow process–I’m still not finished after a week or so of running the software. I hope the drive continues to “hang in there” while the recovery process is running.

The latter drive–remember the internal 80GB laptop HD I mentioned?–is doing much better with respect to recovery. I discovered that if I kept the drive in a vertical upright position that it could read much better. The crazy noises it was making stopped when I held the drive upright! (And, btw, it’s not in any enclosure anymore–there’s no fan or anything like that inside of the drive, and I imagine it’s the heads of the drive making the noise.) So, I have it affixed flat against the side of my new el-cheapo Dell Inspiron 530 desktop tower during the copy process. Seems to working great so far, and I’m nearly done recovering every file from it.