Update Notes: 20-Feb-2001

Err, Bill Thompson reminded me that besides the two types of print servers I mentioned, there's also a third type whereby the print server functions are handled entirely by the network operating system (e.g. NetWare, Windows NT, etc.). In such cases, the printer(s) are connected directly to the parallel or serial port(s) of the server computer.

While this type of print serving is indeed possible - and in fact may be considered the default type of print serving by many - it's not something I recommend, although I SHOULD have mentioned it (mea culpa). Its undeniable advantage is that you save money by avoiding the purchase of additional hardware since this capability is built into most if not all network operating systems.

But, in my opinion, its drawbacks far outweigh its benefits:

• It adds a load to the server, not in terms of servicing the print queue, but in terms of handling the hardware port to which the printer is connected. Servers have to send and receive information out through its LAN interface(s) anyway, so sending data to a networked printer isn't much different from serving a file request. On the other hand, having to INTERRUPT this to send data out another device (i.e. the printer port) complicates things. The way I see it, the fewest peripherals should be attached to a server in order to maximize its "serving" prowess.
• With parallel ports at least, and ignoring older serial printers for the moment, you can only create two print servers this way (using LPT1: and LPT2:). Trust me, you DON'T want to try and add LPT3: and LPT4:.
• Given that the maximum recommended length of a parallel cable is about 5 feet, the printers must necessarily be located close to the server. If your servers are rack-mounted (or perhaps rack "placed"), the printers will have to be kept adjacent to, but outside the rack, potentially causing space/arrangement headaches.
• More important, if your printer is an impact-type printer (such as a dot matrix or line printer) that generates vibration, believe me, you DON'T want it anywhere NEAR your server - or more specifically, your hard disks! Of course, this is next to impossible with a 5 foot cable.
• Finally, attaching a printer directly to a server means users must walk to the printer to pick up their output. Granted, they have to do this anyway, and in small areas, this may not be a problem. The problem is allowing users anywhere near the server. Network Administration 101 preaches that servers should be kept in a locked room, away from unauthorized users. Meanwhile, in a large company with an access- controlled computer room, this type of print serving is even less feasible. And of course, the larger the company, the farther away the print server(s) will be from users, even if access control wasn't an issue.