The method used to establish a printer on a client computer dictates the configuration of the client computer in relation to the printer. The following table details the various methods.
Connection Method | Windows NT Sending Software | Required Network Protocols | Windows NT Receiving Software |
Connect to network printer in Add Printer wizard | Spoolss.exe | TCP/IP, NetBEUI, NWLink | Spoolss.dll |
Create local printer in Add Printer wizard and Print To options for a UNC device | Windows NT Workstation Service (NetBIOS redirector) | TCP/IP, NetBEUI, NWLink | Windows NT Server service |
Create local printer and Print To options for an LPR port | LPR (Lpr.exe) Port Print Monitor | TCP/IP | TCP/IP (LPD) Print Service |
Create local printer using Chooser and Print To options for an AppleTalk device | AppleTalk Print Monitor | AppleTalk | Services For Macintosh |
Notice that only Windows NT and Windows 95 client computers can actually "connect to" a network printer served by a Windows NT print server. When a Windows NT or Windows 95 print client initiates a print request, the required printer driver is downloaded from the Windows NT print server if it is not already on the client's hard disk. All other client computers must "create" the printer—that is, they must install the printer driver directly on their hard disks, specify a port, name the printer, and so on.
Windows NT and Windows 95 print clients can also create a remote printer served by a Windows NT print server. Each method has advantages and disadvantages. Connecting to a remote printer is easier and faster than creating one. If the Windows NT client has connected to a printer, the print job doesn't spool on the client machine, so no spool options are available. (Windows 95 clients always spool locally and again remotely.) The "connected" client also cannot queue print jobs locally. Creating a printer gives the user more control, but that control is not always needed.