I might add that our office is five Macs and one PC. The server is a mac with OSX 10.3.6 client with Windows sharing on and Sharepoints (this is a lot cheaper than OSX Server
😉
We have one shared data folder on the server. (everthing shared, projects, workfiles, shared libraries etc reside there) All machines have full read/write privileges to it. This folder is backed up to one external Firewire hard drive once a day, and to another now and then (should be once a week
😉.
For this procedure, we use Silverkeeper on the server (
www.silverkeeper.com), a free no-hassle OSX backup program that is maintained by laCie (to sell more drives, I guess).
This set-up has been working flawlessly for more than two years.
The PC is a Dell with XP pro SP2. It's firewall is turned off. But we have a D-link router with firewall built-in to protect the network from external attacs through our ADSL internet link.
One thought. The fact that the machines lose their connection when re-started might have something to do with the way they get their Ethernet network adresses. If they don't have fixed IP adresses, a DHCP server must hand out temporary IP leases every time a machine starts. This is usually done by a hardware or software "router" that has a DHCP server built-in.
In my experience it's a lot more stable to give each machine a fixed local IP network adress (192.168.0.1 etc) than to use DHCP (dynamic address allocation). To make this work along with internet connectivity for all machines, you need a router that has NAT (network address translation) between your network and the Internet. If all machines have fixed IPs set, you can turn DHCP off at the router. If it has a configurable firewall too you get very good protection AND a stable, fast network. Routers are cheap these days. Well worth their money.
Each machine's address is set in its TCP/IP properties in the network control panel (system preferences).
Fixed IPs also makes for faster startup times. And you set up the router for internet by your ISP's instructions as you would a single internet-connected computer.
A tip for configuring any Ethernet network is to download Apple's Designing Airport Networks handbook:
http://manuals.info.apple.com/en/airport/DesigningAirPortNetworks0190271.pdf
It has a lot of good tips on how to to this, and it explains TCP/IP networks in what I think is the easiest possible way. You don't need an Airport to understand.
AC4.1-AC26SWE; MacOS13.5.1; MP5,1+MBP16,1