So, as some of you may know, I have been working for a commercial printing company doing IT for about half a year now.  The company has been in the middle of a massive merge and building-consolidation process.  All-in-all, everything has gone quite well.  One server crashed, but everything was recovered from backups.  However, working in a small business during poor economic times means working with some painfully old devices.

Last week I was given a pretty simple task.  I needed to set up a networked label printer that had been moved from the old shop.  Easy enough, it should just grab an IP via DHCP, and I can log onto its web interface to set it up – no big deal.  I hooked up the printer and voila, 192.168.2.13.  It was set up.  Went into our router, changed the IP from dynamic to static, and headed out for the evening.  Seemed like everything had gone great.

Now fast forward to the next morning, the pressmen are just getting ready to pull the press data from the servers, and – oh crap.  The press computer is down.  This press prints out 16,000 sheets per hour, and each sheet has 2-3 pieces on it.  You can imagine how fast I got the phone call.  I went straight to the press when I got in to see an error about an IP Conflict.  Our presses are all assigned static IP’s, so I went in to the network config – the IP assigned was 192.168.2.13.  Sounds familiar.

Turns out this label printer (I won’t name the brand, but I can’t say I’m surprised by this faulty setup) does not quite understand the meaning of DHCP and IP conflicts.  When it booted up the BOOTP process assigned it any random IP, regardless of what else might be under that IP.  I quickly unplugged the printer, and the press came back online.  In the end, I hooked the printer up to a more manageable HP JetDirect, and avoided any more IP conflicts.

The ironic part of this story?

A desk label printer this small :                                                Shut down a printing press this large :

• Wegner Design
• How-to: Enable Surround Sound on Ubuntu Hardy

So what did I do instead? I got violent, because violence solves everything!  I banged my iPod against my shifter in my car three times and tired it again just to see if it worked, and by golly it turned on, no more sad face and my music was playing!**  I about shat my pants I was so excited!  Now granted, it froze up every once in a while and gave the sad iPod face again, but no worries, do the simple solution again and it works!  Now after about three years, it doesn’t freeze up anymore.  It may not work the first time, but keep trying and it will eventually.

After some investigation on to why this works, it turns out that in the older iPods there is a small connector cable that becomes loose from the hard drive through normal wear and tear.  You’re simply just knocking that cable back into place so the hard drive can be read properly.  I have had this same iPod for 5 years now, and it works wonderfully, and have not needed to buy a new one.  Nothing flashy with it either, it is the generation 4 iPod, right before it switched over to color and became more complicated.  Now, would I LIKE a new iPod? Sure, but I would only really want one if I didn’t purchase it, and it was atleast 20 gigs like the one I have now is.

So before you go out and spend a whole lot of cash on a new iPod because you think you’ve lost yours forever, try this and see if it works!  Any questions, comments, feel free to ask!

**Automaticable, Apple, and the poster are in no way liable or responsible for any and all damages caused to your iPod, Car, or self, or anything else when trying any and all “violent” techniques in hopes to remedy the sad iPod face from the MP3 player.  Reader and User try these techniques AT THEIR OWN RISK.

• On the Go: Syncing your Data
• Bring New Life to Your ipod: Go Old School

In layman’s terms– we’re back! If you are wondering what you missed, the list is below.

• Kyle wrote an article listing the Top 12 SOE Firefox Extensions. Check it out, it’s not just for SEO.
• He followed that up with a post regarding letters written to a journalist posing as a little boy from convicted serial killers.
• Kyle also joined Twitter. Let us know if you are on Twitter too!
• Following that was a review of the Iron Man movie that just came out.
• Brian opened the blinds right before finals began.
• Kyle announced his new SEO project revolving around Gibson guitars.
• Scott finished finals and is happier than a clam.
• And finally, Kyle reviewed the new Death Cab for Cutie album, Narrow Stairs.

So spend some time catching up. You know we missed you as much as you missed us!

• Review: Death Cab for Cutie – Narrow Stairs
• SEO Project- Review: Gibson Guitars

They’re in the midst of transferring services to Comcast, set to be complete sometime in April.  Everything was fine on our end until our internet went out a few days ago.  After a few hours of toying with it, I decided it had to be Comcast’s issue.  I tried rebooting the router, renewing the IP, and even connecting my computer directly to the modem– nothing worked.

Finally, I called Comcast and talked to one of their “specialists” from Indiana (better than India, right?).  He dialed into the modem, and was able to get a computer hooked up through the modem, but still not through the router.  We made an appointment to have somebody come out.

Two days later, somebody from Comcast came out and tinkered with things for about an hour.  With all of the toys in his magic bag, he still couldn’t get the router working.  Moreover, we were able to hook up a different router, and that one worked.  We chalked it up as a faulty router, and he was on his way.  But something was still fishy.

We bought the router about 5 months ago, and everything had been working on it perfectly.  I installed the DD-WRT firmwire for even more control.  Everything looked good on it, except we couldn’t get an IP from the modem.  After doing a little research, it seems that Comcast has some trouble with DD-WRT routers.  The solution was to change the router’s MAC address from the default DD-WRT address to something else.  Many users clone their laptop’s MAC, but I used one from an older router.  A quick reboot afterwards, and we’re back up.

It’s hard to say whether it’s an incompatibility issue, or Comcast is actively blocking this alternative firmware.  I’ve generally had bad experiences with Comcast, so I choose to believe the latter.  Anyway, I’m glad we got things worked out, because I wasn’t too excited about going through the warranty process with Linksys either.

• On the Go: Syncing your Data
• How-to: Mount a Network drive in Ubuntu

1. Open up the task manager by right clicking on the taskbar and selecting “Task Manager.”
2. Then, click on the “Perforance” tab, to confirm you’re having this issue. (It should look similar to the above screenshot.)
3. Next, select the “Processes” tab. Sort by CPU by clicking on the CPU column. The entries should have CPU entries in descending order.
4. The process at the top of the list is your culprit. You can do a Google search on the process name to find out what it is, and if it safe and easy to disable it.

In my particular experience, the rogue process was “bigfix.exe”. According to AuditMyPC.com,

BigFix.exe is a tool used to download support information from hardware manufacturers and software vendors. It will also perform checks over your system and try to locate configuration errors and security vulnerabilities. If you find that this process causes problems for your system, it should be terminated.

bigfix.exe is an application that does NOT appear to be a security risk

The Process Server database currently registers bigfix.exe to Bigfix.

So, it came down to a program that was installed with Windows, and running at startup. It was non-essential, so a simple uninstall of BigFix solved the problem.

• How-to: Enable Surround Sound on Ubuntu Hardy
• Organize Your ToDo List in Ubuntu with Remember The Milk and Tasque

• Comcast Blocking DD-WRT?
• A New Year, A New OS