Filter
Top Products
NetWare 4.x - No PSERVER Connection
131
• When defining a new “printer name” within PCONSOLE, did you
use a pre-defined destination/queue from the Ethernet Interface
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.
NOTE: When the IPDS feature is installed, queue name d4prn is not
available.
• The Ethernet Interface only supports Bindery mode when acting as a
PSERVER. Make sure all PCONSOLE setup is performed in Bindery
mode.
• 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 in to 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.
NetWare 4.x - No PSERVER Connection
• Has the Ethernet Interface 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 Ethernet Interface already servicing a queue on another file
server? If so, it can not 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_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 Ethernet Interface only recognizes names like
“
d1prn.” All other names will be ignored by the device.
NOTE: When the IPDS feature is installed, queue name d4prn is not
available.