NetWare 3.x – No PSERVER ConnectionNetWare 3.x – No PSERVER Connection

•Was the NIC power cycled after the PCONSOLE steps were completed? This will make the print server boot up and realize which print queue and file server it needs to service.

•Is the NIC already servicing a queue on another file server? If so, it cannot service another file server at the same time.

•When defining a new print server within PCONSOLE, did you use the correct name for the NIC (e.g., M_091C1A)? By default, it only recognizes itself as M_xxxxxx or M302_xxxxx for the Wireless Adapter where xxxxxx equals the last six digits of its Ethernet address found on the configuration printout or control panel settings under Ethernet Parameters, MAC address.

•When defining a new printer name within PCONSOLE, did you use a predefined destination/queue rather than a name of your own? By default, the NIC only recognizes names like d1prn. All other names will be ignored by the device.

•Is the NIC in Bindery mode as seen under the list pserver output on the device? If servicing only a NetWare 3.x file server, it must be set to handle Bindery services. The default setting is Bindery.

•Is there an available NetWare user license for the NIC to use while it acts as a PSERVER? Every PSERVER takes up one user license since it logs into the Novell file server.

•Have you given the connection process some time after repowering the NIC? In larger Novell environments, the file server identification and connection process can take several minutes.

If you are still experiencing difficulty accessing or browsing the printer, contact the Customer Solutions Center for further assistance.

169