Linksys BEFSR41: Networking for Dummies (Like Me)

My friend Nate is a techno-junkie. He's pushing 85 this year. That's both in age and the number of toys he has plugged in at his home. He won't be happy until he has a telephone and a speakerphone in every room. When he hangs up a phone, they all buzz, ring, clang or click. You can easily close your eyes and pretend you're in a Swiss clock factory.

Nate's also trying to help the industry reach their goal of averaging one computer per household. He and his wife have six. Four are active. The other two aren't plugged in, but stand by on nearby shelves to be used as 'hot spares', should one of the primary machines crash. ...And that happens frequently. Nate downloads anything he can find that's free, including viruses. He's not a stingy with his finds. He manages to spread them among all of his computers, usually via a floppy disk.

The Non-Network, Network.

In light of that, you can see why I didn't comment on Nate's 'network'. In his days of the 56k--and slower--modems, I was frequently called upon to help with telephone wiring. Nate's two computers are at one end of the house. His wife's machines are on the other end. I had a similar setup at my house--with three computers--but I ran network cabling, not phone wire, and connected all of the machines to a 10BaseT hub. Since all of my machines were running Windows 98, it was reasonably easy to share the modem. ...And everything else. In Nate's case, I figured anything I did to facilitate his computers sharing files would increase the time I spent at his home removing viruses from his machines.

Nate is a garage sale addict. His own garage would qualify as a computer museum, if he'd allow the public to view his collection. His active PC's aren't much different. The newest machine runs Windows ME. Another one runs Windows 98. A third PC has limited RAM, so he installed Windows 95. The final machine could run Windows 95, but Nate waxed nostalgic. Windows for Workgroups 3.11. As you can see, setting up a LAN with that collection would be an IT's dream--if the IT enjoyed dreaming about snakes, dentists, tigers, and monthly visits from the IRS.

Nate switched to DSL. He originally left his wife's machines and one of his PC's on dialup. Only his primary machine had a need for speed. Then he reflected that one reason he was paying for DSL was to free up his phone line. It wasn't happening. So, I got called over to install Ethernet Cards on the other three computers. I did, figuring he was finally entering the age of the LAN. Wrong. He installed the DSL software on each computer and began shuttling the DSL modem to wherever it was needed. Networking ala Nate.

Bite the Bullet

I couldn't take it any longer. I explained that since he had Ethernet Cards in each computer, he would be better off networking them. I said this with a pained expression, because I knew what was before me. It's bad enough setting up addresses and sharing on computers running the same operating system. He had three separate ones--four if I counted the old 3.1 machine. (And I wasn't at all sure that one would ever network. It was hard enough finding an Ethernet Card that fit the old 486 motherboard.)

I realized immediately that there would be a problem sharing the DSL modem plugged into Nate's computer. I told him that if we put his machines on a 10baseT hub similar to mine, he'd need a second Ethernet card to connect to the hub. His primary card would need to stay with the DSL modem. He had an empty slot for the second card, but I lamented about how slow my computer booted with the two cards. Consequently, I suggested he go with a DSL router. It would do the same job as the hub, with all of his machines plugged into it, but the DSL modem plugged into it as well, not into his computer. He'd not need another Ethernet card.

He was jazzed about the idea. I was cursing myself. I foresaw many an unhappy hour trapped in Nate's Computer museum. I'd have to play with IP addresses, DNS settings, protocols, and the like until all four machines finally talked to each other. Then I'd have to figure a way to have the 'hub' talk to the DSL modem.

Sex is Highly Overrated

I went along with Nate to the local Best Buy. They had the cables we needed. They also had a wide range of Routers. I say wide range, because they varied widely in whistles, bells and price. My friend is on Social Security, so we started at the low end, settling on the Linksys Router. It was a combination router and four port hub. It also said it came with firewall and antivirus programs. I smiled, thinking that perhaps I had performed my last virus cleaning at Nate's house.

We ran the wires and I plugged in all of the computers. Lo and behold, all of them were talking to the hub. All except the relic. I wiped the drive and loaded Windows 95. Then I installed the program that comes with Windows 98 that allows a Win 95 to network with the more advanced systems. I'd worried about the Windows ME, thinking I'd have to load a program on the other machines to make them speak with it, but I didn't.

That's when I found out I'd erred. The setup provided by Linksys assumes that the modem is still attached to the PC, not the router. I swapped wires and pressed on. Linksys provided two CD's. One was the manual and troubleshooting guide. The second was a magic wand that promised an effortless setup and connection. I grumbled about that one. Been there, done that. Most of those magic disks only work after a lengthy time on hold, waiting for a technician to answer their phone.

The program started. The first question that hit the screen was, "Do you want to see the tutorial?" I abhor tutorials. They either left me wondering when the developer would recognize that my IQ wasn't a single digit, or I'd walk away thinking I should be getting some sort of honorary software engineering degree. As is my custom, I emphatically told the program I didn't want any stinking tutorial.

I expected to see something like "Are you sure?" or "Do you really want to quit the tutorial?" I didn't. The program went right to work. It detected the installed Ethernet card and modem while asking me--politely--to wait. Then it told me to unplug the modem from the computer Ethernet Card and plug the RJ45 connector into the hub, cautioning me to make used I used the correct port labeled 'WAN'. I did. Finally, it asked me to take another cable and connect the computer's Ethernet Card to one of the ports on the hub. I did that too. When it sensed I hadn't screwed up anything, it thanked me and asked for the username and password Nate used with his ISP. I provided that. It thanked me again and said it was finished.

I stared at the computer screen. Naw. It can't be. Nate asked me what we did next. I said I wasn't sure, but maybe I should open a browser? I did. Internet Explorer opened and went right to Nate's homepage. I'm online! ...It's magic! I was almost orgasmic.

The proverbial pessimist, I checked the network. All the computers were talking to each other. Then I went to each PC, opened the browser, and discovered they were all online. No tweaking. No calling tech support. No wondering why two computers saw each other, but no one else. No trying to figure out why one couldn't go online. (Actually, I forecasted I'd have three that wouldn't be online.) They were all searching the internet for viruses Nate had missed. Now there was no maybe about it. I was orgasmic!

DSL... With a Difference

While I strongly recommend a router over the software solution--one where one computer is connected to the DSL/CABLE modem and shares the connection with the others--there's one major change in how things work. With a modem connected to computer, you know immediately if the DSL fails. The computer will try to reconnect, and you'll see it on the screen. With the router, you won't. If the DSL quits, you'll just start seeing those nasty 'page not found' screens. The solution is to turn off the modem, wait a few seconds, and re-power it. When you do, the hub will see it synch and pass your username and password to the ISP, reconnecting itself to the web.

The hub actually has its own chip. When you want to set up the various options, you use your browser and enter the hub's IP address. When I first did this, I discovered the Linksys Router had several pages of options. They are, for the most part, self-explanatory. The book that comes with the router does a nice job of explaining the rest.

Addressing the hub should be a one shot deal. There has been one occasion when its little computer scrambled its brains. I had to go in and reenter the ISP username and password. I also--yes I installed one on my LAN after seeing how easy it was--occasionally activate a function that logs IP addresses. It truly amazes my teenage son when I close my eyes, press my hand against my forehead, and tell him what sites he's been surfing. I don't leave 'IP logging' activated all of the time, but he doesn't know that. It's nice to see the kid twitch and not the parents.

I also discovered that Linksys had stretched the truth. It does come ready to install a firewall and antivirus, but you have to purchase them separately. I mumbled about that for several minutes. Don't get me wrong. I love ZoneAlarm. I just see no need to buy ZoneAlarm Pro to firewall my system at the router level. Instead, I have the free ZoneAlarm installed on each computer. True, firewalling the hub and taking the firewall off my PC's would save computer resource, but I'm stubborn. And installing antivirus on the hub? PC-Cillun may be a very nice program, we've never been close enough where I allowed it to blow in my ear. My heart belongs to another. I've placed my trust in Norton 2002, thank you.

Was It Good for You?

I guess! I was so enthralled with the way the router--with its accompanying software--virtually installs itself, that I've installed it on my LAN. I've also installed it for many of my other friends. It's not that I'm that nice of a guy, volunteering my services. I just love to watch that installation program do its magic, and I'm so easily amused. ...And the installation has yet to fail me on the 6 systems I've set up.

No one has had any problems with the device. Some consider that amazing because at $69, it's considerably more inexpensive--and some call that 'cheaper'--than the $199 router our ISP's have tried to sell us.

True, there are more expenses involved. It is a hardwired router. You have to buy cables and run them. (That can be a two six pack project.) Still, I'm still not overly impressed with wireless. I keep worrying that when I go online with a remote computer, the garage door will start cycling, the TV will randomly change channels, and the cordless phone will ring.

Then there is the expense of equipping your computers with Ethernet Cards. That runs about $10 per computer. ...But that's becoming less of a problem. Most newer computers come with them installed as standard equipment.

There are more expensive routers with more whistles and bells. There are a few that don't cost quite as much. That's your choice. For me, the Linksys BEFSR41 is just perfect for my little home network.

...And it's so much fun to install!