PSERVER Setup

•When setting the NIC up as a PSERVER, did you specify a destination on the NIC (e.g., d1prn) for the printer name, and did you remember this name is case sensitive?

NOTE: NIC 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 or Netware 5.x environment, the destination must be renamed to uppercase to match the PCONSOLE or Netware Administrator entry. Please see “set dest <dest> name <new_name>” on page -322for information on changing names.

•Does the destination you used in your PSERVER setup have the Novell service enabled? Please see “Commands” on page 305 for information on enabling/disabling services.

NOTE: The debug information that follows can be found by trying to telnet the NIC and issuing the commands given or launching a browser to the Novell status page on the NIC (e.g., http://192.168.11.9/

networkNovellStatus.html).

•Try doing a debug nest ipx telnet command on the NIC (or find the “IPX Layer” section on the Novell HTML status page). Check that a board has been bound to the NIC and that the network number is correct for your network. If not, you may want to set a specific frame type for the NIC to use. You can find out what frame type is bound to which board number using the debug nest odi command (or from the “ODI Layer” section on the Novell HTML status page).

•Try a debug nest fserver telnet command (or find the “File Servers” section on the Novell HTML status page). If no file servers show up, then there is probably a problem with the network connection, or the NIC is not on a Novell network. Try a debug nest sap telnet command (or find the “SAP” section on the Novell HTML status page) to see if the NIC is seeing any network activity.

195