View Single Post
  #2  
Old June 4th 05, 01:54 AM
alexander750
external usenet poster
 
Posts: n/a
Default

oh, I see why...Win98 doesn't support IP printing, at lest not natively. :-(

"alexander750" wrote:

I am attempting to set up printing from a 98se machine, via network, to a
printer connected to a Unix box. That printer works correctly when printing
jobs from its host; also, printing works correctly in Windows with its own
printer (i.e., to LPT1).

On the Unix host, I have printer sharing and SAMBA (Microsoft server
emulation) set up correctly; in the Network Neighborhood, I can access the
Unix machine's /home directory (since I'm the only user--and thus the
sysadmin, apart from root and the usual daemons). I cannot, however, see
/var/spool, /var/spool/cups, or /var/spool/samba from Windows (this last has
777 permissions and thus should be visible anywhere on the LAN).

According to the CUPS documentation, when printing from Windows, any
standard PostScript driver can be used (since the host is running Ghostscript
and thus acts as a RIP for whatever printer is connected to it), with a PPD
appropriate for the printer. I used the Apple Color LaserWriter PS driver to
do so, with a modified PPD for the Epson inkjet actually in use there.

When I open the Printers window to add the printer, then select "Network",
and then click "Browse", the Unix box shows no printer connected. If I enter
the network IP address directly as per CUPS instructions (e.g.,
"http://192.168.1.100:631/printers/queue_name") I get a message saying
"This printer is currently offline. You may continue setup, but you will not
be able to use it until it has been placed online." When I complete setup,
the printer appears, but is grayed-out.

I have also tried using
http://machine_name:631/printers/queue_name,
\\machine-name\var\spool\samba, and
\\machine-name:631\printers\queue_name
to no avail.