I have a problem with network printing on Solaris :
I have a printer server on a solaris which works ususally well with
most of our computers.

On a second machine we have issued an lp admin -p printer -s server

What's happening is that when we print on printer from the second
machine, the file is kept on the machine.
If we issue lpstat printer we can see the queue on the server and at
the end, the jobs issued on the second machine.
If we issue an lpq command, the jobs on the server are numberd from 1
to n and than the jobs on the machin start again from 1, as if there
was 2 queue.

Of course it has worked some times ago...

Any idea someone ?

f.g.

filh@filh.org writes:
>
>I have a problem with network printing on Solaris :
>I have a printer server on a solaris which works ususally well with
>most of our computers.
>
>On a second machine we have issued an lp admin -p printer -s server
>
>What's happening is that when we print on printer from the second
>machine, the file is kept on the machine.
>

So you're having a transport problem.  The print client machine is
not transferring the print job to the print server machine.

Can you log into the print client machine and type "telnet server 515"
and get a connection?  (you won't get a login prompt)  If not, what
happens?  Connection refused, or "Trying 12.34.56.78..." and it hangs
at that point?

Lpstat on the print client will show you the jobs on the print server
and the ones on the print client.  If you want to know if a job has
transferred to the server, run lpstat on the server.

  -Greg
-- 
Do NOT reply via e-mail.
Reply in the newsgroup.

gerg@panix.com (Greg Andrews) writes:

> filh@filh.org writes:
> >
> >I have a problem with network printing on Solaris :
> >I have a printer server on a solaris which works ususally well with
> >most of our computers.
> >
> >On a second machine we have issued an lp admin -p printer -s server
> >
> >What's happening is that when we print on printer from the second
> >machine, the file is kept on the machine.
> >
> 
> So you're having a transport problem.  The print client machine is
> not transferring the print job to the print server machine.
> 
> Can you log into the print client machine and type "telnet server 515"
> and get a connection?  (you won't get a login prompt)  If not, what
> happens?  Connection refused, or "Trying 12.34.56.78..." and it hangs
> at that point?

The in.lpd server works too...

Restarded both server and client... and it seems to work. But I would
like a lighter way.

Thanks.

f.g.

filh@filh.org writes:
>gerg@panix.com (Greg Andrews) writes:
>> 
>> Can you log into the print client machine and type "telnet server 515"
>> and get a connection?  (you won't get a login prompt)  If not, what
>> happens?  Connection refused, or "Trying 12.34.56.78..." and it hangs
>> at that point?
>
>The in.lpd server works too...
>
>Restarded both server and client... and it seems to work. But I would
>like a lighter way.
>

I'm sorry, but it's hard to offer a lighter way when you
didn't answer any of the questions.

  -Greg
-- 
Do NOT reply via e-mail.
Reply in the newsgroup.