PSERVER Setup
•Have you tried repowering the PrintNet? Wait about a minute before checking to see if it has logged in and attached to a queue.
•Is the network connector fastened tightly to the unit?
•Is the PrintNet already servicing a queue on another file server? If so, it cannot service another file server at the same time.
•Is there an available NetWare user license for the PrintNet to utilize while it acts as a PSERVER? Every PSERVER takes up one user license since it logs in to the Novell file server.
•When going through the PSERVER setup steps, did you name the PrintNet “M_xxxxxx” where “ xxxxxx” equals the last six digits of the Ethernet address? This is the default format of the unit’s name when it is acting as a PSERVER.
NOTE: This “M_xxxxxx” name must have six digits after the “ _” so if necessary, pad out each byte with a zero (0).
•Has the PrintNet’s name been changed from its default of “M_xxxxxx” and if so, have you incorporated this new name into your PSERVER setup?
•Is there a password set for the Print Server to utilize when it is logging in to the file server? Make sure the PrintNet’s PSERVER password matches that of the PSERVER setup or set both places to no password.
•When setting the PrintNet up as a PSERVER, did you specify a destination on the PrintNet (e.g., d1prn) for the printer name and did you remember this name is case sensitive?
NOTE: PrintNet destinations are case sensitive so they will not be recognized if they are typed incorrectly. By default, they are all in lowercase. If you are setting up in a NetWare 4.x environment, the destination must be renamed to uppercase to match the PCONSOLE or Netware Administrator entry. Please see set dest destination name newname on page 132 for information on changing names.
•Does the destination you used in your PSERVER setup have the Novell service enabled? Please see the “Commands” chapter for information on enabling/disabling services.
111
