When the IT Hits the Fan-02.24.15

So, yeah I was right. Welcome to my life.

Tuesday, 02/24/15. Yeah ok, just a normal day. If your day happens to consist of dealing with Demonically Possessed Network Copiers and Printers.

Apparently we are the proud owners of a fussy, Prima-Donna Konica Bizhub copier. I get a call from our Documentation department. Apparently Tray 3 wasn’t working. So I pull the tray, check things out. No jams, no stuck roller, absolutely nothing wrong. On the screen is simply said “Tray 3 is unavailable currently”.

What the hell?! Is it on a fucking smoke break! Like, “No, I’m just not feeling it today. I’ll be in my trailer.”

Turned it off and back on and suddenly it was fine. No indication at all as to why it just didn’t feel like working.

I hate printers. And copiers.

Next up, right as I was going back to my desk from arguing with a bitchy copier, I get one of our staff at my desk.
Oh, look. It’s a problem with the Staff HP Laserjet 4250 printer!

Did I mention already that I hate printers?

He shows me the pages that he printed out. They look like several print jobs had over-layed themselves all onto a single page. There was multiple different documents obvious on the printed papers and they weren’t even all his.

So, I go down and check out the printer. Print out a couple test pages and configuration pages. Everything looks fine. I have the staffer print again. It prints just fine!

Ok, so apparently the printer missed it’s dose of Prozac or something! Seriously, I fucking hate printers!

Next up in Rigsby’s 3-Ring Circus for Tuesday.

One of our Program Managers has a customer who is supposedly putting some critical documents for an order onto our FTP site. Now, mind you, this customer is a major name in the Enterprise Infrastructure equipment industry. They design cutting edge, seriously expensive network security equipment. In theory they should probably know how to use FTP since it’s older than Dinosaur farts. There must be something wrong with our FTP!

Nope, I test their account and I double-check my test to see that the document I used for testing is sitting in their FTP folder on our server. Worked great.

So, I send our PM their credentials again, along with very clear, concise instructions on how to use the Windows File browser to connect, since that’s more stable and universal than needing to describe to them how to access through an internet browser.

Still no luck. They then email me a print screen of their screen showing all of the files that they insist were uploaded to our FTP site.

The email said “Please look for this folder <folder name>” and on their screen was very clearly the folder, showing all of the files in question, and the path to where this folder was located.

The folder is in C:\Users\<persons name>\Documents\<folder name>


Again, C:!!!

For the non-geek out there, C: is the hard drive letter for the computer you’re sitting at!

In other words, this employee for a company that manufacturing networking equipment was dropping the files into a folder in his drive and wondering why it was that we didn’t see them!!!


When the IT Hits the Fan-02.23.15

When the IT Hits the Fan-02.23.15

Yeah, I think I’m in for an interesting week.

Monday,02/23/15 before I could even get my coffee, I get frantic calls from multiple people because a critical application/file server used by around 30 people wasn’t letting anyone remote in and their mapped drives to it weren’t connecting.

Walk into the Server Room and I immediately hear a beeping, which if you’re in this industry you’ll probably immediately cringe. Beeping is bad. Beeping from inside a Server Room is even worse.

Our old Dell PowerEdge 2850 Server that serves applications, tools, and shared profiles to our Test Department had a wonderful little message scrolling across ECC Unrecoverable Error. In non-geek speak that can mean either failed memory, a bad memory slot, or a completely failed motherboard. Guess which one ours was.

Yeah, after spending an hour swapping memory, one pair of sticks at a time, turning on the server, then turning back off and repeating, nothing worked. The motherboard was fried. The story does have a happy ending at least.

[Side Note: we’ve had another old, unused 2850 sitting in the server rack for a couple years now that I just couldn’t bring myself to scrap]

I ended up calling Dell’s Infrastructure Engineer department and found out that we could safely pull out the drives from the dead server and move them to the aforementioned unused server without any loss of data.

End of story here. After a couple hours of stress, cussing, and more stress, I was never so relieved to see an outdated copy of Windows Server coming up on the screen. Not so much as a hiccup to transfer. We got lucky.

Monday’s Second Adventure. We had gotten in some new Test equipment from a customer that is necessary for their products on Saturday and I got a call saying I needed to come out and get it on the network.



Yeah…………… Thankfully the Test Technician who called me is a fairly computer savvy smartass. He was kidding. The machinery is pre-HP UX operating system, which came out in 1982. The system is so old that it’s operating system controls consists of a hand-held box with nothing more than OnOffYes, and No buttons. That’s it.

I’m pretty sure it was built to be networked by a telegraph. Or maybe smoke signals.

I’m writing this on Tuesday and I’ve already had write up content that has made me want to beat my head against my desk, so I wonder what the rest of this day will bring for me to write about tomorrow.