Please Scroll Down to See Forums Below
napsgear
genezapharmateuticals
domestic-supply
puritysourcelabs
UGL OZ
UGFREAK
napsgeargenezapharmateuticals domestic-supplypuritysourcelabsUGL OZUGFREAK

i fucking hate troubleshooting home networking issues..

decem

New member
especially w/ a laptop and wireless router and 2.4 ghz phone in house and freaking WEP encryption.

but the worst part by far is the fact that these fucks never try to set up anything on their own and just call us as soon as they get their shit and then i ask them what their network looks like right now and then they say "hold on, let me pull the router out of the box"

argh
 
I feel your pain. Have of these assclowns that call can't even run a god damned driver CD on their own. Uhh, there is no setup icon. FUCK OFF!
 
Actually, as someone that has BEEN THERE/DONE THAT..
Let me try and brighten your outlook on this situ bro..

Immagine if they tried to install the S/W, cables etc and screwed it all up.
You don't know what they did and if in the right order etc..

See, this way, you can walk them thru it step by step knowing that it is being done right and if something still does not work you know where you stand..

I used to hate the ones that installed crap 4 different ways and I had to first spend an hour playing de-install/cleanup//

Feel better ?
 
Try working in a 40,000 user environment with over 120,000 computers and servers. Every problem get blamed on the routers, switches, and cables. So I have to sit there looking for ghosts in the networks only to find out hours later that it was a server issue.
 
It's pretty tough to talk someone through something technical like that over the phone. It is easiest to talk to them like they don't know shit (alot of times they don't). I have a whole new respect for techical support once I started doing more customer service.
 
decem said:
especially w/ a laptop and wireless router and 2.4 ghz phone in house and freaking WEP encryption.

argh

Don't forget the microwave.
 
[email][email protected][/email] said:
Try working in a 40,000 user environment with over 120,000 computers and servers. Every problem get blamed on the routers, switches, and cables. So I have to sit there looking for ghosts in the networks only to find out hours later that it was a server issue.

125,000 + Users, uncountable hardware, over 100 Med/large global facilities with little I.T. standardization
 
Oh yeah! 20 users and like 20 machines! Booyahh!

After the hurricane our wireless shit stopped working, so my way of solving it was telling them to just use the fucking cables since that's what they were there fore.
Fortunately they were okay with that.
 
Top Bottom