TechNote 170-05
microLaser 170
Attaching to a Novel NDS Queue
21 Aug 2001 Ed Palmer

Summary: This note documents the steps required to attach the printer with the internal network interface card to a NetWare 4 NDS Queue.

To setup the network interface card, the user must login and open a control session. A session can be opened via TCP/IP with telnet, or via IPX/SPX (NetWare) with the SPXCON utility.

Open a NIC session, login as superuser and issue the following commands:

Local_4>> show protocols

The Name field is shown in the top right of this display. This name is the print server name. For example:

Print Server: PRQ_123456

After the Print Server name, there will be a slash (/) and a number- ignore this.

If desired, the Print Server name can be changed.

Local_4>> show services local

The Print Service names will be listed. This example will be used:

Print Service: PRQ_123456_BIN

The BIN service should normally be used under most operating systems. The TEXT service adds CR on LF and a formfeed at the end of job.

Leave the session open for further configuration.

Log onto the NDS server with administrator rights.

Open PCONSOLE on NWADMIN.

From the NDS Directory Tree, browse to and select the context in which the printer is to be installed.

Note the NDS Tree, the NDS Context and the Fileserver name.

Examples:

NDS Tree: dstree

NDS context: OU=Accounts.OU=Finance.O=YourCo

For a discussion of context, refer to Novell. The Net32 NIC uses the typeful nameing convention.

Fileserver: server

Select Tool >> Print Service >> Quick Setup

In the Quick Setup dialog, enter the following information:

Print Server: PRQ_123456

This must match the Print Server name on the printer.

New Printer: PRQ_123456_BIN

This must match the Print Service name on the printer.

New Print Queue: Bob_Printer

This can be any desired name.

Type: Other/Unknown

All other options should be set to default.

Select Create.

If not already open, open a NIC session and login as superuser:

Enter the NDS information:

Local_4>> define protocols netware access server

Local_4>> define protocols netware dstree dstree

Local_4>> define protocols netware dscontext ou=unit.o=organization

For a discussion of context, refer to Novell. The Net32 NIC uses the typeful nameing convention.

Local_4>> init delay 0

This reboots the print server- the host connection will be lost.

After about one minute, the printer will attach to the NDS queue.

The following network interface commands can be used to resolve connection issues:

netstat

Fileserver:
Queue:
State: JobPoll indicates the print server has successfully attached to the queue.

show protocols netware access

This will return the list of file servers in the access list.

show protocols netware nds

Failure: #
DSTree: tree
DSContext: context

Code	Failure
0	Success
1	Print server out of memory
2	Unexpected response from file server
3	Unexpected response from file server
4	No printers found for the print server. Check to make sure there are printers for the print server and the printer names match the service names on the print server.
5	No queue found for the printer. Check to make sure that the printers have associated queues
6	Login failed. Check to make sure there is a print server object configured with the same name as the print server. Ensure the NDS Print Server name matches the NIC Print Server name.
7	Authentication failed. Check that the login password on the print server is the same as the password for the print server object. If the login password on the print server is the default ("ACCESS") then there should be NO password for the print server object.
8	Print server cannot attach to queue. Check the directory services partitions, replicas, and volumes to make sure that the file server where the queue actually lives has the information about the print server and printers

Code	NDS Failure
0	Sucess
fffffda7	Object could not be found in the given context. Check the print server name, dscontext, and dstree to make sure that the print server is set up correctly with PCONSOLE
fffffda5	The requested attribute could not be found. Check the print server with PCONSOLE and make sure the print server has associated printers and that the printers have associated queues. Wait a few minutes and try a SET PROTO NET RESET to rescan the network.
fffffd69	Directory Services Database is locked. An administrator is probably accessing the database. Wait a few minutes and try a SET PROTO NET RESET to rescan the network.
fffffd63	Invalid password. Make sure the password for the print server object under PCONSOLE is the same as the login password for the print server. If the login password on the print server is the default ("access") then there should be NO password for the print server object. If the login password is something other than the default, then the password for the print server object should match.
fffffd54	Secure NCP violation. The file server requires NCP packet signature which is not currently supported.

Ensure the printer has a IP address and Subnet mask:

Menu >> Interface >> Network x setup >> IP Address = 10.001.001.123

Menu >> Interface >> Network x setup >> Subnet Mask = 255.255.255.000

The IP address and subnet mask shown are examples. Use the address and mask provided by the IT group.

Ensure the printer can be pinged from the host:

Ping 10.1.3.123

Open a session and issue the following commands:

telnet 10.1.1.123

This address is an example.

Network Version V1.0/7

Ensure the network version is 1.0/7 or higher. If the version is lower, upgrade before proceeding.

Username> bob

The username can be any desired name.

Local_4> su

This is the superuser login.

Password> system

The password system does not show.

Local_4>>

The >> prompt indictes superuser mode.

Download SPXCON to a known folder. SPXCON is a stand-alone DOS application and does not require installation.

Open a DOS prompt and navigate to the folder SPXCON was saved to.

SPXCON usage:

SPXCON LIST - Shows all compatible devices on the network.

If the list of devices is longer than the screen, use the comand SPXCON LIST |MORE to pause at the end of a screen.

SPXCON <name> - Where name is the printer name, establishes a session to the NIC.

At the # prompt, enter the password "access".

spxcon PRQ_1234546

This address is an example.

# access

The password "access" does not display.

Network Version V1.0/17(010503)

Ensure the network version is 1.0/17 or higher. If the version is lower, upgrade before proceeding.

Username> bob

The username can be any desired name.

Local_4> su

This is the superuser login.

Password> system

The password system does not show.

Local_4>>

The >> prompt indicates superuser mode.

To change the server name, open a NIC session and login as superuser. Issue the following commands:

Local_4>> define server name name

The server name is a maximum of ten alphanumeric characters. For NetWare, all characters must be uppercase. Spaces are not allowed. When the server is renamed, the default services are renamed to match.

The name will take effect after rebooting the print server with:

Local_4>> init delay 0

Do not reboot the server if further setup is required- complete the setup first.

Copyright © 2002 GENICOM, Specifications subject to change without notice. ® All trademarks are property of their respective holders at the time of this publication. If you have any questions or comments regarding this document, please contact TallyGenicom Technical Support. TallyGenicom has taken care to ensure that the information is complete, accurate and up-to-date. However, GENICOM assumes no responsibility for errors or omissions which may occur. All the information provided is subject to change from time to time at the sole discretion of GENICOM. This information is provided "as is" without warranty of any kind. GENICOM disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall GENICOM, or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if GENICOM, or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.