Printing with a Novell Server

To set up a Queue:

1. Type Pconsole after logging in as a Supervisor
2. From the Available Options, select "Print Queue Information"
3. From the Print Queues box, hit the insert key at the "New Print Queue Name" prompt; enter the name you want for your print Queue, and hit the return key. To exit Pconsole, use the esc key.

To use atps (AppleTalk Print Services):

edit autoexec.ncf

At the end of that file, type:

load appletlk net=5801 zone={"zonename "}
(Note: zonename should be replaced by your ethernet Zone.)

Load ATPS -v

Then save the file and exit.

From the same directory,

edit ATPS.cfg

At the end of that file, type:

-P "PrinterName " -z "Zone " -o "QueueName " -g -e

As an example, to set up a printer with the name "SelectPress 600", ethernet zone "SQA" and queue name "SelectPress_600", type:

-P "SelectPress 600" -z "SQA" "SelectPress_600" -g -e

To contact Novell, call 1-800-453-1267.

Setting up a Novell server to print via AppleTalk

Installing AppleTalk and the print server is necessary to connect printers using AppleTalk and make these accessible to DOS, Windows, OS/2 or Unix clients (whatever is presently connected.) The procedure for NetWare 3.1x is briefly outlined in the following. The exact details will vary from site to site, so please consult your Novell manual.

1. Install the NetWare for Mac product:
   Insert the installation disk in the server's floppy drive and load the NetWare installer (load install). Select Product Options from the menu, and hit the INS key to install the new product. You will be prompted to edit the startup.ncf file, make sure it includes:

   load mac.nam

   set minimum packet receive buffers=150 (or more depending on memory available and number of network boards.)

   Change the autoexec.ncf file to include:

   set maximum packet receive buffers=250 (or more)

2. Add a new frametype to autoexec.ncf:
   Load your existing network drivers (e.g. SMCPLUS.LAN, NE3200.LAN, 3COM507.LAN) once more with the appropriate frame type for Appletalk:

   load drivername, port or slot frame=ethernet_snap name=instancename

   Instancename is any unique name, repeat above for all boards/segments that need AppleTalk.

   Examples:
   

   load ne3200 slot=4 frame=ethernet_snap name=Etalk
load smcplus port=320 int=5 frame=ethernet_snap name=bob

   Dayna LocalTalk network boards may also be used, as well as token ring boards.

3. Add AppleTalk to the autoexec.ncf file:
   

   load appletlk net=5000-5000 zone={"Internal zone name "}

   Include brackets and quote marks when typing, the internal zone name can be anything you choose.

   bind appletlk to instance-name net=100-109 zone={"Zone name "}

   Repeat the bind statements for all boards with AppleTalk.

   The above numbers are examples that you may use if you do not have any AppleTalk routers on your network. Note that EtherTalk phase 2 netnumbers are always a range, e.g. 100-109. If one or more AppleTalk routers are present on the network, make sure that the zone names and net ranges are the same on all joint segments and that different segments do not use the same range. You may also set the Novell server up to learn routing by using this syntax:

   load appletlk net=0-0
bind appletlk to instance-name net=0-0

   Do not use this "seed routing" if the AppleTalk router is not always present.

4. Add AFP (if needed) and AppleTalk Print Service to the autoexec.ncf file:
   

   load afp (not needed if no Macintoshes are to be served)
   load atps -d volume:directory -v

   Specify above the volume and directory you want to use for spooling. Make sure this is on a volume with enough disk space available. How much depends on the size of the print jobs and how many jobs will normally be queued up at one time.

5. Change the atps.cfg file:
   Change the atps.cfg file (this is a new file) to include one line for each printer:

   -p {"Printer name "} -z{"Zone name "} -o {"Queue name "} -e -g

   If you do not know your printer's AppleTalk name yet, use a dummy name and change it later. The zone name is the name defined for the network under (3) above. When naming the queue remember that the queue name as seen by a PC will be all capital letters and no spaces.

   When ATPS is loaded, it will create the queues automatically. (Do not use the pconsole utility to change attributes for the ATPS print server object. The pserver NLM is not necessary to use ATPS, but may be used in addition to ATPS if you also have a parallel port or remote IPX printers. See the manual on how to give Mac users access to Pserver queues.)

6. Add Macintosh name space:
   For all volumes that Macintoshes will access, do the following once (mac.nam has to be loaded):

   mount volumename (if not mounted)
   add name space Macintosh to volume volumename

7. Restart the server:
   Check your typing, save startup.ncf, autoexec.ncf and atps.cfg, bring down the server and reboot.
8. Verify operation and change printer names (if necessary):
   Queues should be created automatically if everything else is OK. ATPS has it own screen on the server, check this to see that the printer(s) are found. If the printer name is not correct, load atcon.nlm and use the lookup service to check the printer name, then edit the atps.cfg file to include the proper name (load install and select Product Options, then select NetWare for Mac to get to atps.cfg.)

   Do not give any printer a name that begins or ends in a space (the printer's name can be changed using the LaserWriter Utility on a Mac, or using a PC-based downloader over a serial port.)

   The queues can be used by any PC or Mac at this point. If Macs are to be connected, connect them to network cabling, change the Mac's Network Control Panel to EtherTalk, and use the Notify init (put in System Folder to receive messages from the server) and the NetWare DA (gives access to view and hold print jobs) are the most useful.

   The atcon.nlm is useful for checking that the AppleTalk connections are OK, checking for router conflicts and looking for AppleTalk devices. Use the monitor.nlm to monitor the number of packet receive buffers used, if the maximum value is reached this indicates that both the minimum and maximum values should be increased for better performance.