M305 Print Server Quick Installation and … 5 Manual Printing with FTP’s PC/TCP B-24 Printing...

manual4.book Saturday, January 16, 1999 4:26 PM

M305 Print ServerQuick Installation and Configuration Guide

Manual Version 1.0For firmware version 1.0

Microplex Systems Ltd.8525 Commerce Court

Burnaby, B.C. V5A 4N3http://www.microplex.com/

P/N 79-305-100


Copyright 1991-1999 Wyndham Technologies Inc.All rights reserved.

No patent liability is assumed with respect to the use of the information contained herein. While every precaution has been taken in the preparation of this manual, Microplex Systems Ltd. assumes no liability for errors contained herein or for incidental or consequential damages in connection with the performance or use of this material.

Copyright 1996, Novell, Inc. All rights reserved. All other product names are trademarks of their respective manufacturers or providers.

This manual was written, illustrated, and produced using FrameMaker workstation publishing software.

Rev: 01/99

Printed in Canada.


TABLE OF CONTENTSMANUAL OVERVIEW ............................................... 1PDF File Index.....................................................................1Documentation Conventions................................................2

M305 INTRODUCTION.............................................. 3Overview..............................................................................3What is the M305?...............................................................3How Does the M305 Work? ................................................4Product Features ..................................................................5

M305 INSTALLATION............................................... 7Overview..............................................................................7Unpacking the M305 ...........................................................7Attaching to the Network.....................................................8

CONFIGURATION TOOLS...................................... 15Overview............................................................................15Two-Part Configuration .....................................................15Available Tools..................................................................15Troubleshooting Tips .........................................................21

WINDOWS CONFIGURATION................................ 23Overview............................................................................23Environment Description...................................................23M305 Configuration ..........................................................24Troubleshooting Tips .........................................................29

UNIX CONFIGURATION ......................................... 31Overview............................................................................31Environment Description...................................................31M305 Configuration ..........................................................32Host Configuration ............................................................34Troubleshooting Tips .........................................................35

NOVELL CONFIGURATION ................................... 39Overview............................................................................39Environment Description...................................................39M305 Configuration ..........................................................40Host Configuration ............................................................41Troubleshooting Tips .........................................................48

APPLETALK CONFIGURATION ............................ 51

V1.0 3


Overview............................................................................51Environment Description...................................................51M305 Configuration ..........................................................52Host Configuration ............................................................52Troubleshooting Tips .........................................................53

M305 REFERENCE PAGES.................................... 55Overview............................................................................55M305 Naming Scheme ......................................................55M305 Command Shell .......................................................56Back to Factory Defaults ...................................................62Firmware Upgrades............................................................63

GETTING HELP....................................................... 65Help Methods Available ....................................................65Repair Procedure................................................................66

M305 SPECIFICATIONS ......................................... 71Hardware Specifications ....................................................71Software Specifications .....................................................75

GLOSSARY ............................................................. 77INDEX ...................................................................... 83Appendix A - More on Windows ......................... A-1Overview......................................................................... A-1M305 Configuration ....................................................... A-3General Workstation Configuration................................ A-9Windows 95/98 Workstation Setup......................................................... A-10Windows NT Workstation Setup......................................................... A-12Windows Troubleshooting............................................ A-15

Appendix B - More on Unix ................................. B-1Overview..........................................................................B-1M305 Configuration ........................................................B-2Host Configuration Overview..........................................B-9Direct Printing Without the Spooler ................................B-9Printing Via the Spooler ................................................B-10Manual System V Host Setup ........................................B-13Manual LPR/LP Host Setup ..........................................B-16Printing from AIX..........................................................B-22

4 V1.0

42525631

-1-21117

-1-2

-1-2

E-5-71

-14212525

-1-2

F-2-3-7-7

-1-2-3


Manual Printing with FTP’s PC/TCP ............................B-2Printing Using FTP Daemon..........................................B-Direct Socket Printing....................................................B-Device Printing - Microplex’s NPD ..............................B-2Troubleshooting .............................................................B-

Appendix C - More on Novell .............................. C-1Overview..........................................................................CM305 Configuration ........................................................CHost Configuration ........................................................C-Troubleshooting .............................................................C-

Appendix D - More on AppleTalk ........................ D-1Overview......................................................................... DM305 Configuration ....................................................... D

Appendix E - Extra Features/Additional InformationE-1Overview..........................................................................EPrint Server Architecture .................................................EGeneral Options ...............................................................M305 Security..................................................................EPrinter Monitoring and Logging ....................................E-1FTP Daemon ..................................................................EManaging with SNMP ...................................................E-Troubleshooting .............................................................E-NCSA.............................................................................E-

Appendix F - More on Specifications ..................F-1Overview.......................................................................... FNetwork Connectors ........................................................ FPower Socket ...................................................................Parallel Port (PRN) .......................................................... FM305 LEDs...................................................................... FVariable Definitions......................................................... F

Appendix G - More on Commands ..................... G-1Overview......................................................................... GCommand Shell Overview.............................................. GComplete Command List ................................................ G

V1.0 5


6 V1.0

MANUAL OVERVIEW

-

manual4.book Page 1 Saturday, January 16, 1999 4:26 PM

MANUAL OVERVIEW

This manual describes the installation and configuration of an M305 on your network. It describes a basic setup for each supported network environment. For more detailed information about configuration and management, please see the Portable Document Format (PDF) files available on the CD ROM supplied with the M305 or from the Technical Support section of Microplex’s Web site, “http://www.microplex.com/”.

PDF File Index

Table 1 lists the PDF files that are available on the CD ROMincluded with your unit. Please refer to these documents if you can’t find what you’re looking for in this guide.

Table 1: Microplex PDF Files

File Name Description

windows.pdf Appendix A - Print setup for Windows environments.

unix.pdf Appendix B - Step-by-step manual configuration instructions for Unix environments.

novell.pdf Appendix C - RPRINTER configura-tion and other Novell information.

apple.pdf Appendix D - Additional configuration for AppleTalk environments.

extra.pdf Appendix E - Details about the M305’sadditional features such as printer logging.

V1.0 1

MANUAL OVERVIEW


Documentation Conventions

The document conventions used in this manual and the appendices are as follows:

• The Courier font in boldface indicates commands that you type.

$ ping ftp.microplex.com

• Regular Courier font indicates displayed results.

ftp.microplex.com is alive

• Example names and numbers described in text are bold.

sends data to the M305 named spike...

The model directory...

• Variable values are shown in italics both in command syntax, output, and in text. Italics also add emphasis.

ping ipname

ipname is alive

Please enter the ipname at the prompt.

Make sure you first contact...

specs.pdf Appendix F - Additional specificationsfor the M305 hardware.

command.pdf Appendix G - In depth look at the M305’s internal command shell. (for commonly used commands, see Com-mon npsh Commands on page 58.)

Table 1: Microplex PDF Files

File Name Description

2 V1.0

M305 INTRODUCTION

e

e

s

e

le


M305 INTRODUCTION

Overview

The purpose of this chapter is to acquaint you with the M305’s architecture and special features.

What is the M305?

The M305 10/100 Pocket Print Server allows you to locatyour printer anywhere on a 10 Base-T or 100 Base-T LANrather than attaching it directly to a host system. After fol-lowing some simple configuration steps, the printer can bsimultaneously shared with users on Unix (TCP/IP), Win-dows (NetBIOS over TCP/IP), Novell (IPX), or AppleTalk (EtherTalk) networks. Multiple users and multiple protocolare supported simultaneously.

Note: The M305 is compatible with most printers with a Centronics parallel interface.

The M305’s key physical components are:

• a 10/100 network interface connector to connect to thnetwork,

• one parallel port,

• Flash memory to store firmware and user-configurabsettings,

• SDRAM.

V1.0 3

M305 INTRODUCTION

ti-

g

r-


How Does the M305 Work?

Print Path

The print path is the path data takes when the host sends a job to a printer through the M305. This print path can be divided into the three components (refer to Figure 1).

Figure 1: Print Path Components

Host The host sends the job to one of four pre-defined destinations (e.g. d1prn) on the print server, not directly to the I/O port.

Print Server The job passes through the destination’s associated model (e.g. m1) for optional pro-cessing and then continues through the desnation’s associated logpath (e.g. l1) where logging information is recorded. The data then ends up at the destination’s associatedI/O port, prn.

Printer The data passes from the print server’s I/O port to the attached printer for output.

There are four destinations on the M305, with each havinan associated model and logpath. The model determines if any extra data processing (e.g. ASCII to PostScript convesion) needs to be done and the logpath determines whether job logging (e.g. user ID) or printer errors need to be

4 V1.0

M305 INTRODUCTION

d


reported. A model or logpath can be associated with more than one destination. Refer to Figure 17 on page 56

Product Features

The M305 offers an extensive list of features including:

• Built-in HTML forms for easy cross-platform configu-ration with any web browser;

• Waldo, the utility for automated TCP/IP configurations(included on CD ROM supplied with the M305);

• Ezsetup utility for automated Unix print configurations(included on CD ROM);

• MPS utility for error-free printing in Windows 95, Windows 98 and Windows NT environments (includeon CD ROM);

• a detailed and easy-to-use command shell, “npsh”;

• multilevel configuration security through passwords, permission levels, and access lists;

• numerous printer logging methods (e.g. automatic Email) to record printer errors and usage;

• remote management through Telnet sessions, “rsh/rcmd/remsh” commands, SNMP, and predefined log methods;

• extensive built-in troubleshooting tools;

• built-in “telnet” and “ping” clients;

• ability to disable protocols and destination services allows memory usage to be configured;

• multiple destinations for versatile printer manipulationand distinct print setups;

• header and trailer strings to instruct printers on tray selection, font, pitch, simplex/duplex, etc.;

V1.0 5

M305 INTRODUCTION

-


• autosensing of job format for ASCII to PostScript conversion or to automatically switch printer emulations;

• flexible naming conventions;

• Flash memory upgrades over TCP/IP networks;

• multiple speeds on the parallel port for additional printer compatibility;

• simultaneous printing on all supported protocols.

6 V1.0

M305 INSTALLATION

-


M305 INSTALLATION

Overview

This chapter discusses the preparation and installation steps necessary to use the M305 on your network.

Unpacking the M305

Upon receiving the M305, check the packaging for any damaged or missing pieces (refer to Table 2, “M305 Packing List,” ). Immediately report problems to the shipping company or vendor. If everything is in order, fill out the Warranty Registration Card:

Registration Options

Fill out the Warranty Registration Card included with your product and mail it to Microplex.

Fax the card to Microplex at +1 604 444-4239.

Fill out an on-line version on our Web site at: “http://www.microplex.com/”.

.

Table 2: M305 Packing List

Print Server

• M305

• Power Supply

Documen-tation

• Quick Reference and Installation Guide (this guide)

• CD ROM with PDF files and software

V1.0 7

M305 INSTALLATION


Attaching to the Network

Site Requirements

Prepare to install the M305 in a clean, well-ventilated envi-ronment protected from extremes of temperature, humidity, mechanical shock, or vibration. Provide enough space at the rear of the unit for Ethernet cable connections.

Prepare to install the M305 within four meters (13 feet) of a grounded 115 or 220 VAC outlet. Power is supplied to the M305 from an external transformer through a two-meter (six-foot) output cord to a 6 position mini din. The external transformer connects through a two-meter (six-foot) line cord to a 3-prong 115 or 220 VAC outlet.

Network Connections

The M305 provides a 10/100Base-T RJ45 (UTP) connector. Refer to Figures 2 and 3 for a view of the front and rear of the M305.

Software • Included on the CD ROM are:

• Waldo - TCP/IP configuration tool

• MPS - Microplex printing solution for Windows 95, Windows 98 and Windows NT environments

• EZSetup - UNIX configuration tool.

• MPAdmin - Novell NWAdmin snap-in configuration tool.

Packaging • Shipping Box

• Cardboard Insert

Table 2: M305 Packing List

8 V1.0

M305 INSTALLATION

). nd-


Figure 2: M305 Front View

Figure 3: M305 Rear View

Printer/ Port Connections

One printer may be attached via the M305’s 36-pin male Centronics connector (with an IBM PC compatible pinoutThe port can be configured with various parameters depeing on the attached printer. These parameters include:

• cen Centronics mode. Used with older impact printers (e.g. dot matrix or line printers);

• pc default mode. Will work with most printers;

• slow for slower parallel interfaces that need a slower transfer rate;

V1.0 9

M305 INSTALLATION

-

m-

e


• fast for high-performance parallel interfaces that can handle an increased transfer rate (like the HP 4 and 5 series printers);

• bb bit bucket (for simulating an attached printer even if one isn’t attached);

• nibble reverse data transfer mode for printers with bidirectional communications capability (used only withback channel enabled).

Printing Test Pages

Use the test page feature to test the M305 and printer comunications without a network connection. To output testpages:

1. Power off the M305 and the printer and disconnect thnetwork connector.

Note: If the print server is connected to the network with link integrity, this procedure will force it into download mode instead of printing a test page.

2. Set Dipswitch 1 and Dipswitch 2 to the “on” position (i.e. down).

3. Power on the printer then power on the M305. The M305 will generate two test pages automatically.

4. When done, power off the M305 then power off the printer. Set Dipswitch 1 and Dipswitch 2 to the “off” position (i.e. up) again for normal operations.

Connecting to the Network

To attach the M305 to the network as illustrated in Figure 4 on page 11, you will need to:

1. Connect the M305 to the network via the appropriatenetwork connector.

2. Attach the unit to the parallel port of the desired

10 V1.0

M305 INSTALLATION

’s e

-r

on


printer. Ensure that the printer is turned off when you plug in the print server.

3. Turn the printer on and unpack and plug in the M305power supply. The connector plugs into the back of thM305.

Watch the lights on the front panel of the device as they cycle through the power-on self test. When the test is complete, the STAT LED will flash once per second (twice pesecond if there is no IP address configured).

Figure 4: Physical Setup

Dipswitches

On the back of the M305 you will find two dipswitches labeled 1 and 2. Their functions are explained in Table 3 page 12:

M305

Printer

Network

Power

V1.0 11

M305 INSTALLATION


Table 3: Dipswitch Settings

Dipswitch

1 2 Comments

off off Normal operation. With both dipswitches in the “off” position, the unit will boot up using the settings in Flash rather than the default set-tings. Dipswitch 2 is in the “off” position from the factory so that the new settings that you store will be used.

on off Factory default settings. With the dipswitches in this configuration, the unit will boot up and all settings stored in Flash will be erased except the Ethernet address and key value.

off on Default IP. With the dipswitches in this configuration, the unit will boot with factory default settings. How-ever, the stored settings in flash are intact. Setting dipswitch 2 to “on” will not clear any settings that you have stored in Flash. It simply boots the unit in a different state with the settings in Flash temporarily ignored.

12 V1.0

M305 INSTALLATION


on on If the unit is connected to a network with link integrity and then reset to MOS, a download will be forced. If the unit is not connected to a net-work, it will print a test page.

Table 3: Dipswitch Settings

Dipswitch

1 2 Comments

V1.0 13

M305 INSTALLATION


This page intentionally left blank.

14 V1.0

CONFIGURATION TOOLS

et-

to-d

ot

h a in


CONFIGURATION TOOLS

Overview

This chapter outlines all of the configuration tools available to you when using an M305.

Two-Part Configuration

When talking about configuration, it’s important to under-stand that there are two parts to a M305 setup:

1. Configuring the M305 so that it can be seen on the nwork. This involves network-related settings (e.g. anIP address within TCP/IP environments) configured through the built-in command shell, npsh.

2. Configuring a host with a new printer so it knows howto send data to the M305. Just being able to see the print server on the network doesn’t mean you can aumatically print to it. A host has to be told where to senthe data.

Note: There are some network environments that do nrequire any network settings to be configured onthe M305. However, all network setups require configuration on the host end.

Available Tools

HTML Forms

The M305’s settings can be configured over TCP/IP througa standard Web browser. The M305’s Web pages provideuser-friendly way to access some of the commands built to the print server.

V1.0 15

CONFIGURATION TOOLS

net


To access the M305’s home page, you will need to:

1. Make sure the print server has an IP address and submask so it is recognizable on your TCP/IP network.

2. Ensure your network station can successfully “ping” the M305 over the network.

3. Direct your Web browser to the Uniform Resource Locator (URL) “http://M305IPaddress” (e.g. “http://192.168.11.9”).

The M305’s HTML structure is divided into several menusas shown in Figure 5.

Figure 5: M305 HTML Structure

Note: On-line help is available for all HTML pages.

Index/Home

Network

Home Page Menu

Print Path

I/O Port

Administration

System

I/O Port

Network

About Configuration Status Help

16 V1.0

CONFIGURATION TOOLS


Waldo

Overview

Since TCP/IP is relied upon for Windows/UNIX printing, the M305 must be configured with an IP address and subnet mask before it can work on the network

Waldo is a tool for discovering, monitoring, and configuring Microplex print/frame server devices on a TCP/IP network. The program is a Java stand alone program.

This chapter discusses the M305’s configuration on a TCP/IP network using Waldo, detailing a complete setup includ-ing:

1. Identifying the M305 on the network using TCP/IP as the underlying protocol.

2. Configuring the M305 with its mandatory TCP/IP set-tings (i.e. IP address and subnet mask).

Additional settings like routing entries can also be config-ured allowing for communications across subnets. Once Waldo is up and running, select Help Topics from the help menu for more detailed information about Waldo.

Environment Description

Waldo requires the JavaTM Runtime Environment in order to work. JavaTM Runtime Environment (also known as the Java Runtime or JRE) consists of the Java virtual machine, the Java platform core classes, and supporting files.

Waldo Configuration

Mandatory

1. The Java Runtime Environment from Sun. The html link is http://java.sun.com/products/.

V1.0 17

CONFIGURATION TOOLS


2. You must have the TCP/IP protocol installed and con-figured on your workstation.

Installing Waldo in Windows

To install Waldo on a windows workstation, you will need to:

1. Insert the CD ROM supplied with the M305 into the drive.

2. Go to the Waldo directory and find the "setupex.exe" file.

3. Double click on this to load the InstallShield Wizard.

4. Answer the prompts throughout the wizard.

5. Once the install process is complete, you will be prompted to view the "ReadMe" file. Select "Yes" to read this and when done, close the file.

6. Find the new Waldo program group and double click on the "Waldo" icon to load the program.

7. Click on "Search…".

8. At the "Discover Devices" dialog box, select "local" and click on "OK".

Note: Click on "Add.." to find a device on another sub-net.

9. The main dialog box will now build up a list of Microplex devices. This process will take a minute ortwo to find the devices on the network. Click on "StopSearching" after the device has been found. Figure 6 shows a sample screen.

18 V1.0

CONFIGURATION TOOLS

ry

t--


Figure 6: Waldo Main Screen

10. Select the M305’s ethernet address from the list box and press "Assign IP…".

11. At the "Assign IP" dialog box that displays next, fill inthe IP address and subnet mask for this M305.

Note: You can also assign a default router/gateway entwithin this dialogue box allowing your M305 to communicate across subnets.

12. Click "Assign" when done to assign these TCP/IP setings to the M305. Waldo will then display on a separate dialog box the status of its progress.

13. After successfully assigning the settings you will seethe M305 with its new IP address in the device list.

V1.0 19

CONFIGURATION TOOLS

r l

r s


Ezsetup

This is a Unix shell script that helps configure M305 set-tings and host print setups. It’s compatible with all Unix fla-vours and has a Main Menu similar to Figure 7.

Figure 7: Ezsetup Main Menu Screen

Configuration Alternatives

Besides the HTML forms and software provided by Microplex, the M305’s internal command shell, npsh, canalso be reached using these common methods:

Telnet A TCP/IP command that helps configure M305 settings remotely. A TCP/IP host starts a Telnet session with the print serveand logs in to the device’s command shelto alter and view settings.

Example:

telnet 192.168.11.9

Remote Shell (e.g. “rsh”, “ rcmd”, “ remsh”) A TCP/IP command that helps configure print servesettings remotely. A TCP/IP host uses thicommand to remotely execute a single command on the M305.

20 V1.0

CONFIGURATION TOOLS

y

g

t-


Example:

rsh spike list prn

This command remotely executes the npsh command, “list prn” on the M305 named spike.

Troubleshooting Tips

M305 Won’t Talk on the Network - Waldo Error Messages

• Unable to assign temporary IP. The address is alreadin use.

• Have you assigned a IP address that is not beinuse by another device?

• Unable to assign temporary IP. The device is not responding. The network may be down, or an invalidIP address has been used.

• Is the IP address that you used valid for your nework?

HTML Configuration Forms Won’t Display

• Can you “ping” the M305 from your workstation? If not, please refer to M305 Won’t Talk on the Network on page 29.

• Have you used the correct URL for the M305’s homepage? It should be “http://M305IPaddress” (e.g. “http://192.168.11.9”).

V1.0 21

CONFIGURATION TOOLS



22 V1.0

WINDOWS CONFIGURATION

p

-

-

-

r -



Overview

This chapter discusses the M305’s support for Windows 95/98 and Windows NT, describing a complete Windows setuincluding:

1. Identifying the M305 on the network using TCP/IP asthe underlying protocol.

2. Configuring the M305 with its mandatory TCP/IP settings (i.e. IP address and subnet mask).

3. Configuring a new printer on the Windows station.

Please see Appendix A - More on Windows (the PDF file called windows.pdf) for more information about other Windows environments.


The M305 supports network printing under Windows environments by utilizing TCP/IP. There are two common set-ups for printing in a Windows environment: setup a printeon an NT server to be shared by Windows 95/98 and Windows NT clients, or have each Windows station print directly to the M305. Figure 8 outlines these two types of setups.

V1.0 23



Figure 8: Windows Integration

M305 Configuration

Mandatory

Since TCP/IP is relied upon for Windows printing, the M305 must be configured with an IP address and subnet mask before it can be seen on the network.

Optional

Additional settings like routing entries can also be config-ured, allowing communication across subnets.

Configuration Steps

To configure an IP address and subnet mask on your M305, Microplex recommends the use of their TCP/IP configura-tion utility called Waldo. Waldo is described in detail on page 17. Once you have the TCP/IP settings stored on the M305, the next section will help you setup a new network printer on your Windows station.

Host Configuration

There are a number of possible ways to configure a printer in a Windows environment. These include:

Win95 NT Server

Win95

Win95

M305

Printer

IP Router

Win95Win95

24 V1.0



1. Direct TCP/IP printing with MPS (Microplex Printing Solution).

2. NetBIOS over TCP/IP (i.e. browsing the Microsoft Windows Network).

3. LPR (Berkeley’s Line Printer Protocol which uses TCP/IP to transfer data to the print server’s built in Line Printer Daemon).

Note: Which method you choose depends entirely on your preference and what is available with your particular Windows software and operating sys-tem. Microplex recommends the use of MPS (Microplex Printing Solution) for Windows NT and Windows 95/98 printing environments.

The key advantage to using MPS is that it allows true peer-to-peer printing in a Windows environ-ment. Using MPS ensures that your connection to the print server remains open indefinitely so that print jobs won’t be lost due to the connection tim-ing-out, as can occur in a NetBIOS setup.

The following sections describe how to configure a printer on a Windows NT 4.x or Windows 95/98 workstation using MPS. For additional information about printing with other methods, or in other Windows environments, please refer to Appendix A - More on Windows (the PDF file called win-dows.pdf).

Installing MPS (Microplex Printing Solution)

To install MPS on a Windows workstation, you will need to:


2. Go to the MPS directory, and find the "Setup.exe" file.


V1.0 25


e


4. Answer the prompts throughout the wizard and select "Yes" to restart your computer at the end.

5. Once your computer is rebooted, MPS should be suc-cessfully installed.

Windows 95/98 MPS Setup

To configure a new printer to print directly to the M305 on a Windows 95/98 station, you will need to:

1. Install MPS if you have not already done so.

2. Select "Printers" from the "Settings" sub-menu on the "Start" menu.

3. Select a printer that you want to use with MPS and click on the right mouse button to bring up a sub-menu.

Note: MPS will only work with an existing printer under Windows 95/98. If you don’t have an exist-ing printer that you can alter, create one now (use any port settings you like since they will be changed in the following steps).

4. Select "Properties" from this menu to display the cur-rent settings for this printer.

5. Click on the "Details" tab to display the printer’s port settings.

6. Click on the "Add Port…" button.

7. At the "Add Port" dialogue that displays, click on the radio button labeled "Other".

8. Click on "Microplex TCP/IP Printer Port" from within this "Other" list box.

9. Click on "OK", you should see a dialogue like the onshown in Figure 9.

26 V1.0



Figure 9: Add Port Dialog

10. In the "Host Name" field, type in the DNS host name or IP address of the M305 (e.g. 192.168.11.9).

11. In the "Port Number" field, type in the port number of the destination you are using (i.e. 4400 is the default port number for d1prn).

12. Click "OK" to create an MPS port.

13. Make sure the new MPS Port is selected in the "Print to the following port" field. It should have the name MPLX::<Host Name>:<Port Number>; for example:MPLX::192.168.11.9:4400

14. Click on "OK" to close this printer’s properties win-dow.

You now have a new network printer which relies on MPS to print remotely to a printer attached to the M305.

Windows NT 4.x MPS Setup

To configure a new printer to print directly to the M305 using MPS on a Windows NT 4.x station, you will need to:

1. Install MPS if you have not already done so.

2. Select "Printers" from the "Settings" sub-menu on the "Start" menu.

3. Double click on "Add Printer" icon.

V1.0 27


r

il-

ld


4. Select the "My Computer" radio button in the "Add Printer Wizard" that loaded, and click on "Next >".

5. Click on "Add Port…" to bring up the "Printer Ports" dialogue box.

6. Select "Microplex TCP/IP Printer Port" from the "Available Printer Ports" list, and then click on the "New Port…" button to bring up a dialogue box similato the one found in Figure 10.

Figure 10: Add Port Dialogue

7. In the "Host Name" field, type in the DNS host nameor IP address of the M305 (e.g. 192.168.11.9).

8. In the "Port Number" field, type in the port number ofthe destination you are using (i.e. 4400 is the defaultport number for d1prn).

9. Click "OK" when done specifying these two fields.

10. Make sure the new MPS Port is selected in the "Avaable ports" list box. It should have the name MPLX::<Host Name>:<Port Number>; for example: MPLX::192.168.11.9:4400

11. Click on "Next >" and continue the setup as you woufor any other printer.

You now have a new network printer which relies on MPSto print remotely to a printer attached to the M305.

28 V1.0


ur is

a

ig-

er y

-



M305 Won’t Talk on the Network

• Have you assigned it a unique and valid IP address which corresponds with the other IP addresses on yonetwork? For example, are you sure no other deviceusing this IP address?

• Are you sure you are trying to talk to the M305 from Windows station on the same subnet? Currently, the print server can only be seen locally unless you confured a routing entry earlier on.

• If you look at the front of the M305, is the STAT LED flashing once a second or is it quicker than that? A slower, once per second rate tells you that the print server is in fact configured with an IP address. A fastrate says it doesn’t recognize its IP address; you maneed to try the configuration process again.

• Have you confirmed the network connection to the M305 is working correctly? Trying different network cables and locations will help narrow down the prob-lem.

MPS Error Messages

• Unable to get information about host <HOST>. Host '<HOST>' could not be found.

• Is the DNS name that you used valid?

• Is your DNS server up and running?

• Is the DNS server setting configured on the workstation running MPS correct?

• Can you "ping" the M305 from your Windows workstation? If not, please refer to M305 Won’t Talk on the Network on page 29.

• Failure to connect to host <HOST>. Connection refused by host on port <PORT#>.

V1.0 29


t-s

st

e - to - If

nt-

t-

-


• Is the IP address you assigned valid for your nework? If a DNS name was used, is the IP addresassigned to this name valid for your network?

• Can you "ping" the M305 from your Windows workstation? If not, please refer to M305 Won’t Talk on the Network on page 29.

• Are you using the correct port number? Issue a lipserver command on the M305 to find out what port numbers are assigned to what destinations.See Appendix G - More on Commands (the PDFfile called command.pdf) for more information.

Printer Errors When Printing or No Output

• Is a large job currently printing (and taking up all of thprinter’s resources)? Usually when printing from Windows 95 stations, a busy printer can cause Windowsdisplay a printer error message. This is because Windows 95 demands immediate printer attention ratherthan holding the data until the printer is ready again. this is a frequent problem, it is better to use a centralspooling station like an NT server or use MPS.

• Have you tried restarting the spooler under Control Panel:Services? Sometimes this is needed to get priing going.

Note: As a last resort, you may want to try re-booing the Windows station. Sometimes this is the only option to completely clear this situation. Usually the M305 has nothing to do with this problem so it can be left alone.

30 V1.0

UNIX CONFIGURATION


UNIX CONFIGURATION

Overview

This chapter describes a complete Unix setup including:

1. Configuring the M305 with its mandatory TCP/IP settings (i.e. IP address and subnet mask).

2. Configuring a new printer on the Unix station.

For additional information about Unix environments, please see Appendix B - More on Unix (unix.pdf).


The M305 supports network printing under various TCP/IP environments including all flavours of Unix. Printing can come from multiple hosts directly or through central spool-ing machines. Figure 11 illustrates this for you.

Figure 11: Unix Integration

PC

PC

PC

M305

Printer

XTerm

XTerm

SparcStationSunOS 4.1.1

IP Router

Solaris

OSF/1

IRIX

Ultrix

SCO HP/UX

Linux

31

UNIX CONFIGURATION

-


M305 Configuration

Mandatory

Since TCP/IP is used, the M305 must be configured with at least at an IP address and subnet mask before it can be seen on the network.

Optional

Additional settings, like routing entries, can also be config-ured to allow communication across subnets.

Configuration Steps

To configure an IP address and subnet mask on your M305, you will need to:

1. Log in as root or superuser on your Unix host.


3. “cd” to a directory with at least three megabytes of free space.

4. Transfer the compressed tar file from the CD ROM onto the host.

tar xvf /dev/devicename

where devicename is usually “fd0” for a CD ROM.

5. Uncompress this file.

uncompress npdist.tar.1.Z

6. Untar this file.

tar xvf npdist.tar.1

A list of files will display and scroll up the screen. Several files and subdirectories are created including a copy of Ezsetup, the Unix script used for print serverand host configuration.

32

UNIX CONFIGURATION

s

n-


7. [Optional] Assign an IP address and host name to the M305 in the host table (/etc/hosts, host NIS map, or DNS name tables).

8. Run Ezsetup from the command line. Follow this syn-tax for most Unix operating systems:

./ezsetup

For HP/UX, use:

ksh./ezsetup

9. Answer the prompts that appear (so Ezsetup can learn about the Unix host it’s running on) and wait for the Main Menu to display. It will look like Figure 12.

Figure 12: Ezsetup Main Menu

10. Enter “1” for “Configure New Unit” since you want to configure an M305 with its TCP/IP settings.

11. Follow the prompts on each screen as Ezsetup stepthrough the configuration of the M305’s IP address, subnet mask, optional default router/gateway, and optional root and guest passwords.

Once you receive a message that this configuration com-pleted successfully, you should be able to communicate with the print server over the network. However, Ezsetupwill now automatically lead you into the second part of co

33

UNIX CONFIGURATION

on t r

t t t

s

t


figuration, “Configure Host Setup”, since you cannot printto a printer attached to the M305 until this is completed.

Note: If doing a print setup on a System V Unix host, avery simplistic Microplex interface script, “raw-sysv.if” will now be used, eliminating the need forany extra host binaries or compilation. This alsoholds true if you have a BSD-type Unix system but you want to use an interface script within theprintcap file rather than the standard LPD (or “remote printer”) method.

Host Configuration

The second half of Ezsetup helps configure a new printer your Unix host (just being able to talk to the M305 doesn’mean you can print to it). You also have to define a printeso the host knows where to send the data.

Ezsetup will continue prompting you for information abouyour host and printer. Answer these prompts until the hosconfiguration is complete. If you have any questions abouthe screens that display, please refer to Ezsetup Tips on page 34.

At the end, you will have a new network printer that senddata to a printer off of the M305.

Ezsetup Tips

• When asked for a print method, follow these rules:

1. If your Unix host uses the BSD print system, select “BSD Remote (LPD)” option.

2. If your Unix host is a System V derivative, selecthe “System V Interface Script” option.

34

UNIX CONFIGURATION

he

lly

r

s

c-

d


• When asked for a printer name, choose the name of the print setup on this host (i.e. the name entered in tprint command). For example, a print setup includingan HP III laser printer might be called “laser”.

• When asked for a destination, choose one of the four predefined destinations/queues on the M305. Normayou would choose “d1prn”.

• When asked which I/O port or port, choose “prn”.

• If asked to name an interface script, name it some-thing meaningful. For example, the HP III laser printeexample might have a script called “laser.if”.

• If using an interface script setup, keep in mind that a“dummy device file” or “device file” is an empty text file that stores data like spooler errors and request IDof the jobs printing. The name should also reflect theprint setup for easy identification. (e.g. “/dev/laser”)

• Near the end of Ezsetup’s “Configure Host Setup” setion, the script mentions carriage return insertion and formfeeds. Carriage return insertion is needed if Unixtext jobs are going to be printed through this setup. Formfeeds are needed only if printing Unix text jobs through a “BSD Remote (LPD)” setup.


Ezsetup’s Menus are Incomplete

• Are you running Ezsetup on an HP/UX host? If so, diyou remember to run Ezsetup with this command:

ksh./ezsetup

35

UNIX CONFIGURATION

,

.

es r

a

e


Ezsetup Stops With an Error

• Are you using a common operating system like SCOSolaris, or HP/UX? If not, you may have run into a compatibility issue. Please see Appendix B - More on Unix (unix.pdf) for manual setup instructions. These will guide you through a setup without using Ezsetup

M305 Won’t Talk on the Network

• Have you configured it with a unique and valid IP address which corresponds with the other IP addresson your network? For example, are you sure no othedevice is using this IP address?

• Are you sure you are trying to talk to the M305 from Unix station on the same subnet? The print server can only be seen locally unless you configured it with a routing entry.

• If you look at the front of the M305, is the STAT LED flashing once a second or is it quicker than that? A slower, once per second rate tells you that the print server is configured with an IP address. A faster rateindicates that the print server is not configured prop-erly. You may need to try the configuration process again.

• Have you confirmed that the network connection to thM305 is working correctly? Trying different network cables and locations will help narrow down the prob-lem.

Nothing Prints

• Can you “ping” the M305 from your Unix station? If not, please refer to M305 Won’t Talk on the Network on page 36.

• Is the M305 able to communicate with the attached printer? To test this, you can:

36

UNIX CONFIGURATION

, et re g

a

r nt

s il. it a-

top er f es.

ix l-


1. “telnet” to the print server (e.g. “telnet 192.168.11.9”) and log in as “root” (press ENTER for password).

2. Enter the command “start fox portname” where portname is “prn”.

3. Execute “stop portname” after starting the test.

This FOX test will send the same text line over and over to the attached printer.

• Is the job getting stuck in the Unix host’s queue? If socheck that the printer is ready to go. If the printer is sbut the job keeps getting stuck in the queue then theis a configuration error on the Unix station so creatina new print setup may be necessary.

• Is the printer’s console or control panel showing any activity (does it look like it’s receiving data?) If it is receiving data but nothing is printing, check to see if manual formfeed is needed. Also, ensure that the printer can support the type of job coming through. Foexample, a PostScript printer might not be able to pria non-PostScript job.

• Do all jobs fail or just certain ones? For example, jobfrom a certain application may be the only ones to faIf so, check the type of data it’s sending to make surematches the printer’s emulation and check the appliction’s printer configuration for mistakes.

Stair-Stepped Output

Stair-stepped output occurs when the output starts at the left of the page but every line thereafter starts a little furthto the right. It also refers to Unix jobs that print one line otext at the top of a page followed by a series of blank pag

This unique output will happen only with Unix text jobs if carriage return insertion is not incorporated into the print setup. The printer may be told to do a linefeed but the Unjob does not specify anything about a carriage return to fo

37

UNIX CONFIGURATION

nt

k l.


low this.

To fix this, carriage return insertion must be enabled some-where in the print setup. The easiest and most common location is on the M305 itself within the appropriate model. The feature is called “onlcr” and the command syntax is:

set model modelname stty onlcr

save

For example, if printing to the destination, d1prn, the asso-ciated model is m1. Therefore, the command is:

set model m1 stty onlcr

save

For default destination-model mappings on the M305, please see M305 Naming Scheme on page 55.

No Formfeed or Extra Page Comes Out

Unix text jobs may also have problems outputting the lastpage of a job especially when the BSD Remote (LPD) primethod is used. This means the formfeed button on the printer has to be pressed to print the last page.

To automate this process, tell the M305 to handle this tasfor you by setting this feature on in the appropriate modeThe command syntax is:

set model modelname trailer $FF

save

For example, if printing to the destination, d2prn, the asso-ciated model is m2. Therefore, the command is:

set model m2 trailer $FF

save

For default destination-model mappings on the M305, please refer to the section entitled M305 Naming Scheme on page 55.

38

NOVELL CONFIGURATION



Overview

This chapter details a complete Novell setup including:

1. Identifying the M305 on the network.

2. Configuring the M305 with its mandatory print setup settings.

3. Configuring a new print queue on the file server.

Please see Appendix C - More on Novell (novell.pdf) for additional information about Novell environments.


The M305 supports network printing under Novell environ-ments by utilizing IPX/SPX. It supports all the latest ver-sions of NetWare including 4.x with the Novell Directory Services (NDS) structure. Both PSERVER and RPRINTER setups are possible. Figure 13 provides a Novell setup over-view.

V1.0 39



Figure 13: Novell Integration

M305 Configuration

Mandatory

The M305 does not require any network settings to make it visible on any Novell network environment. Simply plug it in to your network and power it on. However, with a new print queue setup on a Novell file server, there may be some mandatory settings needed on the M305. Please see the Host Configuration section for further details under all NetWare versions.

Optional

Additional settings are available to fine-tune the M305’s Novell functionality. These options include:

• NDS Context - the NDS context in which the print server object was created (e.g. OU=Print-Server.O=Microplex). This option is required if you create the print server object in a different context from

NetWare 4.1

M305

Printer

Bridge/

File Server

Router

NetWareWorkstation

NetWareWorkstation

NetWare 3.12File Server

NetWareWorkstation

NetWareWorkstation

40 V1.0


at .

-s)

-

5. d R


the context the file server object for the file server that you logged in with is on.

• NDS Tree - the NDS tree the print server object was created in (e.g. MICROPLEX_TREE1). This is only needed if your environment uses more than one NDStree.

• Mode - the mode the M305 will run in. This can be either auto, bindery, or nds. The default is auto so ththe M305 can autosense which mode it should run inSee Appendix C - More on Novell (the PDF file callednovell.pdf) for information on what to do when using both Bindery and NDS file servers at the same time.

• Preferred File Server - in a bindery setup, this speci-fies the file server that the print server object was created on. In an NDS setup, this specifies a file server(that the print server object resides on. Since NDS is distributed, most administrators will not know which file server(s) the print server object is actually storedon, so in most NDS environments this option is not used.

Some of these options will be discussed as needed in theHost Configuration section that follows. For additional information on how to use these options see Appendix C More on Novell.

Host Configuration

Under all versions of Netware, both PSERVER and RPRINTER/NPRINTER setups are supported by the M30Since a PSERVER setup is the most common, you will finthe necessary steps to configure the M305 as a PSERVEwithin this section. For RPRINTER/NPRINTER setup information, please see Appendix C - More on Novell.

V1.0 41



NDS PSERVER Setup (Netware 4.x)

For Netware 4.x environments, Microplex offers a Nwadmn3x snap-in program called MPAdmin. This snap-in can be used to configure both PSERVER and RPRINTER/NPRINTER setups as well as additional settings on the M305. The following steps describe how to configure an M305 using MPAdmin.

Note: Nwadmn3x is only included with Netware 4.11 and higher releases. If you are using Netware 4.10, you can either upgrade to Netware 4.11 or go to Novell’s web site and get the patches to upgrade the Nwadmin program for Netware 4.10 to Nwadmn3x for Netware 4.11. Alternatively, you can perform the PSERVER setup without using MPAdmin. See Appendix C - More on Nov-ell (the PDF file called novell.pdf) for informa-tion on how to do this.

1. Insert the CD ROM that was supplied with the M305 into the drive.

2. Go to the MPAdmin directory, and find the "Setu-pex.exe" file.


4. Answer the prompts throughout the wizard.

5. Login to Nwadmn3x.exe as a user with security equal to "Admin".

6. Go to the "Tools" menu and select the "Define Microplex Print Server Class" menu item. If this item is disabled, then it has already been selected and you can go to the next step.

7. Click on a branch in the tree (i.e. context) that you want to create the M305 print server object in (e.g. OU=PrintServer.O=Microplex).

42 V1.0


n

r r

le


8. Click with the right mouse button to bring up a sub-menu, and choose "Create…" from this menu.

9. A dialogue titled "New Object" should pop up. In the "Class of new object:" list box, select "Microplex PrintServer".

10. Click on "OK" to display the dialogue titled "Create Microplex Print Server", as shown in Figure 14.

Figure 14: Create Microplex Print Server Dialogue

11. Select the M305 from the list of print servers, and thethe "OK" button. Its default name will be M_xxxxxx where xxxxxx equals the last six digits of the print server's Ethernet address found on the bottom of thedevice (e.g. M_091C1A). If the M305 does not showup in the list, click on the "Find…" button to search foit using its Ethernet Address and the Network Numbefor the network it was installed on.

12. You should see the new object in the tree now. Doubclick on the object (e.g. M_091C1A) to bring up its details pages. A dialogue called "Microplex Print Server:<NAME>" should be displayed, where <NAME> is the name of the print server object you created (e.g. M_091C1A). See Figure 15.

V1.0 43


t

.

o


Figure 15: Microplex Print Server Details Pages Dialogue

13. Select the "PServer Assignments" tab, and click on the "Add Printer…" button to bring up the "Add Printer" dialogue box.

14. In the "Microplex Destination For Output" field, selecthe destination on the M305 that you want to print to (e.g. d1prn).

15. Select a printer object to use by clicking on the "New…" or "Browse…" buttons.

16. Click on the "OK" button to assign this printer objectto this M305 print server object.

Note: Microplex requires that the printer object name and Microplex destination name be the same. If this is not the case, you will be asked if you want to rename the destination on the M305

In NDS, a printer object can only be attached to one print server object at any given time. Because of this, if you assign a printer object to another print server object, it will "steal" it from the print server object that is currently using it (this also happens with non-Microplex print server objects). This occurs because Novell is using the printer object to represent a physical printer. A physical printer can only be attached t

44 V1.0


ct

r

g


one parallel or serial port at a time, which means that only one print server object will be required to service this printer at any given time.

However, on a Microplex print server, jobs must pass through an extra layer (a "destination") before being sent on to the printer. This destina-tion allows for further processing of the print job before passing it on to be printed.

In order to properly process the print jobs, the printer object created in Novell, when used with a Microplex print server, must refer to the destina-tion on this server, and not the actual physical printer. If you are using multiple Microplex print servers, you will have to either rename all your destinations to ensure that no printer object names conflict, or keep all the printer objects for one Microplex print server in a context different than those for another Microplex print server.

17. Select the printer from the list box in the "Microplex Print Server:<NAME>" details dialogue, and click on the "Add Queue…" button.

18. In the "Add Print Queue" dialogue that pops up, selea queue object to use by clicking on the "New…" or "Browse…" buttons.

19. Click on "OK" to assign this queue object to the printeobject you chose earlier.

20. Click on "OK" to close the "Microplex Print Server:<NAME>" details dialogue box, and make thechanges permanent.

21. If you were not asked to reset the M305 when you closed the dialogue, re-power the M305 by unplugginand plugging in the power supply.

22. Wait a few minutes after the M305 comes back up.

V1.0 45


nt lt,

s


At this point, you should be able to print to the M305 using the Novell printers/queues that you created. See the Trou-bleshooting Tips section if you are having problems.

Bindery PSERVER setup (Netware 3.x and Netware 4.x)

A Bindery PSERVER setup is possible under both Netware 3.x and Netware 4.x. If you are using Netware 4.x, Bindery emulation is required. Please consult your Novell manual on how to set up Bindery emulation. A Bindery setup using PCONSOLE in Netware 3.x is described below. The setup using PCONSOLE in Netware 4.x is similar to that of Net-ware 3.x and will not be documented.

To configure a print queue on a NetWare 3.x network, you will need to:

1. Log on to the Novell file server as Supervisor.

2. Enter PCONSOLE.

3. Select “Print Queue Information” from the PCON-SOLE Main Menu.

4. Press INSERT to add a new queue to the list of cur-rently-defined queues showing.

5. Type in the name of this new queue when prompted and press ENTER. This can be any name you’d like.

6. Press ESCAPE to return to the PCONSOLE Main Menu.

7. Select “Print Server Information” and press ENTER.

8. Press INSERT when the list of existing print servers displays to add a server.

9. Type the name of the M305 when prompted for a priserver name and press ENTER when done. By defauthe M305 is named “M_xxxxxx” where “xxxxxx” equals the last six digits of the print server’s Ethernet addresfound on the bottom of the device (e.g. M_091C1A).

46 V1.0


t

it

ress

ct

e


10. Back at the print server list, select this newly-defined M305 and press ENTER.

11. Select “Print Server Configuration” from the menu thadisplays.

12. Select “Printer Configuration” from the next menu todisplay a list of configured printers.

13. Select the first item listed as “NOT INSTALLED” andpress ENTER.

14. Type in the name of the default destination on the unfor the “name” field (e.g. d1prn, d2prn, etc.) and go tothe “type” field.

15. Press ENTER to see the possible choices.

16. Select “Defined Elsewhere” from this list.

17. When done, press ESCAPE and select “Yes” to savethe changes to this new printer.

18. Press ESCAPE again to return to the “Print Server Configuration” menu.

19. Select “Queues Serviced by Printer”.

20. Select one of these printers from the printer list that displays and press ENTER.

21. Press INSERT to service this printer.

22. Select the queue created earlier in these steps and pENTER.

23. When prompted for the priority, press ENTER to selethe default or select a priority.

24. Press ESCAPE until back at the PCONSOLE Main Menu.

25. Repower the M305 by unplugging and plugging in thpower supply.

V1.0 47


ys, t

-

r

it

he

r" to

-

r-es


26. Wait two minutes and then select “Print Queue Infor-mation” from the PCONSOLE Main Menu.

27. Select this new queue and from the menu that displaselect “Currently Attached Servers” to see which prinserver is servicing this queue.

28. Press ESCAPE until you have exited PCONSOLE.

At this point, the M305’s name (e.g. M_091C1A) should show within this window. This means the M305 knows about this new Novell print queue it must service as a PSERVER. Therefore, it will poll this queue regularly looking for jobs to print.


NDS PSERVER Setup (NetWare 4.x) - No PSERVER Connection

• Has the M305 been power cycled once the MPAdminsteps were completed? This will make the print serveboot up and realize which print queue and file serverneeds to service.

• Is the M305 already servicing a queue on another fileserver? If so, it cannot service another file server at tsame time.

• The HTML Novell status pages or "debug nest fservenpsh commands can be used to monitor connectionsfile servers. The status should be "logged in". See Appendix C - More on Novell (the PDF file called novell.pdf) for more information.

• The HTML Novell status pages or "debug nest pserver" npsh commands can be used to monitor sevicing of the queues. You should see the queue namin the list. See Appendix C - More on Novell for moreinformation.

48 V1.0


r-.

t

he

g.

5

-

to


• Is the M305 in nds mode as seen under the “list pserver” output on the device? If servicing a Net-Ware 4.x file server, it must be set to handle NDS sevices rather than Bindery. The default setting is Auto

Bindery PSERVER Setup (NetWare 3.x and Net-ware 4.x) - No PSERVER Connection

• Has the M305 been power cycled once the PCON-SOLE steps were completed? This will make the prinserver boot up and realize which print queue and fileserver it needs to service.

• Is the M305 already servicing a queue on another fileserver? If so, it cannot service another file server at tsame time.

• When defining a new “print server” within PCON-SOLE, did you use the correct name for the M305 (e.M091C1A)? By default, it only recognizes itself as “M_xxxxxx” where “xxxxxx” equals the last six digits of its Ethernet address found on the bottom of the device.

• When defining a new “printer name” within PCON-SOLE, did you use a predefined destination/queue rather than a name of your own? By default, the M30only recognizes names like “d1prn”. All else will be ignored by the device. Please see M305 Naming Scheme on page 55 for a list of all default destination names.

• Is the M305 in Bindery mode as seen under the “list pserver” output on the device? If servicing only a NetWare 3.x file server, it must be set to handle Bindery services rather than NDS. The default setting is Auto.

• Is there an available NetWare user license for the M305 to utilize while it acts as a PSERVER? Every PSERVER takes up one user license since it logs in the Novell file server.

V1.0 49


n

ter , n


• Has the password been assigned to the PSERVER iPCONSOLE but not in the M305?

• Have you given the connection process some time afre-powering the M305? In larger Novell environmentssometimes the file server identification and connectioprocess can take several minutes.

50 V1.0

APPLETALK CONFIGURATION



Overview

This chapter details a complete AppleTalk setup including:

1. Configuring a new printer on an Apple station.

For additional information about AppleTalk Configruations, please refer to Appendix D - More on AppleTalk.


The M305 supports network printing under AppleTalk envi-ronments by utilizing EtherTalk, not LocalTalk. Multiple Apple stations in multiple zones can print simultaneously to the M305 as seen in Figure 16.

Figure 16: AppleTalk Integration

Mac

Printer

M305

Bridge/Router

MacMac

Mac

Mac

Mac

Zone A

Zone B

51


t

ll

.

n


M305 Configuration

Mandatory

Under AppleTalk environments, the M305 does not require any network settings to make it visible on the network. Sim-ply plug it into your network and power it on.

Optional

Additional settings are available to fine-tune the M305’s AppleTalk functionality. For example, you may want to sea particular zone for the device to come up in or you maywant to disable some Microplex printers from showing in the Chooser. Please refer to Appendix D - More on Apple-Talk (apple.pdf) for additional information.

Host Configuration

To configure a network printer on an Apple station, you wineed to:

1. Select Chooser from the Apple Menu to bring up theChooser window.

2. Select the LaserWriter icon to produce a list of avail-able printers on the right side of the Chooser window

By default, these M305-related printers will be in the format “M305name_papname” where “M305name” is the name of the print server and “papname” is the name of an I/O port on the device. The print server name will be “M_xxxxxx” where “xxxxxx” equals the last six digits of the M305’s Ethernet address found othe bottom of the device and the I/O port will be prn.

Example name for a printer off of the PRN port of an M305 named M_091C1A:

M_091C1A_prn

52


r

by


3. Choose one of these listed printers to print to and click on OK to close the Chooser window.

This new printer is now a valid network printer which this Apple station can print to.


Printer Won’t Show in the Chooser

• Have you confirmed you are using EtherTalk and notLocalTalk? The M305 does not support LocalTalk.

• Have you clicked on the LaserWriter icon within the Chooser window? By default, the M305 supports theLaserWriter printer driver. To change this, please seethe Microplex PDF file, “apple.pdf” for details.

• Does the M305 need to be configured for a particulazone? By default, the print server will come up in thedefault zone. Please see Common npsh Commands on page 58 for the command syntax to change this.

• Do the M305 printers appear correctly within the Chooser if you try this from another Apple station?

• Confirm that the device can be seen on the network trying another network connection to the M305.

53




54

M305 REFERENCE PAGES

.

t



Overview

This chapter describes some of the most common features of the M305 including:

• important predefined names,

• a description of the built-in command shell, npsh, along with a table of the most common commands,

• how to reset the unit to factory default settings,

• a complete overview of the Flash upgrade procedure

M305 Naming Scheme

The M305 always follows this naming scheme:

M_xxxxxx (e.g. M_091C1A) Default name of M305 in Windows, Novell, and AppleTalk environ-ments. “xxxxxx” equals last six digits of Ethernet address found on bottom of the prinserver.

Workgroup Name of default workgroup M305 can be found under in a Windows environment.

Refer to Figure 17 for an illustration of the default names.

55


on-


Figure 17: M305 Default Names

M305 Command Shell

Within the M305, a command shell is built into the firm-ware called “npsh”. It allows you to manipulate objects like destinations, models, and I/O ports and provides some mitoring and troubleshooting capabilities as well.

d1prn l1

l4

MODELLOG

d2prn l2

l3

PRN

Host/Workstation (Windows, Unix, Novell, AppleTalk)

I/O PORT

PATH

Configuration and Status DataPrint Data

m1

m4

m2

m3

d4prn

d3prn

56


d

ce

in


npsh Access Methods

Access the command shell using these methods:

HTML Forms When you configure a setting using the built-in HTML config-uration forms, npsh commands are actually executed remotely on the M305.

Telnet Session Opening a Telnet session with the M305 allows you to log into the device and access the npsh command shell. (e.g. “telnet 192.168.11.9”)

Remote Shell Command Remotely executes one npsh command at a time from your local TCP/IP station. (e.g. “rsh spike list prn”)

Main npsh Command Prefixes

The four main command prefixes within the npsh commanshell are:

1. “store” - change settings stored in Flash.

2. “set” - change current/working settings in memory.

3. “list” - view current/working settings in memory.

4. “debug” - view certain debugging information.

Note: If the “store” prefix is used, the M305 must be repowered to make the changes take effect. Sin“store” affects Flash settings only, the print server must reset and read the new settings nowFlash.

57


s

to


Note: If the “set” prefix is used, a “save” command must be executed as well so that the new settingare retained after power cycles. Since “set” only affects the settings in memory, they will be lost after a power cycle unless they are told to be saved into Flash ROM.

Common npsh Commands

The npsh command shell consists of more than 50 com-mands. Table 4 outlines some of the more common com-mands. For a complete command reference, please referAppendix G - More on Commands (command.pdf).

Note: When you encounter the word “ifnum”, substi-tute in “1” to represent the network interface (i.e.Ethernet) supported by the M305.

Table 4: Common Commands

Command Syntax Description

store tcpip ifnum addr IPaddress

Store the IP address for the M305.

store tcpip ifnum mask netmask

Store the subnet mask for the M305.

store tcpip route add default routerI-Paddress ifnum

Store a default router/gate-way for the M305 to for-ward remote packets to.

store tcpip ifnum opts [[-]rarp] [[-]bootp] [[-]dhcp]

Control RARP, BOOTP, and DHCP requests for IP addresses.

58



store pserver name newname

Configure the M305’s name; used within Win-dows, Novell, and Apple-Talk setups.

store pserver novell mode nds|bind-ery|auto

Control whether the M305 runs under NDS, Bindery or Autosense mode.

store pserver novell context context

Tell the M305 what con-text the pserver object was created in.

store pserver novell tree treename

Tell the M305 what NDS tree the pserver object resides in.

store pserver novell fserver add fileservername

Tell the M305 about a par-ticular Novell file server. NDS setup - set to the file server that the pserver object resides on (if known); normally left blankBindery setup - set to the file server that the pserver object was created on.

debug nest fserver View the Novell file server(s) the M305 has acknowledged and con-nected to.



59



debug nest pserver View the Novell PSERVER log messages including queues attached to.

store pserver apple zone zonename

Tell the M305 which AppleTalk zone to be in.

set prn mode slow|cen|pc|fast|bb

Configure the speed of the parallel port.

set dest name newname

Change the name of a des-tination/queue.

set sysinfo module [[-]novell] [[-]appletalk] [[-]net-bios]

Control which protocols are enabled on the M305.

list tcpip List the current TCP/IP network settings.

list prn List the current settings of the I/O port.

list dest List the current destina-tion/queue settings.

list model List the current model set-tings.

list sysinfo List current system infor-mation for the M305.



60



cancel jobID Cancel a queued job.

save Save all current settings to Flash.

reset Reset the M305.

ping IPaddress “ping” another TCP/IP host on the network.

telnet IPaddress [escapecharacter]

“telnet” to another TCP/IP host on the network. If escapecharacter is used, it resets the key sequences to exit the telnet session.



61



Back to Factory Defaults

Sometimes it is beneficial to return the M305 to its factory default state. For example, if you are having problems com-municating with the print server over the network, you may want to put it back to a default state and reconfigure the net-work settings. To do this, you will need to move dipswitch 1 to the “off” position and dipswitch 2 to the “on” position then reboot the unit by cycling the power off then on.

start fox|tts|loopb prn

Begin a debugging test on the I/O port of the M305. These tests confirm that the M305’s parallel port is communicating properly with connected devices. fox - A continuous stream of text sent to the attached printer. tts - A continuous stream of Gandalf 400C TTS-compatible text sent to the attached printer.loopb - Loopback test. Any input characters from the device attached to the I/O port is echoed back.

stop all|prn Stop an output test on the I/O port.

quit “Quit” out of the npsh command shell.



62


o les

u

nt

e

n

d-


Please refer to the section entitled Dipswitches on page 11 for instructions about how to do this.

You now have the M305 booted up in a default state, mean-ing its current/working settings are those stored at the fac-tory. All settings configured and stored in Flash are ignored while this switch sits in the “Factory Settings” position.

At this point, you can use npsh commands on the M305 tconfigure certain settings. Here are some common exampof steps taken when the device is in a default state:

1. Forgotten Password

If you have forgotten a password set on the M305, yocan reset the user settings using these commands:

set user from default

save

2. Restore All Settings in Flash to Defaults

Since this default state is temporary and you may wato make sure all settings sitting in Flash are back to their factory default values, you will need to use thescommands:

save default

store tcpip from default

or set dipswitch 1=on and 2=off. See “Dipswitches” opage 11.

Firmware Upgrades

Since the M305’s firmware is stored in Flash ROM, upgraing is easy. Using the File Transfer Protocol (FTP) on a TCP/IP network, the print server can be upgraded to a newer firmware version without needing new hardware.

63



Upgrade Files

There are two files involved with the upgrade process. One is the print server binary (the new firmware) and the other is the upgrade instructions document which provides detailed steps for completing the upgrade.

These files are always available at Microplex’s FTP site (“ftp.microplex.com”) and at Microplex’s Web site (“http://www.microplex.com”) or they can be ordered through Microplex Technical Support. Please see Help Methods Available on page 65 for further information.

64

GETTING HELP

u


GETTING HELP

Help Methods Available

“Troubleshooting Tips” Sections

Troubleshooting tips are listed at the end of each network configuration chapter. The tips listed are the ones most com-monly used. There are additional troubleshooting tips in the appendices as well.

Web Site

Microplex’s Web site, http://www.microplex.com/, con-tains information about the company and its products. Yowill find a link to the Technical Support page which con-tains the “Support Shack”, a central location for technicalbulletins and firmware and software histories and files.

Figure 18: The Support Shack

FTP Site

Microplex’s FTP site, “ftp.microplex.com” contains firm-ware and software for the M305. Once logged in anony-mously, you will need to change to the M305 directory.

V1.0 65

GETTING HELP

-e


Here, you will find several subdirectories pointing to soft-ware, firmware, documentation and miscellaneous files.

Contacting Microplex

If you need technical assistance from Microplex, please have this information on hand:

• M305 serial number found on the bottom of the printserver.

• Description of your network environment and periph-erals attached.

• Description of the problem.

Contact Options

Email “[email protected]”

Fax to “Support” at +1 604 444-4239

Call +1 604 444-4232 and select Technical Support from the list of options (#3)

Note: Email queries usually have the fastest responsetime

Repair Procedure

Warranty Description

Microplex Systems Ltd. warrants this product to be free from defects in workmanship and material for three (3) years from the time of the original purchase date.

During this period, Microplex will repair or replace a defective product with a new or rebuilt product at no extra chargexcept as stipulated below.

At no time shall Microplex’s liability exceed the replace-ment cost of the subject item.

66 V1.0

GETTING HELP

r

-

ir.

if


All expressed and implied warranties for this product including all warranties of Merchantability, Suitability, and Fitness for a particular application are limited to three (3) years from the time of the original purchase date. In no event shall Microplex be liable for Loss of Use, Loss of Profits or Revenues, or other Indirect, Incidental, or Conse-quential Damages. This warranty does not imply the right to loaner or replacement units during the time required to per-form repairs.

This warranty does not cover any losses or damage caused by:

• shipping,

• improper installation, use, or maintenance,

• unauthorized repair, modification, alteration, or replacement of components,

• excessive environmental conditions including electri-cal power surges, temperature, humidity, or any otheirregularities,

• negligence or abuse.

Returning for Repair

To obtain service under this warranty, you must first contact Microplex’s Technical Support department to rule out configuration errors. A Support technician will have you do some tests to ensure the problem is definitely hardware-related. If so, a Return Merchandise Authorization (RMA)number will be given to you by the technician. The defec-tive product should then be returned to Microplex for repa

Please use the following guidelines when shipping goodsback for warranty claim:

• Package the product securely, in original packaging possible, to prevent damage during shipping.

V1.0 67

GETTING HELP

l

-

n

ny


• Indicate the RMA number clearly on the address labeof the shipping carton.

• Include a copy of the invoice/receipt.

• You may use any courier company. However, we recommend using Federal Express due to its lower charges for customs.

Note: Under a normal warranty repair, Microplex will only pay for the shipping charges to return the M305 to you.

• If you ship from a country other than Canada, type (oany paper) a commercial invoice containing the fol-lowing information:

• your address,

• Microplex’s address (as “consignee”),

• country of origin of the product (i.e. Canada),

• number of packages in the shipment,

• description of the product,

• quantity,

• total value of shipment (i.e. your total purchase price),

• reason for return (e.g. warranty repair),

• a declaration.

Canada Customs requires that this invoice accompathe returned product. For an example, refer to Figure 19: Sample Commercial Invoice on page 69. Download a copy from the website: “http://www.microplex.com/microplex/”.

68 V1.0

GETTING HELP


Figure 19: Sample Commercial Invoice

COMMERCIAL INVOICE fromLeslie SmithABC Corporation1234 Western ParkwayAnycity, NCUSA, 27511

DATE OF EXPORT: 22/02/96

AIR WAYBILL NO: 123-12341234

CONSIGNEE:Microplex Systems Ltd.8525 Commerce CourtBurnaby, B.C.V5A 4N3, Canada

IMPORTER (if other than consignee)same as consignee

COUNTRY OF ORIGIN: Canada

# OF TOTALPKGS DESCRIPTION QTY VALUE

1 Ethernet Print Server 1 100.00

REASON FOR RETURN: warranty repair

I declare all information contained in this invoice to be true and correct.

_______________ Leslie Smith 24/03/96

SIGNATURE NAME DATE

V1.0 69

GETTING HELP



70 V1.0

M305 SPECIFICATIONS


M305 SPECIFICATIONS

Hardware Specifications

For additional hardware information, please refer to Appen-dix F - More on Specifications (specs.pdf).

Network Interfaces

The network interfaces provide compatibility with TCP/ICMP/IP and 8.2.3 Ethernet protocols. IEEE 802.3 10/100Base-T UTP Ethernet female RJ45 connector.

Printer Support

Parallel Port (prn) IBM PC compatible male 36 pin parallel interface (Centronics). IEEE 1284-1 compliant. DMA-driven state-machine implementa-tion supports data rates in excess of 600,000 characters per second.

Physical Dimensions

Metric 5.5 cm W x 3.0 cm H x 8.5cm L

Imperial 2.1” W x 1.2” H x 3.25” L

Weight: 0.06756 kg or 0.150 lbs without external transformer

Environmental Details

Operating: 0° C to 50° C

Storage: -40° C to 70° C

90% maximum humidity, non-condensing.

71

M305 SPECIFICATIONS


Electrical Details

Power Supply Options:External transformer available in 120V/60Hz or 220-240V/50Hz.

Power Supply Requirements:Typical 115VAC +/- 10% 36mA, 60Hz

220VAC +/- 10% 18mA, 50/60Hz

Maximum 115VAC +/- 10% 54mA, 60Hz220VAC +/- 10% 27mA, 50/60Hz

AC Power Requirements:Voltage 16 VAC

Current, Typical 600mA

Current, Maximum 1A

DC Power RequirementsVoltage 6 VDC regulated

Current, Typical 70mA

Current, Maximum 105mA

Customer-supplied external transformers must be rated at 20 VA or greater for proper operation.

Power Consumption:Typical 420 mWMaximum 630 mW

FCC Warning

This equipment generates, uses and can radiate radio fre-quency energy. If it is not installed and used as directed in this manual, interference to radio communications may result. The equipment has been tested and found to comply with the limits for a Class A computing device pursuant to Subpart B of Part 15 of FCC rules, which are designed to provide reasonable protection against such interference when operated in a commercial environment. Operation of

72

M305 SPECIFICATIONS


this equipment in a residential area is likely to cause inter-ference. In such a case the user will be required to correct the interference at the expense of the user.

CE Mark Conformity Declaration

The M305 fulfills the requirements for radiated emission according to limit B of EN55022/1987 and the requirements for immunity according to EN50082-1/1992 residential, commercial, and light industry.

M305 LEDs

STAT System Status

NET Data to Network

Run and Auto-reset ModeRun Mode is the normal operating state of the M305. Auto-reset mode is entered when the watchdog timer is triggered and the Print Server has reset itself. The STAT LED flashes differently depending on whether the device’s IP address is configured.

Table 5: STAT LED Patterns

FLASH RATE INDICATES

On once per second (i.e. more off than on)

Normal Mode, IP address configured

On twice per second IP address not configured

Off once per second (i.e. more on than off)

Download (MOS)

Off twice per second Error

73

M305 SPECIFICATIONS

r ion 6 t.


Table 6: NET LED Patterns

Error Conditions

License ViolationAn invalid license mask and key forces the M305 into this mode after three minutes of operation. The mask and key settings are printed on the serial number label at the time of shipment.

Firmware PanicUnrecoverable errors detected by the M305 firmware force it into panic mode. Manually reset the M305 to resume normal operation.

Watchdog HaltThe watchdog timer is a hardware device that resets the system if not serviced regularly by the CPU. It’s pur-pose is to prevent the CPU from entering an infinite loop because of a hardware or firmware problem. Aftea watchdog interrupt, some diagnostic information issaved for debugging and the device resumes operatin Auto-reset Mode. The M305 will auto-reset up to 1times before entering non-operational Watchdog Hal

Spurious HaltUnsupported interrupts force the M305 into this non-operational mode and typically indicate a hardware problem.

FLASH RATE INDICATES

On Indicates link integrity.

Off 1/3 second Flashes off 1/3 second each time a packet is transmitted.

74

M305 SPECIFICATIONS


Hardware ExceptionInternal errors such as bus errors, address errors or ille-gal instructions force the M305 into this non-opera-tional mode.

Software Specifications

Standards Supported

ARC Ethernet Address Control ProtocolARP Address Resolution ProtocolBOOTP Bootstrap ProtocolFTP File Transfer ProtocolGOSIP RFC-1042 Government Open Systems Intercon-

nection ProfileICMP Internet Control Message ProtocolIP Internet ProtocolIPX Internetwork Packet ExchangeLPD Line Printer Daemon ProtocolNetBIOS/SMB Network Basic Input Output System/

Server Message BlockPAP Printer Access ProtocolPSERVER/RPRINTER/NPRINTERSNMP Simple Network Management ProtocolSMTP Simple Mail Transfer ProtocolRARP Reverse Address Resolution ProtocolRFC-1001 NetBIOS over TCP/IPRSHD Remote Shell DaemonTCP Transmission Control ProtocolTELNET Telnet ProtocolUDP User Datagram Protocol

TCP Port Numbers Used on the M305

20 TCP Protocol for FTPD (data)

21 TCP Protocol for FTPD (control)

23 TCP Protocol for TELNETD port

139 TCP Protocol for NETBIOS Session Services

75

M305 SPECIFICATIONS


514 TCP Protocol Remote Command daemon port

515 TCP Protocol BSD 4.3 LPD port

4410 TCP Protocol PRN port for logging

4400 TCP Protocol PRN port

8200 Microplex Communications Protocol Port for Waldo

Note: Client application software can send raw data to PRN by opening a socket to the associated TCP port number as defined above. Such connections are queued along with print jobs using other print methods (e.g. LPR/LPD).

UDP Port Numbers Used on the M305

161 UDP port for SNMP

514 SYSLOG client support

68 BOOTP client port

76

GLOSSARY

d


GLOSSARY

ARP Address Resolution Protocol. Associ-ates a selected IP address with a net-work device’s Ethernet address.

banner page A page printed before the print job which includes details about that job.

bps Bits per second.

Centronics Parallel port interface standard found onmost printers.

Chooser Feature within the Apple operating sys-tem that controls system devices (e.g. printers).

daemon A continuously running process that handles system-wide functions like printspooling.

default router Local device that forwards any IP pack-ets destined for another subnet.

destination Logical print queue on the M305 to which hosts send their print jobs. Thereare four destinations on the M305.

DHCP Dynamic Host Configuration Protocol. Allows a network device to discover its IP address dynamically upon bootup. The IP address doesn’t need to be storewithin the device permanently.

DNS Domain Name Server. Host providing responses to queries for a given host name’s IP address.

V1.0 77

GLOSSARY


EEPROM Electronically-Erasable, Programmable Read-Only Memory. Preserves data after power is removed. Also known as Flash memory.

Ezsetup Quick and easy Microplex configuration script that runs on Unix hosts.

factory defaults Settings shipped with the M305.

flash Permanent memory in the EEPROM. Stores firmware code and configurable settings. Allows for upgrades without replacing hardware inside the M305.

FTP File Transfer Protocol. Used for trans-ferring files from one TCP/IP host to another and used in the upgrade process.

header strings Strings that precede print jobs; used to control the printer and set printing options.

HTML HyperText Markup Language. Format used for documents viewable on the World Wide Web.

HTTP HyperText Transport Protocol.

IEEE Institute of Electrical and Electronics Engineers.

ifnum Interface Number. Represents the net-work interface. With an M305, this will always be “1” for Ethernet.

interface script Unix host filter file that processes the print job before it is sent over the net-work to the M305.

I/O port Port for attaching peripherals to. The M305 provides one: PRN.

78 V1.0

GLOSSARY

.

e


logpath Determines type of print job and printer logging needed per job. One logpath is associated with every destination.

LPD/LPR Line Printer Daemon. The most com-mon TCP/IP remote printing protocol that crosses all hardware utilizing IP.

MIB Management Information Base. A set of variables (database) managed by an SNMP manager application.

model Defines how a print job should be pro-cessed (e.g. banner pages added, ASCII to PostScript conversion) as it passes through the M305. One model is associ-ated with every destination.

MPS Microplex Printing Solution (MPS). Alternative Windows printing solution.

NDS Novell Directory Services. Novell’s glo-bal directory structure for NetWare ver-sions 4.0 and higher.

NetBIOS Network Basic Input Output System. Common interface among PC networks

netmask see subnet mask.

NIT Network Interface Tap. A module that serves as a generic interface between thdata link protocol layer (i.e. Ethernet) and higher interface network protocol layers. Each NIT is indexed by an inter-face number (ifnum).

npsh Extensive built-in command shell within the M305.

V1.0 79

GLOSSARY

-

d

.


papname Printer access protocol name. An Apple-Talk name for each printer defined on the host. Makes up the second half of the name listed in the Chooser and is transparently mapped to a M305 desti-nation.

PDF Portable Document Format. Encodes different types of documents enabling them to be read across multiple plat-forms.

ping Packet Internet Groper. A program used to test reachability of destinations by sending them an ICMP echo request and waiting for a reply. It is a standard com-mand to test a TCP/IP connection. (e.g. “ping 192.168.11.9”)

print path Three-stage path a print job takes whenit is sent from a host to a printer throughthe M305.

PSERVER Print Server. A Novell print method where the M305 continuously polls the Novell file server’s print queue looking for print jobs.

RAM Random Access Memory. Volatile memory within the M305 that contains cur-rent/working settings. Settings are lost once the power is removed.

RARP Reverse Address Resolution Protocol. Allows a network device to discover its IP address dynamically upon bootup. The IP address doesn’t need to be storewithin the device permanently.

router A device that forwards IP packets to their destination. Also called a gateway

80 V1.0

GLOSSARY

-

e


RPRINTER Remote Printer. A Novell print method where the M305 waits for jobs to be sent to it from a defined PSERVER.

serial number Number found on the bottom of the M305. Each M305 is assigned a unique serial number.

SNMP Simple Network Management Protocol. A standard protocol used to monitor net-work devices called “SNMP agents”.

socket TCP connection between two hosts consisting of a source and destination TCPport number at each end.

spooling Storing data in memory or in a file until it can be printed.

subnet mask A binary value used to divide IP net-works into smaller subnetworks or sub-nets. This mask is used to help determine whether IP packets need to bforwarded on to other subnets.

tar Unix command for archiving data onto apermanent storage medium.

TCP/IP Suite of protocols that act as the base protocol for the Internet.

TCP port A logical connection point in the soft-ware of a TCP host or device. When twoIP devices talk, they establish a socket which consists of a source and destina-tion TCP port number on both ends.

Telnet Command and protocol to establish a terminal connection between two hostson an IP network.

V1.0 81

GLOSSARY


trailer strings Strings that follow print jobs; used to control the printer and set printing options.

Waldo TCP/IP configuration utility.

zone A predefined group of AppleTalk sta-tions which helps divide up larger net-works.

82 V1.0

INDEX


INDEX

Symbols.options file B-30.rc B-28/etc/hosts B-31/etc/printcap B-18, B-28, B-29, B-30/usr/spool/lp/admins/lp/interfaces B-14/usr/spool/lp/model B-14

AAC power requirements 72Adobe TranScript B-26

details B-30AIX

configuration B-22AIX 3.2.5

configuring printing B-24AIX 4.1

configuring printing B-23AppleTalk

changing printer names D-2changing zones D-5common commands 60configuration D-1enabling/disabling the module D-4environments 51host configuration 52, D-2limiting printers E-7M305 configuration 52mapping printer names to destinations/queues D-4naming E-5number of printers D-4understanding printer names D-2using different printer drivers D-7

V1.0 83

INDEX


architecture 3diagram E-2

ASCII to PostScript conversion E-6in interface scripts B-11, B-20in models E-3, E-4

ASCII to PostScript conversion, see also a2psautosensing/autoswitching

of printer mode E-6

Bbanner page generation E-6

extra with Novell C-21in interface scripts B-11, B-19in models E-3

binarynpscramble E-10

blank pageswith Novell C-21

BOOTPcommand 58

BSDand npd B-28direct/remote printing B-16host configuration B-16interface script setup B-19interface script syntax B-18spooling B-10

Ccancel job 61CAPTURE C-20

configuration C-21capturing printer feedback E-11carriage return insertion E-6

in interface scripts B-11, B-20in models E-3with DOS B-34

carriage return insertion, see also onlcr

84 V1.0

INDEX


CE Mark 73checksum

in logpaths E-4Chooser

problems D-8command shell

debug commands G-4help with G-3list commands G-5Novell environments, accessing in C-11overview 56prefixes 57, G-2prompt G-3rules 57set commands G-7store commands G-17user accounts G-3user permissions G-3ways to access 15, 57, G-2

config fileand naming schemes E-5

configurationAppleTalk D-1available tools 15description 15I/O port E-5

connectionto network 10

control file B-17

Ddata rate F-3DC power requirements 72Debug G-4debug commands G-4debugging tests

commands 62

V1.0 85

INDEX


defaultrouter B-31

defaultsgoing back to 62restoring settings to 63

descramblingin models E-3

destinationsand PSERVER C-17command 60default E-2default names 55details E-2diagram E-2in print path 4

devicefile B-28DHCP

command 58direct socket printing

npwrite B-9overview B-9rsh/rcmd/remsh B-10

DNS B-31

Eemail

and error messages B-33and logging E-4Microplex Support 66

error conditionsfirmware panic 74hardware exception 75license violation 74spurious halt 74watchdog halt 74

EtherTalk D-8ezsetup B-10

86 V1.0

INDEX


and interface scripts B-11and remote management E-7host configuration 34how to use 33main menu 20overview 20tips 34troubleshooting 35

FFCC warning 72features

list of 5Flash

uses 3flow control

problems B-33formfeeds 38FOX test

steps 37frame type

controlling E-7ftp

executing a configuration file with E-20printing with B-25

FTP Daemonand configuration E-17and printing B-25, E-15and remote management E-7configuring M305 with E-17copying a configuration with E-17monitoring print queue with E-16printing with E-15removing print job wih E-16restoring a configuraiton with E-18using to access command shell G-2

FTP site

V1.0 87

INDEX


Microplex 65

Ggarbled data B-34, C-21

HHardware Specifications

Dimensions 71Operating temperature 71Storage temperature 71

header stringin models E-3with variables E-4

home pageM305 16

host configurationBSD B-16

host softwareand interface scripts B-11

HP OpenSpoolSetup B-20

HTMLand remote management E-7menu structure 16overview 15

II/O port

and destinations E-2and logging E-4command 60default names 55in print path 4problems B-33

installationdiagram 11site requirements 8steps 10

88 V1.0

INDEX


interface scriptBSD syntax B-18choices B-12modifying B-12overview B-11System V syntax B-14

IP addresscommand 58duplicate B-31format B-32instead of IP name B-31

Jjobs

in logpaths E-4

LLED

descriptions 73patterns 73, F-7run and auto-reset mode 73status 29

link integritydetails E-6

listcommon commands 60

list commands G-5logpaths

altering settings E-13default names 55details E-4in destinations E-3in print path 4naming E-12options E-11viewing current E-13

lp

V1.0 89

INDEX


and logging E-13lpstat

and logging E-11

MMacs, See AppleTalk.memory

controlling E-6models

and onlcr B-34and processing options E-3, E-6default E-3default names 55diagram E-2in destinations E-2in print path 4setting a formfeed 38setting onlcr 38types and inclusions E-3

modulecontrol E-7

MPSinstalling in Windows environments 25

Nname

command 59default print path 56default print server 55workgroup 55

naming schemes E-5NCSA E-25

details E-25printing with E-25

NetBIOSnaming E-5

network

90 V1.0

INDEX


connector diagrams 9connectors 8, F-2

Novelladjust polling time C-6changing frame type C-8, C-9, C-10changing M305 name C-7common commands 59communication problems C-17, C-19controlling frame type E-7host configuraiton C-11host software C-11M305 configuration 40naming E-5password security C-4preferred server C-2printing mechanisms C-21printing problems C-20queueing C-20security E-11

Novell modecommand 59

Novell treecommand 59

npcomm.sh B-30npd

and interface scripts B-12, B-13applications which use B-29finding B-27locks B-27modifying a host to use B-28starting B-27stopping B-28testing B-28

npr.if B-9, B-12and extra job processing B-34, E-6overview B-11

V1.0 91

INDEX


problems B-33using B-14, B-19

NPRINT C-20configuration C-21

npscramble E-10in interface scripts B-19

npshconfiguration alternatives 20

npsh, See command shell.npwrite B-9, B-26

and Adobe TranScript B-30and interface scripts B-12, B-19command syntax B-9details B-9

Oonlcr 38

data in wrong format B-34garbled data B-34

onlcr, see also carriage return insertionOpenSpool

Setup B-20

Ppage count

in logpaths E-4parallel port

command 60description 9diagram F-5parameters 9, F-3pinout F-5TCP port numbers 76timing chart F-3, F-4timing diagram F-3UDP port numbers 76

password E-7

92 V1.0

INDEX


forgotten 63Novell C-17

PC/TCPdetails B-24

PDFfile index 1

port numbers 75power

AC requirements 72consumption 72DC requirements 72requirements 72socket pinout F-2specifications 72

print job scramblingin interface scripts B-11

print pathdiagram 4

print spoolerintegrating B-10

printerlogging E-11logging terms E-12logging through logpaths E-12logpath E-12monitoring E-11

printer support 3printing mechanisms

Novell C-21PRN, See parallel port.processing options

details E-6in interface scripts B-20location of B-11

protocolscommand 60supported 75

V1.0 93

INDEX


PSERVERdefault name C-17

pseudo-tty daemonnpd B-26

Qqdaemon B-22

RRARP

command 58problems B-32

remote managementTCP/IP methods E-7

remote shell 20overview 20

repaircommercial invoice sample 69returning for 67RMA number 67

repairs 66return

shipping instructions 67RMA number 67router

command 58communicating across A-5

routingproblems B-31

RPRINTERconfiguration C-12, C-14

rsh/rcmd/remshand Adobe TranScript B-30and interface scripts B-12, B-15, B-19and lp E-13and remote management E-7BSD syntax B-10details B-10

94 V1.0

INDEX


System V syntax B-10

Sscrambling/descrambling

in interface scripts B-20scrambling/descrambling print jobs E-10SDRAM 3security E-7

Novell passwords E-11passwords E-7scrambling/descrambling E-10SNMP E-11tcp access lists E-9

serial numberlocation of 66

servicecontrol E-7

setand I/O port E-5

set commands G-7set date G-7set dest G-7set logpath G-8set model G-9set prn G-12set rprinter G-20set sysinfo G-13set time G-15set user G-15set var G-16

SNMPand remote management E-7communities E-11custom MIBs E-21details E-21security E-11traps E-22

V1.0 95

INDEX


Solaris 2.XLPR Setup B-21

spoolerbypassing B-9, B-33problems B-33

store commands G-17store ifc G-17store pserver G-17store tcpip G-20

subnet maskcommand 58

Sun NeWSprint B-26setup B-29

syslogin logpaths E-4

System Vand npd B-28host configuration B-13interface script syntax B-14spooling B-10

Ttab expansion E-6

in models E-3tab expansion, see also xtabTCP

access list B-32port for logging E-4

TCP/IPand remote management E-7communication problems B-31controlling frame type E-7printing problems B-32

technical support 66Telnet 20

and logging E-4and remote management E-7

96 V1.0

INDEX


problems B-32test

printer B-33test pages, printing of 10trailer string

and formfeeds B-33, C-21in models E-3with variables E-4

UUnix

direct socket printing B-9environments 31Ezsetup utility 20, 33host configuration 34M305 configuration 32

upgradeoverview 63

URLM305 home page 16

usersin logpaths E-4

UTPmanipulate E-5

Vvariable definitions F-7variables

details E-4

WWaldo 17

configuration 17environment 17installing in Windows 18

warranty 66registration 7

Windows

V1.0 97

INDEX


communicating across routers A-5destination names A-8M305 configuration 24manually configuring M305 A-3print methods overview A-1TCP/IP settings A-9workgroup names A-7

Windows 95IP address configuration A-10, A-12NetBIOS Installation A-10, A-14netmask configuration A-10, A-12

Windows NTLPR installation A-12

workgroupdefault 55

Xxtab

and garbled data B-34, C-22xtab, see also tab expansion

98 V1.0

M305 Print Server Quick Installation and … 5 Manual Printing with FTP’s PC/TCP B-24 Printing...

Documents

Transcript of M305 Print Server Quick Installation and … 5 Manual Printing with FTP’s PC/TCP B-24 Printing...