Maybe you should try turning it off and back on again. Oh, just kidding. Your boss sounds like an unreasonable person.

This is why when I call my company's IT department I say "this is the problem and I already tried turning it off then back on." Throws 'em for a loop

Lol maybe he should try deleting system 32 :p

Having worked in tech care, that's actually the first step all the time because what happens if you've left your computer/mobile on for a long time is as new connections are made to the network, your connection slowly filters down the list, and restarting brings you back up to the top, ie. better connection.

That's not how computers work, but nonetheless a reboot is always a good first course of action. (this pc probably needed a reconfiguration requiring two separate reboots).

Yeah, working IT we hear that a lot. "Heh -- just so you know, I already turned it on and off, hah!" What we hear from the same people, almost as often, is "huh -- well, it seems all right now. I guess it fixed itself" when we remote-restart their machines. We usually come up with some BS reason why we're executing the restart, since it's never worth it to say "but I can see your uptime, and your computer's been on since 9 this morning."

Sometimes being smarter than everyone else is a curse

it can be compared to being the only sober person in a room full of druken persons.

That's my motto.

Sucks to suck. :/

Huh?

perhaps she thinks it sucks to suck a penis? #girlproblems

hash tags, not twitter

Most tech support personnel think like that because a simple reset is usually the problem. If you know the problem, why don't you just fix it yourself?

I am guessing the OP did not have admin privileges.

Never worked in an office, have you? Even if it could be fixed locally, the accounts are almost certainly limited privilege.

I worked in an office in environment for a very short period. I was actually written up for fixing a network problem that IT couldn't fix. The real world doesn't apply to places like that. It's really sad.

As others have said, OP may just not be able to do it themselves because of not having permission. Another thing that may be a set back is they don't know HOW to fix it exactly. There's many times where you know the problem, and you know where to go, but not how to get there. It's kind of confusing to explain. Hopefully that makes sense to someone. lol

If it's such a simple fix, do it yourself. Otherwise, go through the motions of tech support and eventually they might get you to the source of the problem and help you through it.

Have you ever talked on the phone with Tech Support before?

Yes, actually, and they've always made me go through all the baby steps of turning it off and on, checking to make sure my wifi is turned on, etc., and then we generally get to the source of the problem once they've ascertained it's not something braindead simple. It takes a while is all.

Well, did you?

Seems like your username would be more fitting for your boss, OP.

wait... so why didn't you just fix it yourself?

OP said they knew what the problem was. However OP did not say that he knew how to fix it.

He wouldn't have an admin account (password). Most of the time in an office the system is locked down. You may know how to fix something but you're rarely allowed to. Or it may be a problem from the server end which again, he can't access.

Your tech support certainly isn't being very supportive. I hate it when things like this happen, sorry OP.

Speak up then!

The Boss doesn't care about things like that! IT is like the weather, you just have put up with it.