Network administration is the most important component in keeping your LAN working smoothly. It requires regular, though not constant, supervision, so LAN administration should fall in the hands of a qualified staff person, and not a volunteer. Since there are many different types of LAN software, from built-in Macintosh and Windows 95 systems to separate software packages like Novell, it impossible to cover all the different details here. However, there are certain aspects of LAN administration which are similar no matter what system you are using.

There are two models of software networking: peer-to-peer and client-server. Peer-to-peer means each computer communicates which each other computer on an "equal" basis, and is not optimized to share information over networks; client-server means that one machine is designed to run central programs (the "server") which are then accessed by the other computers ("clients"). The main difference is that if you run a centralized program (like a database or print-server) on a peer-to-peer network, it will probably be slower than on a client-server database.

However, this difference is not necessarily so clear when you are actually running a network. The network software itself might be designed to be peer-to-peer (like Macintoshes) but you have a central "server" computer which hosts all your shared files, and also runs a "server" version of your database. This means that although the network software is not optimized for this type of setup, your program is, so you are getting some of the benefits.

Although not crucial, it is a good idea to know what kind of setup you have, and conceptualize your network in those terms. Here are some other tips for managing your network:

Keep a map of your LAN: This is similar to an inventory, and does not have to look like an actual map. It is always good to know which wire goes where, and which computer is connected to what cable, etc. If you are using 10-Base-T cable and a hub, it is good to keep a record of which computer or printer is connected to which numbered port on the hub- this will save headaches later if you are troubleshooting.

Printer Sharing: One of a network's basic purposes is for several computers to share printers. This might require you to specify a particular computer which will act as the traffic cop for files that need to be printed. Generally, once you have set up the print sharing, you do not need to regularly modify it, unless you are adding new printers or computers. Most LAN software comes with print sharing tools that will allow you to cancel print jobs, or delay print jobs for a later time (especially important if you accidentally printed the 100 page volunteer manual right before someone wanted to print their grant proposal on deadline).

File sharing: Another basic function of a LAN is to allow computer users to "share" or copy files from one computer to another, without having to put it onto diskette. Usually, to get into another computer over the network, regardless of whether you are on a peer-to-peer system or a server-based system, you need to "log on" to that computer. I.e. you need an ID and a password which gives you access to that computer. If the files are scattered in different computers, you can imagine how quickly things would get complicated if every computer had an ID and password for every other person. Therefore, if you are sharing a lot of files, or if several people regularly work on documents together, it's always a good idea to have a "central" folder where these files are commonly kept. In small LANs, especially peer-to-peer ones, it's easy to set up a folder on someone's computer, and call that the shared folder. On larger LANs, you would set up the "server" computer to do the file and print sharing. In any case, you now only need to set up IDs and passwords on that central computer. You can go one step further, and give certain people "privileges" to special folders, and restrict other people's access to that folder. The typical example is sensitive financial documents that only accountants and managers would be given access to see. Be careful, though, because as LAN administrator, it is your job to keep track of people's IDs, passwords, and who has access to what, and the more restrictions you have in place, the more difficult it is to keep track.

You might have many other duties that fall to you as LAN administrator. These would include doing server backups; maintaining databases that are "shared" or accessible to people on the LAN; maintaining the connection to the Internet, if you have a "dedicated" or direct connection from the LAN; and even running the central email server.

Summary:

Administering LANs is a lot of responsibility, and needs a committed staff person to do the work. However, if things are kept simple, documented, and maintained, the time spent administering the LAN can be reduced greatly. These are also great computer and organizational skills which will benefit you in any environment.