The network is down.
I remember the day well, and you see I was working onside in Columbus Ohio. It was a roughly 2-hour drive from our house in Cincinnati and the project I was working on was in Columbus. A straight shot up I-71. Depending on what was happening at home I sometimes drove home, sometimes I stayed a hotel. I was the acting email administrator for the company, as their actual administrator had quit. They couldn’t find anyone with the skills they needed, so they asked me to step in. I said sure! It meant I had to spend many more nights in Columbus and was able to drive homeless often. Now you have the scenario. I was the customers’ email administrator.
But still working for the company I worked for.
We were sitting in the old IBM mainframe room. We sat in the tape library room.
The facilities and planning teams of the customer sat right outside that room, and they knew who I was and what I did.
I was working on an upgrade for the servers, the planning part when my phone started to ring.
I picked up the phone.
“Hello,” I said.
“Outlook is down.” The voice said and then hung up.
I got 25 or more calls like that.
All the while making sure my server was still working.
I logged into Outlook and sent a message via the internet to my work account.
The email arrived.
I logged my box out and back in and sent another outlook test message.
It worked, I got the email.
I finally got a call from one of the people in the room next to us. I said I would walk over.
I walked to his desk. Then I realized why they couldn’t log into outlook.
They were in the process of changing over its network, and someone had unplugged the Bay Network hub that connected the location network with the data center network.
The network was down.
The outlook was fine!
From then on I started all the calls I worked starting with outlook is done, by saying “check your network first!”
It is ok to ask someone to wiggle the power plug, right?