[Intel Navigation Header]

    NetportExpress(TM) XL/EL Print Server: Troubleshooting Notes

    Contents:

    • TOPICS COVERED IN THIS DOCUMENT
    • "NO LAN MANAGER AND LAN SERVER WAS FOUND RUNNING THE INTEL MONITOR PROGRAM. PROGRAM TERMINATED."
    • NETPORTEXPRESS PRINT SERVER OUTPUTS GARBAGE ON SOME PRINTERS
    • NETPORTEXPRESS(R) PRINT SERVER PRINTS "GARBAGE" CHARACTERS.
    • NPADMIN FOR NETPORTEXPRESS XL PRINT SERVER REQUIRES 512 KB CONVENTIONAL MEMORY
    • JOBS PRINT WITH DOUBLE SPACE BETWEEN EACH LINE
    • USER IS UNABLE TO HIGHLIGHT "PRINT MODES SETUP" DURING INSTALLATION
    • NETPORTEXPRESS PRINT SERVER DOES NOT SHOW UNDER NPADMIN OR NETPORT MANAGER
    • NPADMIN REPORTS "NOT RESPONDING" OR NETPORT MANAGER SHOWS THE XL/EL GRAYED OUT
    • PRINTER OR PLOTTER PRINT JOBS DO NOT PRINT CORRECTLY
    • JOBS DO NOT PRINT (PRINT SERVER MODE)
    • JOBS DO NOT PRINT (REMOTE PRINTER MODE)
    • NPADMIN TAKES A LONG TIME TO LIST ALL NETPORTEXPRESS XL SERVERS
    • ACTIVITY LIGHT FLASHES IN 2 BLINK PATTERN
    • NPADMIN HANGS THE SYSTEM OR NETPORT MANAGER RETURNS ERROR: "IPX INITIALIZATION FAILED!" OR "IPX INITIALIZATION ERROR"
    • UPGRADING YOUR EXISTING NETPORTEXPRESS XL PRINT SERVER
    • NETPORTEXPRESS PRINT SERVER WITH NETWARE 4
    • NPADMIN SHOWS "ATTACHING-XXXX"
    
    

    TOPICS COVERED IN THIS DOCUMENT

    
         *  "No LAN Manager* and LAN Server* was found running the Intel
    
            Monitor program. Program terminated."
    
    
    
         *  NetportExpress(TM) print server outputs garbage on some printers.
    
    
    
         *  NPADMIN for NetportExpress XL print server requires 512k
    
            conventional memory .
    
    
    
         *  Jobs print with double space between each line.
    
    
    
         *  User is unable to highlight "Print Modes Setup" during
    
            installation.
    
    
    
         *  NetportExpress print server does not show under NPAdmin or Netport
    
            Manager.
    
    
    
         *  NPAdmin reports "Not Responding" or Netport(R) Manager shows the
    
            XL/EL grayed out.
    
    
    
         *  Printer or plotter print jobs do not print correctly.
    
    
    
         *  Jobs do not print (Print Server mode).
    
    
    
         *  Jobs do not print (Remote Printer mode).
    
    
    
         *  NPAdmin takes a long time to list all NetportExpress XL servers.
    
    
    
         *  Activity Light flashes in 2 blink pattern.
    
    
    
         *  NPADMIN hangs the system or NetPort Manager returns error: "IPX
    
            Initialization Failed!" or "IPX initialization error".
    
    
    
         *  Upgrading your existing NetportExpress XL Print Server.
    
    
    
         *  NetportExpress print server with NetWare 4.
    
    
    
         *  NPAdmin Shows "Attaching-xxxx".
    
    
    
    

    "NO LAN MANAGER AND LAN SERVER WAS FOUND RUNNING THE INTEL MONITOR PROGRAM. PROGRAM TERMINATED."

    
       Symptom
    
       Launching Netport Manager fails with the following message:
    
    
    
       No LAN Manager and LAN Server were found running the Intel Monitor
    
       program. Program terminated.
    
    
    
       Netport Manager will not launch.
    
    
    
       Description
    
    
    
         *  The monitor program (LMNPMON.EXE) isn't running on at least one
    
            NetBIOS file server.
    
    
    
         *  Communication between the workstation and the NetBIOS file server
    
            that's running the Monitor is hampered.
    
    
    
         *  The workstation is running IBM DOS requester and has the maximum
    
            number of NETBIOS Interface Commands (NCB) set too low.  The
    
            default is 12.
    
    
    
       Solution
    
    
    
       As of version 3.01 and above,  Netport Manager now provides NetBIOS
    
       support for Windows NT, Windows for Workgroups, LAN Manager and IBM LAN
    
       Server, and LMNPMON.EXE is no longer required.  Update Netport Manager
    
       and the NetportExpress(TM) print servers to the current firmware version
    
    
    
         *  If the workstation is running IBM DOS requester, edit the
    
            config.sys file to increase the NetBIOS Interface commands (NCB) to
    
            30.  This is done by editing the line device=c:\dxmt0mod.sys and by
    
            either adding C=30 or if C= already exists then increasing it to
    
            30.  The line should look as follows:]
    
    
    
            Device=c:\dxmt0mod.sys C=30
    
    
    
       Note:     There may be other parameters on the same line such as ST=12
    
       S=12 ES=6 EST=6 0=Y CR=Y CF=Y
    
    
    
       Reboot after making the change.
    
    
    
    

    NETPORTEXPRESS PRINT SERVER OUTPUTS GARBAGE ON SOME PRINTERS

    
       Symptom
    
       Some slower printers cannot keep up with the NetportExpress print server
    
       parallel port throughput when "Medium Speed Centronics" is in use.  The
    
       "Medium Speed Centronics" interface with the NetportExpress print server
    
       is the default setting.
    
    
    
       Description
    
       Set the parallel port(s) to "Low Speed Centronics".  This will slow the
    
       port to make it compatible with slower speed printers.  This option is
    
       available in v3.00 of NPAdmin and in Netport Manager.  These versions
    
       are available through Intel's online services in the current release
    
       section.
    
    
    
       If you are using NPAdmin, the steps to set the "Low Speed Centronics"
    
       are:
    
    
    
         1. Invoke NPADMIN (NPAdmin must be v3.00 or above) and select the
    
            'Manual' option from the configure menu.
    
    
    
         2. Select 'Box and Port Settings'.
    
    
    
         3. In the Parallel Port 1 Interface field (or the Parallel Port 2
    
            interface field depending on which port is connected to the
    
            printer), press <insert>.
    
    
    
         4. From the option list, select "Low Speed Centronics".
    
    
    
         5. To accept the new parallel port interface configuration press F10.
    
    
    
       If you are using Netport Manager, set the parallel port to "Low Speed
    
       Centronics" as follows:
    
    
    
         1. Invoke Netport Manager.
    
    
    
         2. Select an XL in the Netport list box.
    
    
    
         3. Choose configure.
    
    
    
         4. Choose Netport Hardware.
    
    
    
         5. Select Centronics Low in the Parallel Port 1 or Parallel Port 2
    
            list box.
    
    
    
         6. Choose OK 
    
    
    
    

    NETPORTEXPRESS(R) PRINT SERVER PRINTS "GARBAGE" CHARACTERS.

    
       Customer Report
    
    
    
       Symptom: 
    
       NetportExpress(TM) print server prints "garbage" characters.
    
    
    
       Description 1: 
    
       Port speed is set wrong or capture command is missing the NT parameter.
    
    
    
       Solution 1: 
    
       Set port speed to LOW or add NT parameter to capture command.
    
    
    
       Description 2:  
    
       NetportExpress print server  RBL is v3.04 or lower.
    
    
    
       Solution 2: 
    
       Update the NetportExpress print server RBL and Application code to
    
       newest version.
    
    
    
       Description 3:
    
       The printer may be an HP Laserjet* III with old internal firmware.
    
    
    
       Solution 3: 
    
       Some customers have reported that HP has told that they've seen this
    
       problem with other print servers (not just Netport Express(TM) print
    
       server.  This problem can be caused by outdated firmware on the
    
       motherboard of the printer.  To check the firmware on the printer, do
    
       the following: 
    
    
    
         1. Take the printer offline. 
    
    
    
         2. Press and hold the TEST button until the word SELFTEST appears in
    
            the LCD panel.  
    
    
    
         3. Printer will print a Test Page.
    
    
    
       On the Test Page, the firmware version is listed as the FIRMWARE
    
       DATECODE, which appears about 1/3 of the way down the test page.
    
       Bad Firmware is identified by the date - 19900430
    
       Good Firmware has the date identifier  - 19901209
    
       Additionally, the Part Number of a known good firmware board is
    
       33494-69001. We have been told this is a whole new motherboard and is
    
       somewhat expensive).
    
    
    
        We have not confirmed this with HP.
    
    
    
    

    NPADMIN FOR NETPORTEXPRESS XL PRINT SERVER REQUIRES 512 KB CONVENTIONAL MEMORY

    
       Description
    
       The DOS NPADMIN that ships with Netport II print servers also be used
    
       with NetportExpress XL print server (it doesn't support the
    
       NetportExpress EL print server).  Because NPADMIN supports all the
    
       current versions of the NetPort print servers, more memory is required
    
       than in the previous versions.
    
    
    
       Symptom
    
       The symptoms of NPADMIN running on a workstation with insufficient
    
       memory varies.  In some extreme cases NPADMIN may not even execute while
    
       other times NPADMIN may start to work but fails while running. 
    
       Generally this happens when NPADMIN attempts to paint a new window. 
    
       Because it doesn't have enough memory to create the window, it appears
    
       to be stuck at the current screen.  Any type of abnormal behavior from
    
       NPADMIN may be caused by insufficient memory.
    
    
    
       Solution
    
    
    
         1. To run NPADMIN from your workstation, check to make sure you have
    
            at least 512-KB conventional memory free.  You can check this by
    
            running the MEM command from DOS.  The third line, "largest
    
            executable program size" reports the amount of conventional memory
    
            available.  It should be 524288 or greater.  If you have less than
    
            524288 you will need to reconfigure your workstation.  Generally
    
            this requires moving some of the drivers that are in conventional
    
            memory to upper memory (area between 640 KB & 1 MB).  Refer to your
    
            DOS manual for more information on loading drivers into upper
    
            memory.
    
    
    
         2. Use the Windows Interface, Netport Manager.  If you purchased your
    
            XL before Netport manager was available, it is available from
    
            Intel's online services.
    
    
    
    

    JOBS PRINT WITH DOUBLE SPACE BETWEEN EACH LINE

    
       Description
    
       Printouts have an extra space (line feed) between each line.
    
    
    
       Symptom
    
       The NetportExpress print server's parallel port supports Auto Line Feed.
    
        If Auto Line Feed is enabled, a line feed is inserted after each
    
       carriage return by enabling pin 14 on the parallel port to go active
    
    
    
       high.  If Auto Line Feed is turned off and you are still having this
    
       problem, then there is probably an issue with pin 14.  The threshold of
    
       pin 14 is such that the printer recognizes it as an active high and adds
    
       the line feed. 
    
    
    
       Solution
    
    
    
         *  Try a different printer cable.  If that doesn't work then you will
    
            have to prevent connectivity of pin 14.  This can be done by
    
            removing pin 14 from the parallel cable or putting finger nail
    
            polish on pin 14 to prevent connectivity.
    
    
    
         *  Update the NetportExpress XL print server firmware and RBL code
    
            tothe latest firmware release.  Use Netport(R) Manager v2.2 or
    
            later to disable the Auto Line Feed setting for the NetportExpress
    
            print server.  You can find the updates on Intel's online services
    
            in the files NPXL1.EXE and NPXL2.EXE.  These files contain the
    
            latest version of NetPort Manager.  The readme file contains update
    
            instructions.
    
    
    
            After you update the NetportExpress XL print server firmware and
    
            RBL code to the latest version, use Netport Manager 2.2 or later to
    
            set the parallel port to disable "Auto Line Feed" as follows:
    
    
    
       1.   Invoke Netport Manager
    
    
    
       2.   Select an XL in the Netport list box.
    
    
    
       3.   Choose configure.
    
    
    
       4.   Choose Netport Hardware.
    
    
    
       5.   Choose Ports.
    
    
    
       6.   Deselect the box for Auto Line Feed.
    
    
    
       7.   Choose OK.
    
    
    
    

    USER IS UNABLE TO HIGHLIGHT "PRINT MODES SETUP" DURING INSTALLATION

    
       Symptom
    
       The user is unable to highlight "Print Modes Setup" in the Configure
    
       section of NPAdmin or "protocols" in Netport Manager during a new
    
       installation.
    
    
    
       Description
    
       The Application file has not been copied into the RBL server's SYS:Login
    
       directory.  Or, the NetportExpress print server has not been able to
    
       download the Application file from the RBL server's SYS:Login directory
    
       to its RAM. The Print Modes Setup or Protocols remains grayed out until
    
       the XL successfully downloads the application file (EN.NPX & TN.NPX for
    
       the XL, or ENL.NPX & TNL.NPX for the EL).
    
    
    
       Solution
    
       Make sure the Application  file is in the SYS:Login directory of the
    
       "Boot Load" Server.  Netport Manager automatically does this when you
    
    
    
       choose the Boot Load Server.  Make sure the RBL server has been set in
    
       the Box and Port settings screen if you are using DOS NPAdmin.  Next,
    
       reset the NetportExpress server.   Finally, if you have updated the
    
       application file,  make sure you've done an RBL Flash Memory update.
    
    
    
    

    NETPORTEXPRESS PRINT SERVER DOES NOT SHOW UNDER NPADMIN OR NETPORT MANAGER

    
       Overview
    
       NPAdmin or Netport Manager does not list the NetportExpress print
    
       server.  There are many possible reasons for this but, basically, if the
    
       unit doesn't list at all under NPAdmin or Netport Manager, then the unit
    
       is not getting in the bindery of the file server your workstation is
    
       attached to.
    
    
    
       Description
    
    
    
         *  Try another network connection that is known to work.  Try Netport
    
            Manager from a different workstation.
    
    
    
         *  The NetportExpress print server must pass the POST test before it
    
            comes up on the network.  If it fails this test, it will flash in a
    
            repeated red pattern.  Check the front LED on the unit.  If it is
    
            flashing, please see the "Activity Light Blinks" section in your
    
            manual.
    
    
    
         *  Ensure that there is no router filtering that would prevent the SAP
    
            packets from crossing the router.
    
    
    
         *  Ensure that Reply to Get Nearest Server (GNS) is enabled on at
    
            least one Netware file server.  On Boot-up the NetportExpress print
    
            server requires a response to GNS in order to broadcast on the
    
            network and show up under NetportManger.
    
    
    
         *  Make sure the cables to the unit do not exceed the IEEE Ethernet
    
            specifications.  Be sure the unit 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.  NetportExpress print servers 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 cards are much more tolerant of
    
            long cable lengths.
    
    
    
         *  Make sure the NetportExpress print servers frame type is set
    
            correctly.  
    
    
    
            Set the DIP switches on the back panel on the Ethernet XL or EL for
    
            the correct frame type protocol as follows:
    
    
    
            Frame type          Position 1        Position 2
    
            Ethernet II         Up                UP
    
            802.3*              Down              UP
    
            SNAP                Up                Down
    
            802.2               Down              Down
    
            *Default
    
    
    
            Set the DIP switch on the back panel of the Token Ring XL or EL for
    
    
    
            the correct frame type protocol as follows:
    
    
    
            Frame Type          Position 2
    
            802.2               Up
    
            SNAP                Down
    
    
    
       Note:     SW1 (the push button) and SW2 position 2,3 & 4 are not in use.
    
    
    
    

    NPADMIN REPORTS "NOT RESPONDING" OR NETPORT MANAGER SHOWS THE XL/EL GRAYED OUT

    
       Overview
    
       From NPAdmin, the status of the NetportExpress XL print server is "Not
    
       Responding" or Netport Manager shows the XL or EL ID number grayed out
    
       and can't be accessed..
    
    
    
       Note:     NPAdmin's Check All Ports reports "RBL not defined" while all
    
       other screens report "Not Responding".
    
    
    
       Description
    
       The problem in this case is that the NetportExpress print server is
    
       registered in the bindery, but cannot communicate with the workstation
    
       running NPAdmin or Netport Manager.  This typically happens for about 2
    
       minutes after a unit is removed from the network because NetWare takes
    
       about 2 minutes to remove a device from the bindery.
    
    
    
       For those situations where the unit is still connected to the network,
    
       try the following:
    
    
    
         *  Try a different workstation, or try putting the XL or EL on another
    
            drop.
    
    
    
         *  Check to make sure the communication path between the XL or EL and
    
            the workstation is not hampered.
    
    
    
         *  Try viewing the NetportExpress print server information from a
    
            workstation with a Novell approved IPX configuration.
    
    
    
         *  Check that the cabling segment is within IEEE specification. 
    
            10baseT cabling should not exceed 100 meters and thin wire should
    
            not exceed 185 meters.  Cable that is used to connect a workstation
    
            adapter may be longer than the specification.  Many adapters can
    
            withstand longer cable lengths.  The NetportExpress print server is
    
            much more sensitive to cables that are longer than the
    
            specification.
    
    
    
         *  Running BINDFIX may help as a last resort.
    
    
    
         *  There is a hard coded time out when NPAdmin or Netport Manager
    
            queries an XL or EL.  If NPAdmin or Netport Manager doesn't hear
    
            back from the device within this time period, NPAdmin reports Not
    
            Responding or Netport Manager show the XL or EL greyed out.  This
    
            sometimes happens on busy networks when the NetportExpress print
    
            server is connected across wide area links.
    
    
    
    

    PRINTER OR PLOTTER PRINT JOBS DO NOT PRINT CORRECTLY

    
       Symptom
    
       There are many symptoms of print jobs not printing correctly, including:
    
    
    
         *  Text files work fine but graphic 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.
    
    
    
       Solution
    
       Set the parallel port to "Low Speed Centronics."  For more information,
    
       see the section on "NetportExpress Print Server outputs garbage on some
    
       printers" in this document.
    
    
    
       Description
    
       One of the main items to check when print jobs do not print correctly is
    
       the settings on the NetWare capture command.  The NT (no tabs - defines
    
       the job as a byte stream (graphic 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 of the printer cable.  Parallel
    
       cable should not be longer than 6 feet.  Serial cables should not be
    
       longer than 25 feet.  Many times printing problems are resolved by
    
       swapping printer cables.
    
    
    
       Next, check that the printer driver selected in the application matches
    
       the printer.
    
    
    
       If the unit is in the print server mode, and the printer device is a
    
       serial plotter, set the XON/RTS (XON, XOFF and Request to Send) option
    
       for the handshake parameter in the Box or Port Setting window.  Anytime
    
       the NetportExpress server prints to a serial device, the parameters on
    
       the printer and on the NetPort print server must match exactly (Baud,
    
       Databit, Stopbit, Handshake, Parity).  See NPAdmin's Box or Port Setting
    
       window.
    
    
    
       Refer to the section titled, "NetportExpress print server outputs
    
       garbage on some printers" in this document.
    
    
    
    

    JOBS DO NOT PRINT (PRINT SERVER MODE)

    
       Overview
    
       The NetportExpress server is set 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 is a cabling problem.  For
    
       serial printers, the cable must be a serial printer cable (a modem cable
    
       will not work with printers).  Some serial printer manufacturers require
    
       specific cable pinouts.  Check your printer manual for the recommended
    
       cable.  The NetportExpress print server 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 NetportExpress server and the
    
       printer.  We recommend using the XR (Xon/Xoff & Request to send)
    
       parameter when the NetportExpress server is attached to a plotter.
    
    
    
       For parallel printers be sure the cable is a known working cable that
    
       does not exceed 6 feet.  Many printing problems can be traced to printer
    
       cable problems.
    
    
    
       Another common cause for Print jobs not printing is that the unit is not
    
       connected correctly to the queue.  In Pconsole check "Currently Attached
    
       Servers" for the Print queue in Print Queue Information.  If the
    
       NetportExpress server is listed, be sure it is the only print server
    
       listed.  If the unit is not listed then check the following section of
    
       this document: NPAdmin shows ATTACHING-xxxx.
    
    
    
       Another cause could be that NPAdmin's Port status/Check all ports status
    
       field indicates that the NetportExpress print server is Off Line (-OL)
    
       or Halted for Form (-HF) or Netport Manager's Status shows Off Line for
    
       Halted for Forms.
    
    
    
         *  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 printer cable or by a printer cable
    
            that is too long.
    
    
    
         *  -HF indicates that the printer will not print until a new form is
    
            mounted.  Use NPADMIN to change the form by selecting
    
            Port-Status/Check All Ports, and highlighting the NPX then press
    
            <enter>.  You will see a box titled Options, choose Change Forms
    
            and press <enter>.  To turn Form Checking off, use NPAdmin's Manual
    
            Configuration option.
    
    
    
    

    JOBS DO NOT PRINT (REMOTE PRINTER MODE)

    
       Overview
    
       The NetportExpress server is set up in the Remote Printer mode using
    
       NetWare's Pserver NLM or EXE.  Print jobs will sit in a queue, or
    
       Pconsole shows the job sitting in the queue.
    
    
    
       Description
    
    
    
         *  Check the status of the unit. If it is in Attaching-xxxx mode
    
            please see the section of this document labeled NPAdmin shows
    
    
    
            ATTACHING-xxxx.
    
    
    
         *  If the XMDFIX.NLM patch is being used, be sure it is the newest
    
            version, v1.02 dated 9/15/92 or newer.
    
    
    
         *  Make sure the PSERVER.NLM version being used is 1.22 or 1.27 or
    
            higher.  Do not user Pserver.NLM v1.26 as it was recalled by
    
            Novell.
    
    
    
    

    NPADMIN TAKES A LONG TIME TO LIST ALL NETPORTEXPRESS XL SERVERS

    
       Overview
    
       If NPADMIN is run from a wide area network that has NetportExpress XL
    
       print servers and/or other Netport servers located across the WAN,
    
       NPADMIN may take a long time to register all the units.
    
    
    
       Note:      NPAdmin doesn't support the NetportExpress EL print server.
    
    
    
       Description
    
       Most menu options in NPADMIN list all of the Netport print servers on a
    
       network.  If the network is a wide area network, NPADMIN will search all
    
       parts of the network.  This can cause a long delay in the NPADMIN
    
       program as NPAdmin must talk to each unit.
    
    
    
       The NetportExpress print server does not support command line utilities
    
       but NPAdmin does have the ability to filter on a particular
    
       NetportExpress server.  This method prevents NPAdmin from having to talk
    
       to all units.  From the command line start NPAdmin as follows:
    
    
    
            npadmin /n=npxxxxxx
    
    
    
            or
    
    
    
            npadmin /n=netport_alias
    
    
    
       This can be set in NPAdmin by selecting the Set Viewing Criteria option
    
       which is located under Port-Status.
    
    
    
       Once an individual NetportExpress server has been filtered on, all
    
       NPAdmin screens will ONLY list that unit.
    
    
    
       Another way to avoid NPAdmin taking a long time to list all the
    
       NetportExpress servers is to filter NetportExpress server SAPs.  This
    
       can be done on most routers. The NetportExpress server uses different
    
       SAP Server Type IDs than NetPort I & NetPort II servers.
    
    
    
       NetportExpress Server Type ID:         03FC
    
                                              03FD
    
    
    
       Finally, try Netport Manager.  It has a Domains option that creates
    
       logical groups of Netport print servers.   For example, you can create a
    
       domain called Finance and put in its group all the devices (including
    
       XLs, Netport II, and original Netport  print servers) that belong to the
    
       Finance department.  
    
    
    
    

    ACTIVITY LIGHT FLASHES IN 2 BLINK PATTERN

    
       Overview
    
       Anytime a NetportExpress print server is reset, it goes through a POST
    
       (Power on Self Test).  If a failure is found, the unit's activity light
    
       will flash in a pattern indicating what failure was found.  If the unit
    
       fails POST and the Activity LED flashes in a repeated pattern, the
    
       NetportExpress server will not come up on the network and will not show
    
       up under NPAdmin.  A 2 flash pattern indicates a Flash memory checksum
    
       error.
    
    
    
       Description
    
       If a Flash memory checksum error is discovered (2 flashes), the unit
    
       will not come up on the network and will not show under NPAdmin.  This
    
       should be verified by removing all printers attached to the unit and
    
       resetting the unit by re-engaging the power.  If the 2 flashes continue,
    
       normally a RMA (Return Merchandise Authorization) is required.
    
    
    
       To get a RMA go to your dealer or call the appropriate technical support
    
       number listed in your manual.  Have the unit's serial number, your fax
    
       number and your shipping address handy when you call.
    
    
    
    

    NPADMIN HANGS THE SYSTEM OR NETPORT MANAGER RETURNS ERROR: "IPX INITIALIZATION FAILED!" OR "IPX INITIALIZATION ERROR"

    
       Product:  NetportExpress XL and EL print servers
    
       Other:  Novell NetWare
    
    
    
       Symptom
    
       NPADMIN hangs the system or Netport Manager returns error: "IPX
    
       Initialization Failed!" or "IPX initialization error"
    
    
    
       Description
    
    
    
         If using VLMs:
    
    
    
         *  The NETX.VLM module is not loaded.  The NETX.VLM module is used in
    
            conjunction with Bindery Services to ensure compatibility with the
    
            utilities that come with NetWare 3.x and below.  NETX.VLM is also
    
            necessary if you have applications that are written to take
    
            advantage of the NetWare shell's specific API functionality.
    
    
    
         If NOT using VLMs:
    
    
    
         *  The Windows or network drivers are out of date.
    
    
    
       Solution
    
    
    
         If using VLMs:
    
    
    
         *  Modify the NET.CFG file to load the NETX.VLM module.
    
    
    
         If NOT using VLMs:
    
    
    
         *  Use the latest IPX.COM or ODI drivers.  If using the IPX driver,
    
            use IPX.COM v3.10 or later.  If using the ODI drivers, use v2.x or
    
            later of LSL.COM and IPXODI.COM.  You can get the latest releases
    
    
    
            of these drivers by downloading VLMUPX.EXE from Netwire on
    
            CompuServe.  Also make sure the MLID portion of the ODI stack is
    
            the latest available from the network card manufacturer.
    
    
    
         *  In the SYSTEM.INI file, in the [386Enh] section, the Network= line
    
            must include VIPX.386.  The VIPX.386 file should be dated November
    
            19, 1993 or later.  You can get the latest release of VIPX.386 by
    
            downloading WINDR1.EXE and NWDLL1.EXE from Netwire on CompuServe.
    
    
    
         *  Update to the latest version of NetPort Manager.   File NPXL1.EXE
    
            and NPXL2.EXE is available through Intel's online services.
    
    
    
    

    UPGRADING YOUR EXISTING NETPORTEXPRESS XL PRINT SERVER

    
       Customers who purchased a NetportExpress XL print server before the
    
       multiple protocol software  was released, can easily update their units
    
       in the field.  An upgrade kit is available for $25 and can be obtained
    
       by requesting packet number ZC.  Within the US and Canada, call Intel at
    
       503-222-5393, outside the US or Canada, contact your local Sales
    
       Representative.  The upgrade kit will contain TCP/IP, AppleTalk and
    
       Netport* Manager manuals, 4 software disks and update instructions.  As
    
       part of the upgrade process, you must do an RBL Flash memory update. 
    
       The current multiple protocol software is also available through Intel's
    
       online services.
    
    
    
    

    NETPORTEXPRESS PRINT SERVER WITH NETWARE 4

    
       Effective with the 2.7O firmware upgrade released in July 1995, the
    
       NetportExpress XL and EL print servers provide support for Novell
    
       NetWare Directory Services as well as Bindery support.
    
    
    
    

    NPADMIN SHOWS "ATTACHING-XXXX"

    
       Overview
    
       The NetportExpress XL print server has been configured and reset, but it
    
       still shows "attaching-xxxx" under NPAdmin.  The unit will not print
    
       when it is in this mode.  There are many possible reasons for the unit
    
       remaining in this mode.
    
    
    
       Possible solutions for Attaching problem
    
    
    
       Attaching-PTSC:
    
       The Print server password in Pconsole may have been changed and does not
    
       match the password originally defined in NPAdmin's Port or box settings.
    
        Check the passwords.
    
    
    
       Attaching-PTSC:
    
       If the XL unit is in Print Server mode, check that the file server that
    
       the unit needs to attach to has an open connection slot available.  If
    
       not, a connection slot will need to be cleared for each XL unit.
    
    
    
       Attaching-xxxx:
    
       Occasionally, the NetWare* bindery becomes corrupt.  Run the NetWare
    
       BINDFIX supervisor utility.  Then rerun NPAdmin and configure the unit
    
       again or manually reenter the configuration information in Pconsole and
    
       reset the unit.
    
    
    
       Note:     See the section titled "Print Server Attaching Messages and
    
       Descriptions" in "The Complete Guide" for more information about each
    
       Attaching error condition.
    
    

    Trademark information