Tales From the Support Crypt
An anonymous reader writes "Talking viruses, infected physical devices, and lights that go out are some of the 'problems' Panda Security's tech support service has had to face. Many of them were not a result of computer viruses, but of confused users. This proves once again, that antivirus manufacturers must make a special effort to increase user knowledge regarding computer security and malware effects." For anyone who's been on the receiving end of such questions, now's a good time to tell your cathartic tale.
My all-time favorite true story occured when I tried to help my dad (I bet that for everyone here, our parents are our #1 support customers).
Dad reports following problem: in the last month or so, the mouse started acting strange. Every time he gestures right, the mouse goes left. When he wants to go up, the mouse moves down.
I look it up online, suspecting some virus having fun. Can't find anything.
Dad reports that he got used to the problem, he just has to gesture in the opposite way and then he can use the computer again. Not a great workaround, but it's good enough for him.
At my next visit home, I finally can diagnose the problem live instead of over the phone: Dad was holding the mouse upside down.
True story - lasted for a month before problem was fixed. My fault for not figuring it out sooner.
--
FairSoftware.net: where geeks create side-businesses together
Six months of AI programming will make you think there is a God. Six months of tech support and you'll know there isn't.
#fuckbeta #iamslashdot #dicemustdie
But they charged us $600 to chop off dad's hands and reattach them the other way round.
I would say it is best to avoid geek squad.
I took a call from an end user a couple of months ago, informing me she was having trouble changing her password. She was receiving an error message that said "Passwords cannot begin or end with a space."
When she asked me what to do, I focused all of my energy on maintaining calm professionalism and replied "If you're typing a space before the new password - don't; if you're typing a space after the new password - don't."
Her reply?
"Hey that worked! You guys are so smart, I don't know how you can remember all this stuff!"
One of our senior techs (yes, feel free to laugh, I know I do!) came to tell me he had a virus on his laptop. His cursor was runnign wild, an dplenty of windows kept popping open and apps being launched. He could not figure why, so his best guess was "a really bad virus."
From personal experience, 97% of people who guess "It must be a virus!" have no virus whatsoever (the reverse is also true - 97% of viral issues ar edismissed as "something weird is going on and I don't know why") so I assumed it surely wasn't one. I had him unplug his wireless mouse bluetooth dongle, which ended the problem immediately, so it was clear where the problem was coming from. I guessed bad drivers, and suggested he reinstall. Putting them fresh from the driver disk simply returned the issue.
The following day, while looking for a spare power supply, we stumbled on the answer. The wireless keyboard that came with the mouse he was using had been carelessly thrown in there, with another keyboard on top, mashing down a large part of the wireless keyboard's keys. The laptop was just doing as it was told by the keyboard all along.
8 years ago I had a guy at our company come up to me and tell me he got an email from a girl that said "I love you." He then said, she attached a vbs file to the email and he spent the last 10 minutes trying to get the attachment to work. He said he double clicked on it, ran it from a command prompt and several other ways but couldn't get her "love" program to work for him. The guy was an IT analyst.
"Anything tastes good if you deep fry it."
I've had two of those happen this month.
First case:
We got an email saying the internet was down and had been for 15 minutes. We monitor this company's connection with a constant ping (every 5 min or so). If it goes down, we'll know. We didn't get one. Plus we were able to VPN in and get on their servers.
Called the customer up. Turns out www.msn.com was busted and wouldn't load. Google, Yahoo, CNN and BBC worked just fine.
It was very likely they heard a badly suppressed laugh right before I hung up.
Second case:
Another company's internet tanks. We can't ping their public ip, they're down. This happened on a Monday, 10AM.
After dragging AT&T there on a leash so they could swap out some hardware (inside a locked box...), the net started working again, Tuesday, 2PM.
We got an email from them shortly after it came back up, dated Monday, 11AM... "Our internet's down."
I need to print both of those out and frame them.
I've done a bit of support for an electronics company that also made TVs. Back in 2007 one of their newest models was a decent 40" LCD tv, HD ready etc. and fairly cheap. We got a LOT of support calls on that one because of the design of the rear of the TV.
The TV had a physical on/off switch, but the designers had decided to "hide" it between the speaker and display enclosures on the back of it. It was clearly outlined on the diagram on page 5 of the manual, but still we had a ton of calls about this particular model, because people couldn't turn it on. And invariably about half of them would complain that they already hung it on the wall and couldn't reach the bloody switch. Boo fucking hoo - read the manual before assembling your unit.
But - I had one phone call about this TV that still has me smiling ear to ear
Me: "[$Company] support, you're talking to Martin" ... hi?"
Very timid, baby girl voice: "Hiiiiiiii?"
Me: "Ehh
Very timid, baby girl voice: "My name is Pia"
Me: "Hello Pia."
Pia: "I'm four years old!"
Me: "Is your mom or dad around?"
Pia: "My daddy doesn't know how to turn on his TV"
At this point I simply couldn't help but laugh out loud. Then I hear a grown up female voice in the background
Mom: "Just go ahead and laugh, that's what we've been doing all day long"
Me: "Okay, can your dad hear me Pia?"
Pia: "He says he can"
And then I proceded to guide him to where this switch was.
It's one thing to be a stupid user, it's another thing entirely to know that there's something you don't know - at least that's what Socrates believed.
I have to tell you that techies often get the "no I don't" kind of response because of all the wrong diagnoses that have been given in the past. I can count many times when I have instructed a technician on what to do, what I have tried, and then get some half-assed "please reboot", or "check the ethernet cable" or whatever. The thing is, it is impossible to tell the smart, slashdot reading help desk personnel from the just-graduated-from-college-and-trying-to-find-a-real-IT-job person.
Let's see... last week I actually noticed my mouse wandering around on the screen where it wasn't supposed to go. Then the computer opened up a Windows Explorer on its own. No shit. So I opened up Notepad, in between wrestling control over my mouse, and wrote "This is my computer, what the heck are you doing on it?"
The response was "Are you employee #XXXXXXXXXX with the email problem?"
My response: "No, I am working at home and wondering why you took control of my computer."
Him: "Sorry, I am trying to help another user."
Me: "Please give me your name, phone number and department so I can check who you are."
Him: "Sorry, Matt Smith, XXX-XXX-XXXX, Support Desk"
Me: "No worries, don't let it happen again."
I let him drop after that. And here I was freaking out that during my "work" from home, at the exact point I happened to be browsing Slashdot on the company laptop, that they were on to me and I was busted. I am probably busted anyway based on the logs...
This post brought to you by your friendly neighborhood MBA.
That will be the best part.
echo -e 'global _start\n _start:\n mov eax, 2\n int 80h\n jmp _start' > a.asm; nasm a.asm -f elf; ld a.o -o a;
On night at about 2am, I received a call from one of our field technicians. Quite distraught, he told me his computer was broken and he had a high-profile job in the morning and needed it replaced ASAP. He explained that when he tried to type in his username to login, it was showing garbage on the screen, "all sorts of weird numbers and symbols". He regaled me with the story of how he had taken the laptop apart, checked the contacts on the keyboard ribbon cable, found his keyboard chipset model, and Googled the problem, eventually finding it to be a common issue known as a "K9 Keyboard Chipset error". This guy had done his homework.
Having no way of getting his laptop replaced so quickly by myself, I was forced to call the desktop support manager (who was the epitome of a BOFH). He groggily answered, and the technician told him the issue.
"Do me a favor," said the BOFH.
"OK?" the technician responded.
"Hold down the shift key, and press the Num Lock key. Then login."
"ITS WORKING!"
"Gentlemen, we will discuss this on Monday," growled the BOFH, before slamming the phone down. Those words are to this day etched in my mind. I don't blame him for being angry, but in my defense, the tech *did* sound like he'd already tried everything. From then on, I became known as NumLock PantsDown. I'll tell Slashdot about the "PantsDown" portion another time.
holy crap, I can right click in minesweeper! Now its a whole lot more fun to play!
My potato gun was confiscated by the United Nations. They said I wasn't allowed to have weapons of mash destruction.