Client Debugging Procedures
Windows (using Samba)
- In a MSDOS window, type net view \\net-print.
You should see a complete list of the printers on the Net-Print
server. If not, then your lmhosts file may be incorrect
or in the wrong place.
- In a MSDOS window, type net view \\net-print\queuename.,
where queuename is the name of the queue you want to
print to. You should see status information for this queue.
If not, then make sure that the queue name is correct.
MacOS X.2 and X.3
Diagnostic test
- Create a simple PostScript test file, or download test.ps.
- In a terminal window, cd to the directory containing the
PostScript test file and execute the following commands:
- For MacOS X.2 (Jaguar):
setenv AUTH kerberos
/usr/bin/klprng -A
-Pk-<queue_name>@net-print.cit.cornell.edu test.ps
- For MacOS X.3 (Panther):
setenv AUTH kerberos
/usr/libexec/cups/backend/klpr -A
-Pk-<queue_name>@net-print.cit.cornell.edu test.ps
- Carefully note any error messages.
- In particular, if the error message is Bus error, then
it is likely that you are using the wrong queue name.
Obtain the correct queue name from the Printer
Information page.
"Get_local_host: hostname '<your hostname>.<your
domainname>' bad" error
Your host name as reported by the hostname command
must be the same as the host name which is registered in DNS for your
host. In practice, we find that having the line HOSTNAME=-AUTOMATIC-
in the file /etc/hostconfig works. If the HOSTNAME
line on your workstation has a different value, then consider using the
following method to change it:
- Invoke a terminal session.
- cd /etc
- sudo pico hostconfig
- Edit the HOSTNAME line to be HOSTNAME=-AUTOMATIC-
- Save the hostconfig file.
- You must reboot your workstation for this change to take effect.
Kerberos
One possible reason for printing failure is if you do not have Kerberos
5
tickets. This could be due to a problem with your Kerberos
configuration
file. You can restore your Kerberos configuration file (/Library/Preferences/edu.mit.Kerberos)
by removing it and then re-installing Sidecar/Kerberos. The
installer
will not replace the config file if it already exists.
CUPS
You can examine your current printer configuration using the CUPS Web
interface.
For some reason, this doesn't work with Internet Explorer.
It
does work with Mozilla (and presumably Netscape). The main page
is
at http://localhost:631.
- Select Manage Printers.
- For each installed printer:
- Modify Printer allows you to view/change the
connection parameters and driver options.
- Configure Printer allows you to view/change
printer-specific features.
- Clicking on the printer name link also allows you to examine
the log of completed jobs.
The error log for CUPS is in /var/log/cups/error_log.
You can obtain more detailed log output by editing /etc/cups/cupsd.conf
to change LogLevel info to LogLevel debug. You
will have to type sudo killall -HUP cupsd to get
CUPS
to reread its configuration file.