![[Intel Navigation Header]](/CONTENT/PIX/HEADER.GIF)
Netport(R) II Print Server: Troubleshooting Notes from Tech Support
Contents:
IMPORTANT NOTE THE FOLLOWING:
Unless otherwise specified the term "NetPort(R)" used in this document
refers to NetPort(R) II.
The shipping software for Ethernet is v4.34 and Token Ring is v5.34.
The software is available through Intel's online services.
TOPICS COVERED IN THIS DOCUMENT
These are the topics covered in this document, in this order. The topic
heading will be capitalized and moved to the left margin.
* Ethernet NetPort(R) II print server has Flash update that adds
802.2, SNAP and SFT III support
* NetPort Print Server and NetWare 4
* NetPort Server in print server mode loses connection and needs to
be reset to continue printing
* NetPort Print Server status is "Not Responding"
* Printer or plotter print jobs don't print correctly
* NPADMIN or Netport Manager shows "Attaching-xxxx"
* NetPort Print Server doesn't show under NPLIST or NPADMIN
* Jobs don't print (Printserver mode)
* Jobs print intermittently (Printserver mode)
* Novell print server and file server have the same name
* NetPort Print Server's activity light flashes in 2 blink pattern
* NPADMIN takes a long time to list all NetPort Print Servers
* Upgrading to the latest release of NetPort Print Server software
ETHERNET NETPORT(R) II PRINT SERVER HAS FLASH UPDATE THAT ADDS 802.2, SNAP AND SFT III SUPPORT
This Flash memory update version 4.32 and above adds support for 802.2
and SNAP to the existing 802.3 and Ethernet II frame type protocols. The
frame type the Netport(R) II print server uses is determined by the
position of the two DIP switches on the back panel of the unit. Only
one frame type can be active at one time. The latest software file
NPE434.EXE is available through Intel's online services. It contains a
readme with update instructions.
Setting the Switches on the Netport print server.
------------------------------------
Once updated the following switch settings will select the different
frame types:
Both up 802.3
Both down Ethernet II
Left switch down right switch up 802.2
Left switch up right switch down SNAP
The update also adds support for SFT III.
NETPORT(R) II PRINT SERVER AND NETWARE 4.X
We have done initial testing with the NetPort(R) II print server and
NetWare 4.x. These tests indicate that the NetPort II server in print
server mode will work with NetWare 4.x in bindery emulation mode.
Installation requires a few additional steps. For step by step
instructions on how to install a NetPort II print server with NetWare
4.x document 6032 is available through Intel's online services. The
NetPort II print server was designed for use with NetWare 2.x and 3.x,
therefore, Intel makes no claim that all functionalities of the NetPort
print server will work with NetWare 4.x.
Intel's current plan is to support NetWare 4.x directory services with
the NetportExpress print server product line only.
NETPORT(R) SERVER IN PRINT SERVER MODE LOSES CONNECTION AND NEEDS TO BE RESETTO CONTINUE PRINTING
Symptom
The NetPort(R) server is set up in print server mode and it loses
connection to the file server and no longer shows up under Pconsole's
Print Queue Information/"Queue_name"/Currently Attached Server menu.
When this occurs, the NetPort print server needs to be reset in order
for the printer to resume printing.
Description
For NetPort II print servers that are exhibiting this problem, the fix
has been included in release versions 5.25 and 4.25 (Token Ring and
Ethernet respectively) or later of that software. Information on how to
use the Intel online services to download new releases of software is at
the end of this document.
Another reason for this symptom on an Ethernet network is the cabling.
Be sure the NetPort is within 100 meters of the hub or concentrator on a
10BaseT network or that the thin wire segment is not longer than 185
meters. NetPorts are not tolerant of cables that are longer than the
IEEE specification. Even if a workstation works on the cable, the cable
may be beyond the specifications. Some network adapter cards are much
more tolerant of long cable lengths.
There have been field reports that increasing the QSCAN setting may help
prevent the NetPort from disconnecting when the NetPort is used in print
server mode. Use the following command: NP2CON NPxxxxxx QSCAN=80.
NETPORT(R) PRINT SERVER STATUS IS "NOT RESPONDING"
Symptom
From NPADMIN or Netport(R) Manager the NetPort shows the status as "Not
Responding". This can be caused by a number of factors including a
Token Ring NetPort on a UTP network at 16 Mbps or a workstation running
a non-NetWare approved IPX.
Description
The problem in this case is that the NetPort is registered in the
Bindery but cannot communicate with the workstation running NPADMIN or
Netport Manager.
* Try a different workstation, or try putting the NetPort on another
drop or, if this is a Token Ring network, try a workstation on a
different ring.
Other items to check are:
* Check to make sure the communication path between the NetPort and
the workstation is not hampered.
* If a Token Ring Netport is running on a 16 Mbps UTP network, it may
not work correctly; Token Ring NetPort is supported ONLY on an STP
network at 4 or 16 mbps, or on a 4 Mbps UTP ring.
* Try viewing the NetPort information from a workstation with a
Novell approved IPX configuration.
* Token Ring Netport is reported to not communicate with the Xircom
Pocket LAN adapter. Use a different workstation.
* Check that the cabling segment is within IEEE specification.
Cabling that is used to connect a workstation adapter may be
longer than the specification. Many adapters can withstand longer
cable lengths. The NetPort is more sensitive than some
workstations to cables that are longer than the specification than
some workstations.
* Running BINDFIX may help as a last resort.
* You may have set the dip switches to 802.2, but your firmware is a
version prior to v4.32.
PRINTER OR PLOTTER PRINT JOBS DON'T PRINT CORRECTLY
Symptom
There are many symptoms of print jobs not printing correctly including:
* Text files work fine but graphics files print incorrectly.
* Print jobs have extra ASCII characters in the middle of the print
job.
* Several pages have little text and extra ASCII characters at the
top of each page.
* Columns are out of line.
Description
One of the main items to check when print jobs do not print correctly is
the settings on the Novell capture command. The NT [no tabs - defines
the job as a byte stream (graphics) file] flag should be added. Also the
TI [time out - defines the number of seconds before a print job will
close and be sent to the queue for printing] flag should be checked. A
sample capture command would be:
Capture Q=leohp TI=50 NT
Note: For some rare situations the TI value must be set as high as
400. (maximum is 1000 seconds)
The next item to check is the length and condition of the printer cable.
Parallel cable should not be longer than 6 feet. Serial cables should
not be longer than 25 feet. Also check that the correct printer driver
is selected in the application. Frequently printing problems are
directly related to the cable. When in doubt, try swapping the cable.
If the NetPort(R) is in the print server mode, and the printer device is
a plotter, set the XR (XON/XOFF and Request to Send) option for the
handshake parameter. Anytime the NetPort prints to a serial device, the
parameters on the printer and the NetPort must match exactly (Baud,
Databit, Stopbit, Handshake, Parity).
Try connecting your printer to parallel port 2. Parallel port 1 is the
high speed port and occasionally a printer will only work properly on a
traditional speed parallel port.
NPADMIN OR NETPORT(R) MANAGER SHOWS "ATTACHING-XXXX"
Symptom
The NetPort(R) print server has been configured and reset, but it still
shows "attaching-xxxx" under Netport(R) Manager or NPADMIN. The Netport
print server will NOT print when it is in this mode. There are many
possible reasons for the Netport print server remaining in this mode.
Document 6015 that focuses on troubleshooting with the "Attaching"
options is available through Intel's online services.
Description
* Attaching-RP
If the NetPort print server is configured for the Print Server
mode, check that the file server and any Novell print server
defined do not have the same name. The file server and Novell
print server must have unique names. See the section relating to
this subject toward the end of this document for more information.
* Attaching-PS
If this is an Original NetPort print server with any version of
Flash software or a NetPort II print server with Flash software
version less than 5.25 or 4.25 and the NetPort print server is in
print server mode and the server is a Netware 3.x server, check
that unencrypted passwords is turned on. This is accomplished by
typing the following command at the 3.x file server: "set allow
unencrypted passwords=on".
If this is a NetPort II print server with Flash software versions
4.25 or 5.25 or later the encrypted passwords are supported. This
feature will only be available for the NetPort II print server .
This feature indicates that the "set allow..." command is not
needed for the NetPort II print server to log into the 3.x file
server.
* Attaching-PS
If the NetPort print server status is Attaching-PS and the problem
is not with encrypted passwords, delete and recreate the print
server and queue server entries in PCONSOLE. If this was first
created with NPADMIN v1.49 or below, update to the newest NPADMIN
to correct this problem.
* Attaching-PS or Attaching-RP
If the NetPort print server was configured manually (not using
NPADMIN), verify the entries in Pconsole by following the "set up
NetPort as a Print server" or "Set up NetPort with Remote printers"
section of the manual.
NoteIn remote printer mode do NOT use -p or -s notation in the NAME
field of PCONSOLE.
* Attaching-SN or Attaching-PSRP
If the NetPort print server was configured manually (not using
NPADMIN) verify that the SERVERNAME= parameter was set. This is
done from the command line as follows:
np2con npxxxxxx servername="name_of_server"
where "name_of_server" is the name of the file server the NetPort
print server will attach to when in print server mode or the name
of the NetWare Pserver when the NetPort print server is in remote
printer mode.
NoteThat NPADMIN sets the SERVERNAME= parameter automatically.
* Attaching-PS
If the NetPort server is in Print Server mode, check that the file
server, to which the NetPort print server will attach to, has an
open connection slots available. If not, a connection slot will
need to be cleared for each NetPort server.
* Attaching-PS
If the NetPort print server was configured with NPADMIN v1.49 or
below; rarely, there has been a problem where an NPADMIN print
server configuration of a NetPort print server did not work, but
manually defining it in Pconsole worked fine. Version 1.83 of
NPADMIN fixes this problem. The newest version of NPADMIN is
available by downloading or connecting to the Intel online
services.
* Attaching-xxxx
Occasionally, the NetWare bindery becomes corrupt. Run the NetWare
BINDFIX supervisor utility. Then rerun NPADMIN and configure the
NetPort print server again or manually reenter the NetPort
information in Pconsole and reset the Netport.
NETPORT(R) PRINT SERVER DOESN'T SHOW UP UNDER NETPORT(R) MANAGER OR NPADMIN
Symptom
Netport(R) Manager or NPADMIN does not list the NetPort print server.
There are many possible reasons for the NetPort print server to not
appear on the network.
Description
* Try another network connection that is known to work.
* The NetPort print server failed the POST test and the Activity
Light is flashing in a repeated pattern. The NetPort print server
must pass POST before it comes up on the network. If it fails this
test, it will flash in a repeated pattern. Check the front LED on
the NetPort, if flashing, see the "Activity Light Blinks" section
in your NetPort manual.
* If this is a NetPort 10base-T print server, be sure it is connected
to a true 10Base-T hub. The NetPort print server does not support
pre-10Base-T hubs.
* If this is a Token Ring NetPort print server on a UTP network, be
sure the network is running at 4Mbps. The Token Ring NetPort print
server does not support UTP at 16 Mbps but does support STP at 4/16
Mbps or UTP at 4 Mbps.
* Make sure the cables to the NetPort print server do not exceed the
IEEE Ethernet specifications. Be sure the NetPort print server is
within 100 meters of the Hub or concentrator on a 10BaseT network
or that the thin wire segment is not longer than 185 meters.
NetPort print servers are not tolerant to cables that are longer
than the IEEE specification. Even if a workstation works on the
cable, the cable may be beyond the specifications. Some network
cards are much more tolerant of long cable lengths.
* The NetPort print server may be configured to the 802.3 protocol
but is trying to be accessed from an Ethernet type II or 802.2
workstation. Verify the frame type DIP switches match the frame
type on your network.
The Ethernet version of the NetPort II print server has 2 toggle
switches to set packets. These switches are recessed on the back
panel of the NetPort print server. If you are not sure which
packet type you are using, go ahead and change the switch and see
if that makes a difference. Use a pen to reach inside the back
panel and change the switch settings (Do not use a pencil as the
graphite crumbs act as conductors and may cause a short). If it
does not make a difference, then switch back to the original
settings. For the proper switch settings,see "Setting the Switches
on the NetPort print server" in the section of this document titled
"Ethernet NetPort II Print Server has Flash Update that Adds 802.2
and SNAP Support."
JOBS DON'T PRINT (PRINT SERVER MODE)
Symptom
NetPort(R) is in Print server mode and print jobs are not printing. If
the printer is a serial printer, the print jobs will leave the NetWare
queue, but never print. If the printer is a parallel printer, the print
jobs remain in the NetWare queue.
Description
* Most often the cause of jobs not printing are cabling problems.
For serial printers, the cable must be a serial printer cable (a
modem cable will NOT work with printers). Some printer
manufactures require specific cable pinouts. Check your printer
manual for the recommended cable. The NetPort manual has three
serial cable pinouts that may be helpful.
Make sure handshaking parameters (baud, parity, stop bits, data
bits, xon/xoff cts/rts) are set the same for the NetPort and the
printer. We recommend using the XON/ RTS (Xon/Xoff & Request to
send) parameter of the NetPort when attached as a print server to a
plotter.
For parallel printer be sure the cable is a known working cable
that does not exceed 6 feet. A high number of printing problems
can be traced to printer cable problems.
* Another common cause for Print jobs not printing is that the
NetPort is not connected to the file server. In Pconsole check the
Currently Attached Server for the NetPort Print queue in Print
Queue Information. If the Netport IS listed, be sure it is the
ONLY print server listed. If the NetPort IS NOT listed then check
the following sections of this document: Netport Manager or NPADMIN
shows ATTACHING-xxxx or NetPort in Print server mode needs to be
reset to continue printing for possible solutions.
* Another cause could be that the Netport Manager's status display or
NPADMIN's Port status/Check all ports status field indicates that
the NetPort is Off Line (-OL) or Halted for Form (-HF). If -OL,
check the printer and the cable. The printer may be out of paper.
Resetting the printer often helps. -OL is often caused by a
faulty, loosely connected, or incorrect pinout cable. -HF
indicates that the printer will not print until a new form is
mounted. Use NPADMIN to change the form or issue the command:
NP2CON NetPort_name FORM=NEW. If you do not wish to use forms,
issue the command: NP2CON NetPort_name FORM=OFF.
JOBS PRINT INTERMITTENTLY (PRINTSERVER)
Symptom
NetPort(R) is in print server mode. The first job prints fine but other
jobs seem to get lost. Some jobs print and some don't.
Description
Possible solutions include:
* The NetPort print server is not the ONLY print server attached to
the queue. In Pconsole check PRINT QUEUE INFORMATION/CURRENTLY
ATTACHED SERVERS. If additional print servers are displayed,
delete the queue and recreate it with just the NetPort print server
in PRINT QUEUE INFORMATION / QUEUE SERVERS.
* The NetPort print server's serial port is configured but a serial
printer is not physically attached, thus every other job is going
out the serial port. In Pconsole check PRINT QUEUE
INFORMATION/QUEUE SERVERS. If the serial port is defined
(npxxxxxx-s or new_name-s) and not being used, delete it and reset
the NetPort print server.
* Check the parallel cable length - maximum length is 6 feet.
NOVELL PRINT SERVER AND FILE SERVER HAVE THE SAME NAME
Symptom
NetPort(R) II uses the SERVERNAME= parameter to determine which mode it
should become: print server or remote. If the NetWare print server and
the file server have the same name there will be problems setting up the
NetPort in its Print server mode.
Description
The NetPort print server is defined as a print server on a network where
a file server and any Novell print server have identical names. The
NetPort print server will find the Novell Print server name first, for
the name defined in SERVERNAME= parameter. When this happens, the
NetPort print server will never look for the file server name and will
show a status of ATTACHING-RP.
Be sure there are no Novell Pservers on the network that have the same
name as a Novell File server being used by the NetPort print server.
NETPORT(R) PRINT SERVER'S ACTIVITY LIGHT FLASHES IN 2 BLINK PATTERN
Symptom
Anytime a NetPort(R) print server is reset, it goes through a POST
(Power on Self Test). If a failure is found, the NetPort's activity
light will flash in a pattern indicating what failure was found. A 2
flash pattern indicates a Flash memory checksum error.
Description
If a Flash memory checksum error is discovered (2 flashes), the NetPort
will not come up on the network and will not show under NPAdmin or is
greyed out in Netport Manager. This should be verified by removing all
printers attached to the NetPort and resetting the NetPort by
re-engaging the power. If the 2 flashes continue, normally a RMA
(Return Merchandise Authorization) is required.
To get a RMA number, call the appropriate technical support number
listed in your manual. Have the NetPort, the serial number, your fax
number and your shipping address handy when you call.
NPADMIN TAKES A LONG TIME TO LIST ALL NETPORT(R) PRINT SERVERS
Symptom
If NPADMIN is run from a wide area network that has NetPort(R) print
servers located across the WAN, NPADMIN may take a long time to register
the NetPorts. Using the command line utilities to configure the NetPort
print server is one way to avoid this problem.
Description
Most menu options in NPADMIN list all of the NetPort print servers on a
network. In a wide area network, NPADMIN will search all parts of the
network for NetPort print servers including connections across T1 lines.
This process can cause a long delay in the NPADMIN program.
The easiest way to manage Netports in a wide area network is to use
Netport Manager on a station running Windows and group Netports in
separate domains through Domain Maintenance. Netport Manager will
communicate only with those Netports in the selected domain.
Another way to avoid this problem is to filter the NetPort print server
SAPs. This can be done on most routers.
Trademark information