Filter
Top Products
Chapter 6 Novell Troubleshooting Tips
188
NetWare 3.
x
- No PSERVER Connection
• Was the Ethernet Interface 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 Ethernet Interface 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 Ethernet Interface
(e.g., M_091C1A)?
For the Ethernet Adapter, it recognizes itself as the default,
M_xxxxxx, where xxxxxx represents the last six digits of the
network adapter's Ethernet address (e.g., M_091C1A) found
on the configuration printout.
• 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 Ethernet Interface only recognizes
names like d1prn. All other names will be ignored by the
device.
• Is the Ethernet Interface 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 Ethernet
Interface 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 Ethernet Interface? In larger Novell
environments, the file server identification and connection
process can take several minutes.