-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Well, I've licked it. I upgraded to a more recent version of Samba and it
took care the problem. It seems that the version I was using didn't handle
users correctly in the print que, and there was something wrong with the
guest setup. The new ve
> Message: 10
> From: Dan Sawyer <[EMAIL PROTECTED]>
> Organization: ArtisticWhispers/Blenderwars
> To: Joel Hammer <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
> Subject: Re: [Samba] Print server on all linux network
> Date: Sun, 6 Oct 2002 19:13:17 -0700
>
>
Hmmm...
I thought you can print well from the server itself?
Are you sure you were ever using BSD printing. Maybe you were really using
lprng.
I think samba defaults to bsd. Have you got a printing parameter in your
smb.conf?
Joel
On Sun, Oct 06, 2002 at 07:13:17PM -0700, Dan Sawyer wrote:
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Second update:
On the advice of someone else on this mailing list, I converted from BSD
printing to CUPS (still using samba). Doing so has given me what is perhaps
a more identifiable error message. When I send a job to the server, I check
the q
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
A followup to the last message:
I have configured the Samba server to act as a WINS server, so YAST2 finds it
now.
Upon examining the log.smbd file, I find that there are no log entries
generated when I try to print from the console or X on the cl
If it makes you feel any better, from day one with my linux experience
I have never gotten printing to work on my own small home network using
these automatic configuration tools. This explains why I know so much
about printing.
Have you ever posted to me your server printcap?
On the server, can
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Okay, Joel, after another bit of futzing around, here's what I've come up
with.
The files dumped using the command you told me to DO indeed write postscript
files to the directory in question. However every attempt to print those
files on the se
Well, this is progress.
This means that the file has been transferred to the samba server.
Now, I would look at the spool directory given in your smb.conf share
definition, and make sure the file got there.
It may have been removed via the printing command in your share.
(I blush to say I didn't s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Well, I now got a positive response from the console, but nothing printed.
Here's the console dump:
thedude@floyd:~> cat kittykey.txt | smbclient //bob/nec -c 'print -'
added interface ip=192.168.1.100 bcast=192.168.1.255 nmask=255.255.255.0
Got a p
Try putting a space between print and -
Joel
On Thu, Oct 03, 2002 at 09:32:49PM -0700, Dan Sawyer wrote:
> -BEGIN PGP SIGNED MESSAGE-
> thedude@floyd:~> cat kittykey.txt | smbclient //bob/nec -c 'print-'
> added interface ip=192.168.1.100 bcast=192.168.1.255 nmask=255.255.255.0
> Got a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Evidently something's not set up right. Here's what I got:
thedude@floyd:~> cat kittykey.txt | smbclient //bob/nec -c 'print-'
added interface ip=192.168.1.100 bcast=192.168.1.255 nmask=255.255.255.0
Got a positive name query response from 192.168.1
Well, you have to talk to the samba server from the client:
The basic command is as follows:
cat file | smbclient //server/nec -c 'print -'
Does this command work for you?
The file has to be in a format the printer (queue) can use on the server.
If this works, then you can set up print queues on t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Okay, I've removed the [printers] tab.
When I print locally, I do indeed use lpr -Pnec (or at least, that command
works very well). However, using that command from the client doesn't do a
thing for me (nor does printing from a gui program). I'v
I would remove [printers] since neither you or I know what it really does.
Now, when you print locally, you print to the queue nec?
This will depend on the lpr command (lpr -Pnec) or if you just use lpr the
first printer defined in you /etc/princap will be invoked.
Joel
On Thu, Oct 03, 2002 at 04
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Well, actually, no, I haven't been able to wrap my brain around how it works
beyond the bare concepturals you outlined.
Attatched is the printer secton of my samba.conf - perhaps it will be
enlightening. I tried modifying my conf based on your conf
Do you understand how printing works with samba?
Essentially, you just transfer the file to the samba spool directory, and
invoke lpr to print the file. You will need to look at your smb.conf file to
see what is supposed to happen. I would set up a share just for your printer
and not rely on the g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello, everyone -
I've been trying for two weeks now to get my print server operational under
Samba. After walking through the howtos and tweaking the configs per spec,
it just ain't working. Printing from a client machine sends, and then
nothi
17 matches
Mail list logo
