Network Guide

	Settings for NetWare Users

Overview
For Users of Printers Supporting NetWare Queue-Based Printing
For Users of Printers Not Supporting NetWare Queue-Based Printing

Overview

If you are using a printer that supports NetWare queue-based printing, see For Users of Printers Supporting NetWare Queue-Based Printing for detailed information.

If you are using a printer that does not support NetWare queue-based printing, see For Users of Printers Not Supporting NetWare Queue-Based Printing for detailed information.

Note:

To find out whether your printer supports NetWare queue-based printing, see the User’s Guide.

Top

For Users of Printers Supporting NetWare Queue-Based Printing

This section explains how to configure the network interface for NetWare. First, you need to set up the printer in a NetWare environment, and then configure the network interface using EpsonNet Config.

Introduction to NetWare settings

Supported systems

server environment

NetWare 3.1/3.11/3.12/3.2 (Bindery)

NetWare 4.1/4.11/4.2 (NDS, Bindery emulation)

IntranetWare (NDS, Bindery emulation)

NetWare 5.0/5.1 (NDS, NDPS)

NetWare 6.0 (NDS, NDPS)

Client environment

The client environment must be supported by NetWare. The clients are able to use the printer driver mounted on the network interface.

The following Novell Client is supported.

For Windows 98:
Novell Client 3.4 or later for Windows 98/95

For Windows 2000:
Novell Client 4.8 or later for Windows

For Windows XP:
Novell Client 4.9 or later for Windows XP

About modes

You can choose either the Print server, Remote Printer, or Standby mode. We recommend that you use the Print server mode unless the number of users exceeds the limit.

Features of these modes are described below.

Print server mode (NDS/Bindery Print server):

High-speed printing with direct printing

Uses the NetWare user account

Can connect up to 8 file servers simultaneously

Can register up to 32 print queues

Remote Printer mode:

A NetWare user account is not required.

A print server is needed to control the remote printer.

Can attach up to 16 printers for NetWare 3.x, and up to 255 for NetWare 4.x or later.

Note:

When you turn on the printer, the user account is temporarily accessed in the Remote Printer mode. If there is no user account available, turn on the printer before connecting the client to the network.

LPT1 remote printing is not supported.

Standby mode (factory default mode):

The Standby mode is the default mode. This mode disables all NetWare related functions. Use the Standby mode when you are not using the network interface in a NetWare environment.

Instructions for using NetWare

Printing a text file

When you print a text file using the NPRINT command of NetWare or DOS, redirection, misconversion or a gap in characters may occur depending on the client environment.

IPX routing protocol “NLSP”

It is possible to set the IPX routing protocol “NLSP” from NetWare 4.x or later; however, the network interface does not support NLSP. RIP/SAP controls the communication.

You can select the routing protocol from a) NLSP with RIP/SAP Compatibility, or b) RIP/SAP Only. If you remove the bind of RIP or SAP when NLSP with RIP/SAP Compatibility is specified, the network interface then cannot communicate with the file server and NDS. (See “Protocols” and “Bindings” in NetWare’s INETCFG utility.)

Bindery and NDS

You can check the bindery context path from the server console by using the SET BINDERY CONTEXT command.

If the bindery context path has not been set, or if you want to use the printing environment of another context from a non-NDS client, you need to specify the context for the bindery context. Use the SET BINDERY CONTEXT command to set the context in the AUTOEXEC.NCF file.

You cannot use the bindery print server mode with EpsonNet Config if you are running Novell Client for Windows 95/98 version 3.00 or Novell Client for Windows NT version 4.50. To configure the network interface for bindery mode, use Novell IntranetWare Client or EpsonNet Config with Web Browser.

See your NetWare documentation for more information.

Time required to recognize the network interface

It takes up to two minutes for the NetWare server to recognize the network interface, after the printer is turned on. During this start-up time, the status sheet does not show the correct information.

Frame type

The same frame type should be used for the NetWare server and IPX router on the same network. If more than one frame type is used on the same network, bind all the frame types to the NetWare servers and IPX routers.

For NetWare 5.x

The IPX protocol must be installed (bound) on the NetWare 5.x server.

About modes

If the mode you have logged in is different from the mode you set for the network interface, a message appears when you try to configure the network interface for NetWare. If you do not want to change the current settings, click Cancel and log in again using the same mode set for the network interface.

Using Bindery Print server (NetWare 3.x/4.x)

This section contains instructions on using the network interface in the Print server mode on NetWare 3.x/4.x/IntranetWare with Bindery emulation.

Note:

The network interface in the Print server mode of NetWare 3.x does not allow you to use the Print server status display control with PCONSOLE.

Turn on your printer.

From any NetWare client, log in to the target NetWare server with supervisor privileges. You must log in with the bindery connection.

Configure the network interface using EpsonNet Config. See the EpsonNet Config Reference Guide for details.

If NetWare objects are already created, you can also use EpsonNet Config with Web Browser. See NetWare for details.

Using NDS Print server (NetWare 4.x/5.x/6.0)

This section contains instructions for using the network interface in the Print server mode on NetWare 4.x, IntranetWare, NetWare 5.x, or NetWare 6.0 with NDS mode.

Turn on your printer.

From any NetWare client, log in to the target context of the NDS tree as an ADMIN.

Configure the network interface using EpsonNet Config. See the EpsonNet Config Reference Guide for details.

If NetWare objects are already created, you can also use EpsonNet Config with Web Browser. See NetWare for details.

Using NDS Remote Printer Mode (NetWare 4.x/5.x/6.0)

Follow the steps below to make the printer environment using NWAdmin under NetWare 4.x, IntranetWare, NetWare 5.x, or NetWare 6.0 with NDS mode.

Creating objects

From any NetWare client, log in to the target context of the NDS tree as an ADMIN.

Run the Administrator tool (NWAdmin).

Create a printer:

Click the directory context icon, and select Create from the Object menu, then Printer. Type the Printer name and click Create.

Create a print server:

Click the directory context icon, and select Create from the Object menu, then Print server. Type the Print server name and click Create.

Create a print queue:

Click the directory context icon, and select Create from the Object menu, then Print Queue. Type the Print Queue name and select the Print Queue Volume, then click Create. Double-click the print queue object, and register the user.

Note:

Since your clients need the print queue name you set here when they use the printer, announce the print queue name to your clients.

Double-click the Printer Object icon in the NetWare Administrator screen.

In the Printer dialog box appears, click Assignments and then click Add.

From the print queue list, select the queue you created in step 5 and click OK.

Click Configuration, and select Other/Unknown for the Printer type list box and click OK.

Double-click the Print server Object icon in the NetWare Administrator screen.

In the Print server dialog box that appears, click Assignments and then click Add.

From the printer object list, select the printer object you want to assign and click OK.

Go back to the screen in step 11, and click the Printer Number button to set the printer number from 0 to 254.

To confirm the objects you have assigned, double-click the Print server object icon. Click Print Layout, and check that the print server, printer, and print queue are connected.

Configuring for NetWare using EpsonNet Config

Turn on your printer.

Load the print server from the file server’s system console which the print queue volume is set.
>LOAD Pserver print server name you set using NWAdmin

Configure the network interface using EpsonNet Config. See the EpsonNet Config Reference Guide for details.

If you use the NetWare objects that are already created, you can use EpsonNet Config with Web Browser too. See NetWare for details.

Using the EpsonNet NDPS Gateway

This section contains instructions on printing using Novell Distributed Print Services^® (NDPS^®) with Novell^® NetWare^® 5.x/6.0. Novell Distributed Print Services (NDPS) is the new generation print services of NetWare.

Note:

Banners cannot be printed with NDPS.

The Status Monitor 3 utility cannot be used with NDPS.

Bind the IP or both IP or IPX protocols on the NetWare server that runs NDPSM.NLM and EPSONGW.NLM.

Check the following points before starting.

Install the appropriate client software, such as Novell Client for Windows 95/98 version 3.4, Novell Client for Windows version 4.8, or Novell Client for Windows XP version 4.9 on client workstations. Make sure they install NDPS.

When you use the network interface with Bindery (either in the Print server mode or the Remote Printer mode), you need PCONSOLE.EXE to create bindery objects such as Print server and Print Queue objects. Since PCONSOLE.EXE does not come with NetWare 5.x/6.0, you need to get the file from Novell.

Outline of settings

The followings are basic steps to use the network interface with the NDPS printing system. Detailed procedures are described in the subsequent sections.

Install EpsonNet NDPS Gateway.

Upload printer driver files to the NDPS RMS server.

Create an NDPS Manager object in NetWare Administrator.

Create a Printer Agent in NetWare Administrator.

Configure the network interface using EpsonNet Config.

Set the printer on the client workstations.

The environment to use, the settings you make, and the tools to use differ depending on the printer type and connection type you choose. You can create an NDPS Manager and Printer Agent in NetWare Administrator or partially via the server Console. See the Novell online documentation for more details.

Installing EpsonNet NDPS Gateway on your NetWare server

You can install EpsonNet NDPS Gateway from the Software CD-ROM.

Note:

If an older version of EpsonNet NDPS Gateway is already installed, be sure to unload the NDPS Manager before installing a new version of EpsonNet NDPS Gateway.

Open the NETUTIL folder.

Open the ENGW folder.

Double-click EDPS2***.EXE.

Note:

The last three characters of the file name, represented by asterisks, vary depending on the place of purchase.

For detailed information on EpsonNet NDPS Gateway, see the online guide on the Software CD-ROM.

To view the online guide, follow the steps below.

Open the NETUTIL folder.

Open the ENGW folder.

Double-click index.htm.

Uploading printer driver files to the RMS

After installing EpsonNet NDPS Gateway, you need to upload the printer driver to the Resource Management Service (RMS).

Upload the printer driver to the NetWare server using NDPS Broker. For details on the procedure, refer to the section of NDPS or iPRINT in the NetWare documentation.

Creating an NDPS Manager

Run NetWare Administrator (NWADMN32.EXE) on the client machine. The main browser window appears.

To create an NDPS Manager, click the Directory context icon, and then select Create from the Object menu.

Select NDPS Manager from the list.

Enter the NDPS Manager name in the NDPS Manager Name field.

Browse the Resident server and select where you want the NDPS Manager assigned.

Browse the Database Volume and select where you want the NDPS Manager database assigned.

Click Create. The NDPS Manager icon appears in the main browser window.

Type LOAD NDPSM at the server console, and then select the NDPS Manager you have created.

Creating a Printer Agent

After creating an NDPS Manager, you can create Printer Agents, either public access printers or controlled access printers. The following are the features of public access printers and controlled access printers.

Public Access Printers:
NDPS printers that are available to all network users and not associated with an NDS object. Users can select and print to any public access printer they can view from their workstations. However, these printers do not take full advantage of services such as security and job event notification.

Controlled Access Printers:
NDPS printers that are added to the NDS tree by NetWare Administrator. They are only available to the workstation user through the NDS object list. These printers can take full advantage of the security and management features provided by NDS.

Creating a Printer Agent automatically

You can create a Printer Agent automatically. Only public access printers can be created in this way. See “Creating Public Access Printers Automatically” in the EpsonNet NDPS Gateway manual for detailed information.

Creating a Printer Agent manually

You can create Printer Agents, either public access printers or controlled access printers. The way to create a Printer Agent differs depending on the printer type you choose.

Select a printer type (either public access printer or controlled access printer).

Create a public access printer. If you want to create a controlled access printer, go to step 3.

In NetWare Administrator, double-click the NDPS Manager you have created. Click Printer Agent List, and then click New. Type the Printer Agent name, and then select EpsonNet NDPS Gateway Configuration for the Gateway Type. Click OK. Then go to step 4.

Create a controlled access printer.

In NetWare Administrator, select the Directory context icon. Select Create from the Object menu, and then select NDPS Printer. Type the Printer Agent name, and then select Create a new Printer Agent, and then click Create. Select the NDPS Manager you have created, and then select EpsonNet NDPS Gateway Configuration for the Gateway Type. Click OK.

Select one of the following port handler type. Select Remote (lpr on IP) if you want to use the printer in IP network. Select Remote (rprinter on IPX) if you want to use the printer on an IPX network. Select Queue Based if you want to keep the NetWare NDS print server configuration of the network interface. Then click Next.

Configure it as described below. It is a good idea to print a network status sheet of the network interface and configure the corresponding items.

For Remote (rpinter on IPX) connection:
You need to use the same configuration of NetWare Remote printer mode as you have set by using EpsonNet Config already.
IPX Network Number: Enter the IPX network number of the network interface.
IPX Node Number: Enter the IPX node number of the network interface.
SAP Name: Enter the Primary Print server Name. Do not use the following characters: ~ ! @ # $ % ^ & * ( ) + ` = { } [ ] │ \ : ; " ' < , >. ? / `
Printer Number: Enter the printer port number (from 0 to 254).

For Remote (lpr on IP) connection:
IP Address: Enter the IP address of the network interface. You can confirm the IP address on the network status sheet.

For Queue Based connection:
NDS Context: Type the NDS context.
Print server Name: Print server name that is already defined in NDS or Bindery. If the printer is in the Remote Printer mode, enter the print server name that is used when Pserver.NLM is loaded.
Printer Name: Printer name that is already defined in NDS or Bindery.
NDS Volume for Print Queue: The format is as follows:
Format: NDS Volume and context
For example: NDPS_server_SYS.EPSON
File server for Print Queue: Enter the file server name for the print queue.
IPX Network Number: Enter the IPX network number of the network interface.
IPX Node Number: Enter the IPX node number of the network interface.

When you finish filling in the boxes, press Finish. Follow the on-screen instructions.

The Select Printer Drivers dialog box appears. Select an appropriate printer driver for Windows Me/98 and Windows 2000. Be sure to select the correct printer driver for your printer from the appropriate menus.

Click Continue.

Confirm the Printer Agent that you have just created.

In NetWare Administrator, double-click the NDPS Manager object and click Printer Agent List. Check that the status of the Printer Agent you have just created is “Idle”.

Configuring for NetWare using EpsonNet Config

Follow the steps below if you want to use the printer in IPX network.

Note:

Be sure that the one of the following clients is installed on your computer: Novell Client 32, Novell IntranetWare Client, or Novell Client.

Turn on your printer.

From any NetWare client, log in to the target NetWare server as an ADMIN.

Run EpsonNet Config from the Start menu. See Accessing the EpsonNet Config Reference Guide for details.

If the IP address of the printer is already assigned, you can use EpsonNet Config with Web Browser too. See NetWare for details.

Setting the printer on client workstations

After configuring the network interface, set up the printer on client workstations.

Installing printers automatically

Run the Novell Printer Manager from Windows. If you are running Windows Me/98/2000, run:
\PUBLIC\WIN32\NWPMW32.EXE

In the Novell Printer Manager dialog, select New from the Printer menu.

Click Add. A list of available printers appears.

Select the printer you want and click Install.

The Novell Printers---Install dialog appears. You may modify the printer name that appears and select a pre-defined configuration.

Click OK. The printer driver for that printer model is installed automatically from the Resource Management Service.

Click Close. The printer appears in the main Printer Manager window and is available for print jobs.

Installing printers manually

Install the printer driver.

Change the Ports on the printer’s properties dialog box. Specify the following objects for the port.

For Public Access Printers:
The Printer Agent you have created in “NDPS Public Access Printers” under Entire Network.

For Controlled Access Printers:
The Printer Agent you have created in the NDS tree.

See the Novell online documentation for details.

Instructions for using a dial-up network

This section explains about using a dial-up network.

Note:

The primary server described in this manual indicates a primary time server which offers time to the workstations on the network.

Using a dial-up network in each mode

Print server mode

You must use a dedicated dial-up line.
Since polling is performed on the file server in the print server mode, no vicarious response by the router is possible. Therefore, no dial-up connection is possible in this case.

Remote Printer mode

In Remote Printer mode, use of a router with a vicarious response function allows the primary server to be installed at the dial-up destination. However, an extra account might be generated when the primary server is down. To avoid that, it is recommend to use connections via a dedicated dial-up line.

Follow the instructions for using a dial-up line.

When there is a primary server at the dial-up destination

For local networks with file servers:

When the power is turned on

A dial-up is generated because access is made to a local file server first and then to a primary server. There is no problem since this dial-up only occurs at startup.

When the network interface is not correctly set

A dial-up is generated because access is made to a local file server first and then to a primary server. This dial-up is repeated at intervals of approximately 5 minutes. Make the network interface settings correctly to avoid this problem.

During normal operation (standby)

An SPX Watchdog packet is sent according to the NetWare protocol convention. Use a router with a vicarious response function to avoid a dial-up.

During normal operation (printing)

A dial-up is generated while the printing data is being transferred. This is not a problem because it is a dial-up specific to the dial-up network.

When the primary server is down during operation

A dial-up is generated because a connection to the primary server is attempted periodically. Since this is attributable to the automatic re-connection function, turn off the printer once.

When the file server on the local network is down

When there is no file server on the local network, NetWare cannot be used on the local network. In this case, the NetWare protocol for the network interface is also not available. No dial-up is generated under this condition. When the file server on the local network is restored, the network interface is also automatically restored.

For local networks with no file server:

Depending on the router settings, the NetWare protocol can be used without a file server on a local network. This setup follows the same pattern as that described above.

When there is a primary server in the local network

Even if a primary server is installed on the local network, an unnecessary dial-up may be generated depending on the configuration.

The following problems are common to both Print server mode and Remote Printer mode.

When the power is turned on

Since access is made only to the primary server, no dial-up is generated.

When the network interface is not correctly set

Since access is made only to the primary server, no dial-up is generated. However, if the file server/print server of the remote network is erroneously set as the primary server, an unnecessary dial-up might be generated. Correct the settings to avoid this problem.

During normal operation (standby/printing)

Since access is made only to the primary server, no dial-up is generated.

When the primary server is down during operation

Connection to the primary server is periodically attempted, but no dial-up is generated. However, if the router is set to pass SAP packets (Find Nearest server), an unnecessary dial-up might be generated. To avoid this, turn off the printer once, or do not allow the router to pass SAP packets (Find Nearest server).

Top

For Users of Printers Not Supporting NetWare Queue-Based Printing

This section explains how to configure the network interface for NetWare.

To print in a NetWare environment, you need to use NDPS. First, install EpsonNet NDPS Gateway on the NetWare server, and then set a valid IP address to the network interface using EpsonNet Config.

Note:

Be sure to set a static IP address to the network interface.

Introduction to NetWare settings

Supported systems

server environment

NetWare 5.0/5.1 (NDPS)

NetWare 6.0 ( NDPS)

Client environment

The client environment must be supported by NetWare.
The clients are able to use the printer driver mounted on the network interface.

The following Novell Client is supported.

For Windows 98:
Novell Client 3.4 or later for Windows 98/95

For Windows 2000:
Novell Client 4.8 or later for Windows

For Windows XP:
Novell Client 4.9 or later for Windows XP

Using the EpsonNet NDPS Gateway

This section contains instructions on printing using Novell Distributed Print Services^® (NDPS^®) with Novell^® NetWare^® 5.x/6.0.

Note:

Banners cannot be printed with NDPS.

The Status Monitor 3 utility cannot be used with NDPS.

Bind the IP protocol on the NetWare server that runs NDPSM.NLM and EPSONGW.NLM.

Check the following points before starting.

Install the appropriate client software, such as Novell Client for Windows 95/98 version 3.4, Novell Client for Windows version 4.8, or Novell Client for Windows XP version 4.9 on client workstations. Make sure they install NDPS.

Outline of settings

The followings are basic steps to use the network interface with the NDPS printing system. Detailed procedures are described in the subsequent sections.

Install EpsonNet NDPS Gateway.

Upload printer driver files to the NDPS RMS server.

Create an NDPS Manager object in NetWare Administrator.

Create a Printer Agent in NetWare Administrator.

Set the printer on the client workstations.

Installing EpsonNet NDPS Gateway on your NetWare server

You can install EpsonNet NDPS Gateway from the Software CD-ROM.

Note:

If an older version of EpsonNet NDPS Gateway is already installed, be sure to unload the NDPS Manager before installing a new version of EpsonNet NDPS Gateway.

Open the NETUTIL folder.

Open the ENGW folder.

Double-click EDPS2***.EXE.

Note:

The last three characters of the file name, represented by asterisks, vary depending on the place of purchase.

For detailed information on EpsonNet NDPS Gateway, see the online guide on the Software CD-ROM.

To view the online guide, follow the steps below.

Open the NETUTIL folder.

Open the ENGW folder.

Double-click index.htm.

Uploading printer driver files to the RMS

After installing EpsonNet NDPS Gateway, you need to upload the printer driver to the Resource Management Service (RMS).

Upload the printer driver to the NetWare server using NDPS Broker. For details on the procedure, refer to the section of NDPS or iPRINT in the NetWare documentation.

Creating an NDPS Manager

Run NetWare Administrator (NWADMN32.EXE) on the client machine. The main browser window appears.

To create an NDPS Manager, click the Directory context icon, and then select Create from the Object menu.

Select NDPS Manager from the list.

Enter the NDPS Manager name in the NDPS Manager Name field.

Browse the Resident server and select where you want the NDPS Manager assigned.

Browse the Database Volume and select where you want the NDPS Manager database assigned.

Click Create. The NDPS Manager icon appears in the main browser window.

Type LOAD NDPSM at the server console, and then select the NDPS Manager you have created.

Creating a Printer Agent

Public Access Printers:
NDPS printers that are available to all network users and not associated with an NDS object. Users can select and print to any public access printer they can view from their workstations. However, these printers do not take full advantage of services such as security and job event notification.

Controlled Access Printers:
NDPS printers that are added to the NDS tree by NetWare Administrator. They are only available to the workstation user through the NDS object list. These printers can take full advantage of the security and management features provided by NDS.

Creating a Printer Agent automatically

Creating a Printer Agent manually

You can create Printer Agents, either public access printers or controlled access printers. The way to create a Printer Agent differs depending on the printer type you choose.

Select a printer type (either public access printer or controlled access printer).

Create a public access printer. If you want to create a controlled access printer, go to step 3.

Create a controlled access printer.

Select Remote (lpr on IP).

Configure it as described below. It is a good idea to print a network status sheet of the network interface and configure the corresponding items.

For Remote (lpr on IP) connection:

IP Address: Enter the IP address of the network interface. You can confirm the IP address on the network status sheet.

When you finish filling in the boxes, press Finish. Follow the on-screen instructions.

The Select Printer Drivers dialog box appears. Select an appropriate printer driver for Windows Me/98 or Windows 2000. Be sure to select the correct printer driver for your printer from the appropriate menus.

Click Continue.

Confirm the Printer Agent that you have just created.

In NetWare Administrator, double-click the NDPS Manager object and click Printer Agent List. Check that the status of the Printer Agent you have just created is “Idle”.

Setting the printer on client workstations

For detailed information on setting the printer on client workstations, see the Novell online documentation.

Top