Originally posted by: AMCRambler
It's a two way street too. Having worked tech support before and not being a totally clueless like 90% of the people described here my level of frustration with the ridiculously moronic first level tech support you get when you call in is quite high. Here's my example.
About a month ago we had a pretty violent storm come through and the next day my fiance tells me her parents DSL stopped working, can I come check it out. Since I'm the one that set up their network and signed them up for DSL as a Christmas present, I'm their default tech support, which is fine I don't mind helping them out. They had a refurbed Netgear router I got off Woot.com for a good price so I immediately suspect the router took a dump. The DSL modem seems alright with the power, ethernet and DSL lights all lit and all re-light when it is rebooted. On the router side I see the WAN light is blinking on and off randomly and seems to coincide with me touching the ethernet cable in the wan port. I log into the router config page just to see if there's anything in the logs and the logs show the WAN connection attempting to connect, connecting and then failing so at this point I'm thinking the router is cooked.
I run down to Best Buy and pick up a new D-Link and set that sucker up. Still can't get a WAN connection with the new. Oh crapsky, it's probably the DSL modem. I get the router out of the middle and hook the DSL modem directly the NIC in the pc and sure enough it won't assign an address to the NIC. I even tried hooking it up with the crappy ass USB connection, installing the software and gateway and stil no go. I've got to call Verizon tech support and get a new modem. So I call up and I get the fellow over in India named Bob with a nice accent. Ok whatever, I'm pretty good at picking out what he's saying and he starts walking me through the script. Did you unplug and replug the modem? Did you un plug and replug the router? Go to start, run type in cmd. Type in ipconfig /release, ipconfig /renew, what is the ip address now? Connect the modem directly to the NIC. Blah Blah Blah, buddy I did all this already. He doesn't care gotta go through it. Argh.
Finally he's seeing the modem is not assigning and IP and tells me your network card is bad, you need to contact the manufacturer for support. I'm like dude, the network card is working fine. Remember when I told you I replaced the router, connected to the configuration page and set up the settings? Router gave the card a DHCP address and it worked fine. The DSL modem is the problem here. Ok well you have to call the billing department to buy a new modem. Oi. 40 minutes of my life gone with this mook and he can't even get me a new modem. Billing opens tomorrow at 9am here's the number.
3 days later I've got the new modem, plug it in and surprise the internet is back up.
Cliffs:
Being technically competent, knowing exactly what your problem is and calling for tech support only to be walked through everything you've already done by somehow who really doesn't know what he's doing and is just reading through a choose your own adventure tech support script is enough to make me crazy.