Warning - extreme navel-gazing ahead. Feel free to turn back now. I just need to vent.
A while back, I had a navel-gazing post about my plan to turn an old eMachines Celeron PC into a home file server. I figured I had four basic options:
- Install a full Linux distribution, including Samba for serving files to the XP and Vista machines.
- Install a specialized Linux distribution for web, mail and file serving (such as ClarkConnect or SME Server).
- Install a specialized distribution for file serving (FreeNAS or NASlite).
- Buy the OEM version of Windows Home Server.
I originally planned to go with Xubuntu, figuring WHS was too expensive and the other options too limiting. In the end, however, I decided against my better judgment to use NASlite. It seemed far easier to configure, supporting Samba, FTP, HTTP and RSYNC out of the box. Plus, it’s a tiny download that runs off a RAM disk, freeing most of the 40 GB master drive for storage along with the 320 GB slave. The download was easy, and the install relatively so. If you’re a first-timer, have the PDF of the install guide available, as the text-based installer is far from self-explanatory. After several reboots, I had a nice Linux-based file server hooked up to the wireless network.
Then the problems started. Three of the Windows machines saw the server automatically, and it was easy to right-click and map the network drive (I picked S: for Server). The newest machine, the infamous $348 Wal-Mart laptop, just wouldn’t find the server. It wouldn’t find the two XP machines, either. Turns out the blasted Norton Internet Security was screwing things up. Rather than figure out which setting to change, I just deleted it from the drive (which I planned to do anyway) and installed Windows Live OneCare, which I prefer anyway.
So far, so good. Then I decided to get too ambitious. I had a nice little appliance serving documents, photos, video and music. iTunes on all four PCs was using the network share for its library. OneCare was backing up to the network share. With a little effort, the My Documents folders were being automatically synced with the Documents folder on the NAS. That’s all great, but what if I could access my files from the Internet? Wouldn’t that be better? Of course it would. NASlite comes with a simple HTTP server, but all it does is serve the contents of the FTP directory. You can define a default gateway, but this would make the documents world-accessible. That won’t work for obvious reasons.
At this point, I decided that a VPN was the way to go. Just connect the remote PC via VPN, and bingo - access to the NAS. So I trekked down to BestBuy and picked up the Linksys WRV200 Wireless-G VPN Router. Thus begins the trauma. Verizon had supplied me with the Westell 327W DSL modem/router, which was running the wireless network. To use the Westell with the Linksys, I had to put the Westell in bridge mode, which was easy enough. Then I hooked up the Linksys using the CD. Turn on all the PCs, and connect to the new WiFi network. Works pretty well, although the Acer wouldn’t connect the first time. Trying to set up the VPN was a disaster. Linksys doesn’t provide documentation, of course, just the Quick Install Guide. There’s a manual on the CD, but it contains next to no information about the VPN. And the information it does include is sometimes wrong. As a simple example, the manual says that when you configure a VPN user, the router will automatically change the dynamic IPs on the network from 192.168.1.x to 10.x.x.x, to avoid conflicts with remote networks. What it actually does is pup up a warning and ask you to provide a new IP for the router. Presumably, it would then change the IPs assigned via DHCP, but none of this was clear. But in the end, I think I ended up with a configured VPN endpoint and some users. DynDNS would turn the dynamic Verizon IP into a usable URL.
I never got a chance to try it out, however. Last night, we tried using Word for the first time since installing the Linksys. And Word crashed upon startup. Try again, crash again. Lather, rinse, repeat. It appeared that Word was hanging on “connecting to printer…” Pushing Escape would allow Word to start, but certain commands would crash it 100% of the time, such as adding a header. Google suggested that turning off “print in background” would help, but no dice. Another page suggested the problem was that there was no local printer defined, and Word was having trouble connecting to the network printer driver. That could be - the laptops print to a shared printer hooked up to the desktop because the stand-alone print servers didn’t play nice with the Epson all-in-one inkjet when I bought the printer (apparently, they work better now, but the ones that do cost as much as the printer did). Defining a local printer allowed Word to start. Changing the printer to the shared printer to actually print a document made Word crash.
Eventually, I decided the problem had to be the firewall on the VPN router. That’s the good news. The bad news is there is no way in the web interface to either (a) turn the firewall off in order to test this theory or (b) allow printer sharing over the network, something Linksys’ consumer routers allow via a single click, and something the Westell was pre-defined for. So I yank the Linksys out, narrowly avoid throwing it at the wall, and reset the Westell to turn it back into a router. Reboot, connect to the Westell web interface, which says PPPoE is connected. But no internet. The default FF home page just says “could not find the file specified”. Trying to load a different page redirects to the Verizon DSL activation page. Oh, so I have to reactivate because I reset the Westell, OK. Using Firefox just sent the DSL software into an endless cycle of checking for updates. After a while, I tried IE, which seemed to work. Unfortunately, the software would accept what I assumed to be my Verizon password. Get on the phone to Verizon, and pick reset password. That’s fine, but it tells me to go to a web page to complete the process, which I can’t do because I need the password to connect to the internet. Call Verizon (at this point it’s about 12:30 am), who assign a temporary password. Finally, at about 1:15 am I have restarted the Westell-based network. Word doesn’t crash.
So I’m giving up on that Linksys VPN router. There’s probably an easy way to do this, but I’m just too tired to care. That $150 for WHS is looking pretty good about now.