techrecovery | Wireless Is Not For Lusers

I 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.