Wireless Is Not For Lusers
Nov. 24th, 2004 09:15 am![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png){kind=small}
jacobine.livejournal.com posting in ![[community profile]](https://www.dreamwidth.org/img/silk/identity/community.png){kind=small}
techrecoveryI am going to shoot one of our techs. Seriously.
He agreed to set up a wireless connection for one of the managers who works remotely in podunk Louisiana. This man frequently works out of his home. However, he's rather computer clueless. And he's trying to use a wireless connection. With multiple people. Across VPN. Over a DSL line.
He calls us at least once a week. Once. A. Week. Something is wrong, or something isn't working. The problem currently is that outlook keeps punting him into work offline whenever he tries to send email. Oh, it works fine for 15 minutes or so... I've boosted his timeouts, but it hasn't worked yet.
This points to nat latency to me, and the fact that some routers boot your connections after a certain amount of inactivity. He doesn't understand this, of course.
Neither does the tech, since he's always referring problems to us and this is clearly not a problem on the server side. I love this tech and he's a good worker, but he's really clueless about some things.
(At least I just talked to said tech and told him what I thought, so he's going to call one of the network folks...)
My boss said I could shoot him. So anybody like to help? Argh.
He agreed to set up a wireless connection for one of the managers who works remotely in podunk Louisiana. This man frequently works out of his home. However, he's rather computer clueless. And he's trying to use a wireless connection. With multiple people. Across VPN. Over a DSL line.
He calls us at least once a week. Once. A. Week. Something is wrong, or something isn't working. The problem currently is that outlook keeps punting him into work offline whenever he tries to send email. Oh, it works fine for 15 minutes or so... I've boosted his timeouts, but it hasn't worked yet.
This points to nat latency to me, and the fact that some routers boot your connections after a certain amount of inactivity. He doesn't understand this, of course.
Neither does the tech, since he's always referring problems to us and this is clearly not a problem on the server side. I love this tech and he's a good worker, but he's really clueless about some things.
(At least I just talked to said tech and told him what I thought, so he's going to call one of the network folks...)
My boss said I could shoot him. So anybody like to help? Argh.
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
no subject
Date: 2004-11-24 07:25 am (UTC)no subject
$10,000 he's done
no subject
Date: 2004-11-24 08:08 am (UTC)Hmm and if he's on the VPN is the Wifi secured?
Just use ethernet. sigh. moron.
Heck I'd do it for planetickets and nice gun on arrival.
*grin*
no subject
Date: 2004-11-24 12:26 pm (UTC)The company I work for offers wireless solutions. One of which is a self-install and one which a tech comes out, installs everything, gets it all working, etc.
We almost never have problems with the latter. The former, however, we do get quite a few. Most ranging from "My computer has to have a special wireless card for it to work?" Yes, yes it does. Wireless is not some magical box you put in your house that gives you a connection around the world.
And oh man, the amount of people who get a Linksys and expect me to walk them through setting it up and get pissed off when I tell them we don't support it and to call Linksys. "But I can't get through to Linksys! Waaah!"