Filter
Top Products
Chapter 5 Novell Troubleshooting Tips
88
Novell Troubleshooting Tips
This section provides information on possible solutions to some standard
configuration errors. If you require technical support, please have as
much of the following information available when you call:
1. What level of software are you running?
2. What type of attachment do you have?
3. What is your host operating system?
4. Give a detailed description of the problem.
5. How often, and when, does the problem occur?
6. Give a detailed description of your network and the components
attached.
Please follow these tips to determine what the problem may be with your
PrintNet configuration.
NetWare 3.x - No PSERVER Connection
• Has the PrintNet been power cycled once 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 PrintNet 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 PrintNet (e.g., M_071C1A)? By default, it
only recognizes itself as “M_
xxxxxx
” where “
xxxxxx
” equals the last
six digits of its Ethernet address found on the configuration printout.
• When defining a new “printer name” within PCONSOLE, did you
use a pre-defined destination/queue rather than a name of your own?
By default, the PrintNet only recognizes names like “
d1prn.” All
other names will be ignored by the device.
• Is the PrintNet 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.