To: Valueman who wrote (645 ) 12/5/1999 4:24:00 PM From: Jay Lowe Respond to of 1782
We've talked about the premise wiring issue upstream ... lots of choices upward ... I'll lay out a straw-man to start the ball. First off, lots of general tutorials on the webcnet.com .zdnet.com First thing to think about is where you want your information ... most folks start with the cards and wires and never think about the top-down view. Basic LAN, non-dedicated server --------------------------------------------------------- - 10/100 ethernet NICs (PCMCIA in laptop if not built-in) - simple hub - Win9x client everywhere - Win9x server on one system (not the most used one) as file server - all your data on the server, separate from applications -- i.e., think of your data independently of apps or boxes -- this saves mucho grief when upgrading apps, changing boxes -- useful for mobility ... drag your data onto the laptop to go -- makes backup easy, all volatile data in one place --- you can trash all the other systems at will, upgrade, etc --- backup device in that machine: CD-W, DAT tape, DVD-W - Win9x server on whatever boxes host printers -- but avoid distributing your filesystem - server sharepoints (volumes) for each family member - another sharepoint for family-common data - high-speed internet running to one box -- NAT-based routing server on that box (Wingate, WinRoute) -- NAT clients on the other boxes, hence fast everywhere -- Win98 2nd edition has built-in NAT - UPS on the server -- don't need UPS on the other PCs ... no volatile data there ;-) Frills --------------------------------------------------------- - run Windows 2000 on the server -- built in WAN-LAN routing (internet sharing), firewall, etc - or, use an external hub-router-firewall box -- DSL or cable into hub ... routes to all PCs - make the server dedicated -- more robust, always-on, hide it in a closet, use an older PC