X
Tech

The network strikes back

The LAN was working (I swear!) but then...not. Hello, tech support.
Written by John Blackford, Contributor
If you read my column last month, you may recall that my upgraded PCs and HomePNA network were humming (though I was grumbling about the time I spent on the project).

There was a small problem, though. If the upstairs PC (the modem server) lost contact with my ISP, a window popped up, asking, "Reconnect?" My wife would then have to walk upstairs to click "OK." Strangely, sometimes even that didn't work. While troubleshooting the glitch, I figured I'd move the modem downstairs, so Anne could reconnect without leaving her PC.

Call me naive, but it seemed reasonable. The LAN instructions were written in baby talk, and installation was smooth as silk. The network had come up immediately, and Web access was possible from either computer. As I filed last month's column, I viewed the network as the simplest part of my upgrade.

But after switching the modem to the downstairs PC, the LAN could no longer "see" it. Putting it back on the upstairs system did no good, nor did pulling out the LAN cards on all the PCs, removing the LAN software, and starting over. The LAN couldn't see the modem. Period.

What followed was a crash course in networking that involved rereading instruction manuals, talking to tech-support types, and mediating the LAN/modem bickering. I discovered the beauty of freeware and the value of advice from experts—including some online. Also, I found, vendor tech support may be unavailable. For example, if your PC vendor goes out of business, you'll pay for Windows support, assuming you're running the OEM version that came installed on your system. You'll pay for hardware support, too, unless you signed up with a third-party provider.

Facing my own LAN problem, I was eager, confident, and persistent. The latter quality got me through the process. I can't describe the frustration of having no Web access while spending hours on hold, only to hear an offhand suggestion like, "Well, you might try..." followed by, "and call again if that doesn't work."

Anyway, after much installing and uninstalling, phone calling, Web searching, and experimenting, I got the network running again. I won't embarrass the HomePNA-card vendor by repeating its name, but several of its support people recommended a freeware product called AnalogX proxy server (www.analogx.com) over its own bundled software for handling the dial-up connection.

Though everything's working, I still must reconnect manually when the connection gets dropped—basically where I started out. Our "Computer Cures" columnist, Alfred Poor, suggested a utility that automatically responds "OK" whenever that window pops up. I've downloaded Macro Magic 4.1 from ZDNet Downloads to see whether it's up to the challenge. I'll let you know.

During the tech-support phase of the saga, I mentioned to one of the network techs that I planned to switch to cable or DSL. In that case, he said, install a router between the broadband modem and the PCs, stringing CAT 5 cable to each. Avoiding that, of course, had been one reason to go with a phone-line-based network! But further research confirmed the advice, so that's the long-term plan.

But wait! As I was writing this column, I got a call from Tiny Software, maker of WinRoute Pro, a software router and firewall. According to the representative, the product can run my network, replace the proxy-server software, improve security and stability, and enable faster access via the dial-up modem. (I'll still need the utility to auto-reconnect until I replace the modem.) So I'm going to give WinRoute Pro a try.

A few minutes later (I'm not making this up), my wife called with her own suggestion: Call in a network specialist and get out from under the whole process. "What!" I said. "Pay for onsite service? No way!" Besides, troubleshooting is kind of fun. I'm not the only one who's stumbled on home networking. I know the IT guru at a major financial company, whose wife reports trouble reaching the Web through their home LAN.

The lesson is that home networking and dial-up modems are a tough match. Tech support can be hard to come by—or it might not quite address problems caused by several products interacting. Consider online advice an option; Jim O'Brien's column, on p. 72, makes some great suggestions. Freeware may help, too—and you'll find a vast array in the ZDNet Downloads area.

My advice: Don't assume your upgrade will be hassle-free. Have a backup plan, and build time for troubleshooting into your schedule.

Editorial standards