Search Cornell

Organizing and Planning for Shared Resources on Your LAN

Contents of this page:

• Network Interface Basics
• Configuring and Customizing Network Software
• Adding Shared Resources to Networks
• Planning for a File Server
• Administering a File Server
• Printers
  • Adding Printers to Macintosh-Only Ethernet Networks
  • Adding Printers to PC-Only Ethernet Networks
  • Adding Printers to Mixed Ethernet Networks

Network Interface Basics

Network interface devices for computers and printers typically take one of three common forms:

• Printed circuit boards (network interface cards or NICs) designed to be installed into an expansion slot inside the computer or printer.
• Interface devices directly integrated into the circuitry of the computer or printer - i.e. built-in by the manufacturer.
• External devices which connect to a port on the outside of the computer or printer.

Each node (workstation, file server, or printer) on your network needs a network interface card and/or connector. The card or connector works together with the network operating system software and network applications to supply networking capability to the node. Additional wiring and components connect the nodes to create the LAN.

Most network interface devices are installed inside workstations. There are currently a few exceptions:

• External SCSI (Small Computer Systems Interface) devices for Macintoshes which have no available internal slots.
• External devices are sometimes needed to convert from one interface type or network type to another. These are needed for some printers, and in some cases, to convert from one port type to another, i.e. AUI (Attachment Unit Interface) to RJ-45 interface conversions.

When you install NICs, you should be aware that:

1. Improper grounding or handling of internal components can cause damage to your workstation.
2. If you are installing cards in Windows-based computers, you may need to know the addresses used by other adapter cards already in the workstations.

 

Configuring and Customizing Network Software

Workstation Software

Each workstation on your network must have network software installed on it. The software varies according to platforms and operating systems, but all programs require network-related information such as IP addresses, gateway addresses, domain name information, and subnet addresses.

1. Find out how to set up network software on the Ethernet Connections page.
2. Some of your users may use portable computers and use the same computer at home, at work, and on the road. If this is the case, they may need to change the network software on the computer when they change work locations. For example, they may use an Ethernet connection at work and an EZ-Remote connection at home, which necessitates some changes. Find out how to switch between Ethernet and EZ-Remote.
3. As part of setting up the network software on workstations, you or your users need to ensure that the Domain Name Service entries are correct. Refer to Updating Your Computer's DNS Information for details.

 

Adding Shared Resources to Networks (Printers, File Servers, Modems)

Shared resources such as printers and file servers (and less commonly modems) are nodes on a LAN that are used by everyone on that LAN. For example, everyone on a LAN may print documents on the same printer, and save and use files on a file server.

You need to plan for shared resources, just as you plan for workstations. They should be included in your planning for a network, in your site preparation when a network is installed, in your documentation, and in your maintenance and troubleshooting routines.

The following sections present some general points to keep in mind when planning for, installing, and configuring shared resources:

• Planning for a File Server
• Administering a File Server

 

Planning for a File Server

When selecting a file server, keep in mind that you need much more RAM than you need on a personal workstation to support the network operating system. CIT Network & Communication Services (NCS) can recommend the amount of RAM to purchase for your file server.

Because it is a shared device, you also need a significant amount of storage. You should have a large internal or external hard drive. In general, hard disks have a reputation for breaking down periodically, so keep in mind:

• You may want to plan for an external hard drive instead of an internal one. If it breaks down, it is easier to service and replace.
• Some network operating systems have system fault tolerance which duplicates (or mirrors) data on multiple storage devices; if one storage device fails, the data is available from another device.
• Perhaps most importantly, have a backup routine and stick to it. Consider using CIT's EZ-Backup program.

Plan for a dedicated file server. Even if your network operating system software allows you to use a file server for multiple purposes, there are several good reasons not to do this:

• The performance of the file server may be affected.
• Even the most cautious and sophisticated users hang their workstations from time to time. A hung workstation that is also functioning as a file server is out of commission as both a client workstation and server, and both the client and server functions need to be restarted. This ends up affecting the entire network by making the file server inaccessible and affecting all people using that file server.

  If you can possibly afford a dedicated server, that's what you should plan for.

Put your file server in a secure place, especially if it has an external hard drive. Access privileges lose their effect when the hard drive is unplugged and connected to another system. All folders and files can be opened and your files become completely vulnerable.

 

Administering a File Server

AppleShare, Novell NetWare and Windows NT or 2000 provide administrator's guides with their file server software. You should use the administrator's manual as your major source of information for administering, maintaining, and troubleshooting the file server. Some basic principles are worth repeating here.

1. Don't share your administrative password. Anyone using your administrative password can change any data or access privileges on the server. Like any password, it is there to preserve the integrity of the system and the data.

2. Plan! Think about communication patterns in your group or department, talk to people who will be using the file server, and plot how you want the server to function before creating groups, assigning users to groups, and granting access privileges to folders or directories.

   Your file server documentation may describe and provide examples of users, groups, access privileges, and directory structures on your file server.

3. Set up and use the file server for the greatest efficiency.

   Although it may seem obvious and tempting to divide up file server space among users and let them use it for private copies of software and data files, such an approach doesn't use a file server to its best advantage. It is particularly important to constrain the way software is used on a file server. Instead of letting people use file server space for private copies of applications, you should get network versions of the applications people use and put only those applications on the network. You save space on the hard drive and as the administrator, you have only one copy of the software to troubleshoot and upgrade. You can also keep your network documentation up-to-date more easily because you always know what applications are on the file server and thus on the network. If an application has set up files, these can all be kept on the server and administered easily.

   Note that some software does not come in both single user and networked versions. In these cases, the software you have will work on the file server, but you cannot make it available for use by multiple users until you get a license from the manufacturer. It is your responsibility to maintain a legal network and to be familiar with the site licensing requirements for the software on the network. CIT has established licensing agreements for the Cornell community with many software makers, see the Software Licensing page for details and prices.

   Urge people to use the file server as a repository for collaborative work. The most recent version of the document should be stored on the file server so that collaborators will always be assured of working on the current version.

   Encourage people to use the file server as a way to transfer data. It is a much simpler matter to move a file from folder to folder or directory to directory than it is to copy a file onto a disk and deliver the disk to someone else.

 

Printers

Printers are an important shared resource in many offices. The need to print is ubiquitous and high quality printers are costly, thus the desire to share the equipment is high.

Unfortunately, printers are among the more complicated pieces of equipment to successfully network, and printing is often the thorniest of the many system integration issues that need to be addressed on networks.

Adding Printers to Macintosh-Only Ethernet Networks

If you have a LaserWriter printer with LocalTalk ports only (i.e. LaserWriter IINT), there are basically two ways to install this printer as a node on your network. The first method is to use an external bridging device such as a Farallon EtherPrint box. The printer is connected via LocalTalk to the box, and the box is then connected with a standard twisted-pair Ethernet drop cable to a dedicated network jack. This method has the advantage of providing the printer with a dedicated network connection, with the disadvantage of the cost associated with the purchase of the bridging device. Essentially, you are adding an external network interface adapter to the printer which converts LocalTalk to Ethernet.

More recent models of Apple LaserWriters, advertised as Ethernet ready have a built-in Ethernet port, Apple's proprietary FriendlyNet port. The FriendlyNet interface will not fit into a standard UTP port which is used at Cornell. A UTP FriendlyNet adapter must be purchased. This plugs into the FriendlyNet interface and connects to a dedicated network jack.

Follow the configuration checklist below.

1. Make sure every Macintosh workstation on the network is Ethernet ready and make sure each workstation has its own activated data jack.
2. Install Ethernet driver software on all workstations on the network.
3. Ensure every printer has its own activated data jack.
4. If your printer has a FriendlyNet port (Apple's proprietary Ethernet port) you can use it to connect it to the network.

   If the printer does not have an Ethernet port use the AppleTalk port on the printer and an EtherPrint interface to connect it to an Ethernet network. An EtherPrint interface is an external device which sits between the AppleTalk port on a printer and the jack, to connect the printer to an Ethernet network.

   Do not attempt to circumvent a network interface by using LocalTalk to connect a printer directly to a Macintosh workstation on an Ethernet network. The workstation user will have to switch between printer drivers to use the printer, and other clients on the network will not be able to use the printer. Note that software exists which performs this function, but it is not currently recommended or supported at Cornell.

5. Run Apple Namer software to name the printer when it is first installed on the network.
6. Apple Print Spooler is not recommended for use on Ethernet networks.

Adding Printers to PC-Only Ethernet Networks

Several basic methods exist for attaching printers as nodes on PC-based Ethernet LANs. All involve the use of print server software, a standard component of PC-based network operating systems such as Windows NT and Windows 2000. Print jobs are sent to the print server, which sends the jobs on to the printer.

Whatever the characteristics of your LAN may be, it is advisable to determine your preferred method of printer attachment during the planning phase of a new network installation so that any dedicated network jacks can be installed and/or activated as a part of the initial installation.

The method used to connect a printer to a PC-only Ethernet network, depends on whether or not the printer is able to accept a network interface device. The list below describes the connection options.

• Install a network interface device on every workstation on the network and make sure the workstation has its own network port on a phone jack connecting it to the network.
• Print server software may be required to send local print jobs to a printer. Novell NetWare software contains print server software. A Novell file server must be installed on the LAN if you want to use this software.
• There are three alternate ways to connect a printer to an Ethernet network with a Novell NetWare file server using either the parallel or serial port on the printer. Choose one of these options for a printer that will not accept a network interface. If you aren't sure whether or not your printer accepts an interface, contact the vendor.

1. Connect the printer to a workstation on the network. Run Novell RPRINTER.EXE software on the workstation to allow it to handle print jobs in the background. The person using the workstation may notice a momentary halt when jobs are printed. This workstation should not be heavily used. If a user error necessitates rebooting the workstation, network printing is not available until the workstation is running again.

   Local printers connected to workstations need not be made accessible to all other clients on the network. Novell print server software sets up queues for printers and controls who is allowed to use a printer queue. Refer to the Novell documentation for details. Setting up print servers and queues under Novell can be tricky. If you need extra help, you may contract with CIT to provide it. Contact CIT Network & Communication Services.

2. Connect the printer directly to the Novell file server on the network. Run PSERVER.NLM on the file server.
3. Connect the printer to a dedicated print server, a computer which is used only for print service. Run Novell PSERVER.EXE software on the print server to allow it to process print jobs. This is a good way to reuse older equipment and improve network printing performance at the same time. Also, this configuration is less subject to user error than configuration 1.

Many printers, such as HP LaserJetSeries can accept an Ethernet network interface and connect directly to an Ethernet network. Usually, these printers come with a parallel and/or serial ports, and a network interface is optional. The interface of choice at Cornell is an unshielded twisted pair port (UTP port).

Many print server devices are available through the Cornell Store from HP and other vendors that support Novell NetWare and Apple EtherTalk protocols, and switch between them automatically. You may need to run Novell PCONSOLE software to install it if you are using Novell Netware as your printer's print server.

RJ45 UTP interfaces which support Novell NetWare protocol (IPX (Internetworking Packet Exchange) only are available, but are NOT recommended at Cornell. TCP/IP is the recommended communications protocol at Cornell.

Many applications running under Windows, such as Excel and Word, use PostScript printer drivers. If you intend to use PostScript on a PC Ethernet network, see the discussion on upgrading printers for PostScript in the following section on mixed Ethernet networks.

 

Adding Printers to Mixed Ethernet Networks

If you have a mixed Ethernet network (Macs and/or IBM type machines and/or UNIX machines) and you have some people who want to print PostScript files and others who need to print ASCII files (some old programs only print ASCII), then the best way to help yourself and the people on your network is to talk to an expert in CIT Network & Communication Services before purchasing a printer. Team members are very experienced dealing with the issues of networking printers and can advise you on the best printer for your situation. Configuring a printer on a mixed network is a complicated task; some steps that may need to be taken include:

1. Install a network interface device on every workstation on the network and make sure the workstation has its own jack connecting it to the network.
2. Be aware that print server software may be needed to send local print jobs to a printer. Novell NetWare software contains print server software.
3. Use a printer, such as the HP LaserJet Series which can accept a network interface and connect directly to an Ethernet network. Usually, these printers come with parallel and/or serial ports, and a network interface is optional. The interface of choice at Cornell is one with an RJ45 UTP port. When purchasing a new printer please specify that you want the RJ45 UTP Ethernet option installed.

   The HP LaserJet 5000N with an HP JetDirect card uses the RJ45 UTP interface and is recommended because it simultaneously supports ASCII and PostScript under Novell NetWare and Apple EtherTalk protocols, and switches between them automatically. This printer will connect directly to the network through a CIT data jack. All you have to do is assign an IP address to the printer and directly access it from the network.

   Some HP printers which are intended to process PostScript files must have a LaserJet PostScript Cartridge Plus installed, as well as 5 MB of memory to print PostScript jobs. Beware of buying "bundled" printer upgrades which include a PostScript Cartridge, extra memory, and a network interface, because the network interface may not be the one you need. If you need help configuring a printer for your network contact the Cornell Store or CIT Network & Communication Services.

   Printing in mixed network environments, which support computers and peripheral devices from several different manufacturers (Windows, Macs, UNIX workstations) using several different printing protocols (e.g. PostScript, IPX [Internetworking Packet Exchange]) will be greatly simplified by deploying some of the more "intelligent" printer interface devices such as HP's JetDirect card.

Home | FAQ | Troubleshooting | DHCP | DNSdb
NCS | NOC | Mailing Lists | Notification
Network Status | TSP Forum

Last updated: February 11, 2002
Reformatted: June 29, 2007