GCC 12n Guía De La Red
21
Assuming that your printer is turned on and correctly connected to the network, the
problem may lie in the frametype. Make sure that the frametype listed in the printer’s
configuration page is the same Frametype being used by your NetWare client.
problem may lie in the frametype. Make sure that the frametype listed in the printer’s
configuration page is the same Frametype being used by your NetWare client.
• I changed the NEST configuration using the Config tool, but when I
power cycled my printer the configuration reverted to what it was before
the changes were made.
the changes were made.
Did you remember to click on the “Save” button in the Config tool?
• The print server didn’t log into the file server.
Make sure that the configuration page shows the same print server name and file
server name as the Config tool. If you are using NetWare 4, check the Config tool to
make sure that the name context, DS tree are correct, and check that you have entered
a typeful name context instead of a typeless name context. Also make sure that the
internal print server is active.
server name as the Config tool. If you are using NetWare 4, check the Config tool to
make sure that the name context, DS tree are correct, and check that you have entered
a typeful name context instead of a typeless name context. Also make sure that the
internal print server is active.
• The print server is running, but NPRINTER didn’t connect to it.
In NetWare 4, you must create a user on the file server for NPRINTER to log in as;
check NETADMIN or NWADMIN to make sure that you have created a user. Use the
Config tool to make sure that the printer has the correct name and password. Also
make sure that user is in the same context as the print server and printer objects by
looking in NETADMIN or NWADMIN.
check NETADMIN or NWADMIN to make sure that you have created a user. Use the
Config tool to make sure that the printer has the correct name and password. Also
make sure that user is in the same context as the print server and printer objects by
looking in NETADMIN or NWADMIN.
• I can send jobs to a queue correctly, but the printer won’t read the jobs
from the queue.
Try printing a configuration page. This will tell you if the print server and NPRINTER
have connected correctly. If they have not, the print server will not be able to print
jobs from the queue. If the print server has connected correctly to NPRINTER, check
the file server name to make sure that you have connected to the correct file server.
have connected correctly. If they have not, the print server will not be able to print
jobs from the queue. If the print server has connected correctly to NPRINTER, check
the file server name to make sure that you have connected to the correct file server.
If you can find no errors but the printer will still not print from the queue, use
PCONSOLE to check the queue; you may have disabled the queue.
PCONSOLE to check the queue; you may have disabled the queue.
• The printer prints a banner page, but the rest of the job does not print.
If your print job is sent from a Windows computer, this machine may be sending a
Control-d (^d) character at the beginning of the file which causes a PostScript error
immediately after the banner page is printed, halting the job. See the section “Con-
trol-d and PostScript printing” in the section “Configuring Windows computers that
will print to your NEST printer.”
Control-d (^d) character at the beginning of the file which causes a PostScript error
immediately after the banner page is printed, halting the job. See the section “Con-
trol-d and PostScript printing” in the section “Configuring Windows computers that
will print to your NEST printer.”